Page 1 of 1
1001: Error connecting to server. (11003)
Posted: 2014-02-05 15:21
by Aka Izayoi
Good morning,
it seems that I've finally come to seek additional assistance. I've been playing PR for awhile (3-5 months then a break; repeat) and I've really been enjoying the game's evolution. But, since the beginning of January, I can no longer log into my online account; receiving the error - 1001: Error connecting to server. (11003) . At first, I just thought PR was migrating over to PR2. But, these past few days, it seems the regulars on the server I play on is still on fighting. So, I retried, failed to log in online expectantly, then resorted to reinstalling PR. Finished working that out, but I still couldn't get in. I checked to see if I could get in and play offline, which worked fine; I managed to log in and get back into my choppers (Offline of course). Then, to double check, I ran BF2 vanilla to see if I could log into Gamespy there. Turns out I could, which I did and played (Only very, very shortly after everyone was yelling every enemies' position every two seconds.) I returned back to the PR launcher and tried again, without success to this moment. I clicked on Support on the PR launcher but even that gets an error and leaves me with this PR launcher log report. I would love to get back out there on the field, drop those neat little packages out there, and start lifting those ground pounders out of hot spots once again. I'm sure they're feeling the heat down there. Think you guys can help an 'ol pilot out?
Re: 1001: Error connecting to server. (11003)
Posted: 2014-02-05 15:33
by LITOralis.nMd
Is your Antivirus or Firewall blocking PR? Try to disable your AV and firewall for testing.
You need to allow PRBF2.exe (same direcotry as BF2.exe) and PRLauncher.exe and PRUpdater.exe (both in BF2\mods\pr\bin ) to get through your firewall and antivirus and router and router's internal firewall.
If you post your exact info for
firewall and antivirus and router
I can probably pin it down immediately.
If you start PRLauncher, click Support, then click "Copy to clipboard" then paste it all in this thread, I'll have your system specs, which can also help.
Re: 1001: Error connecting to server. (11003)
Posted: 2014-02-05 15:41
by Aka Izayoi
Ah, how could I forget to mention. Naturally, I also testing for my firewall/AV and checked to see if anything in my router changed. Regardless, I still met the same faith.
Well, what do you need? I'll be happy to provide it. Some kind of log from my firewall or AV perhaps? Or will names suffice? Just let me know.
It seems I can't get those specs for you. Right as I click on Support on the PR Launcher, I get a critical error, blocking me from user input to the Support log and gray out-ing the "Copy to clipboard" button. If you ask me, I think she just wants you to buy her dinner before getting a peek inside first.
Re: 1001: Error connecting to server. (11003)
Posted: 2014-02-05 15:50
by LITOralis.nMd
Right as I click on Support on the PR Launcher, I get a critical error, blocking me from user input to the Support log and gray out-ing the "Copy to clipboard" button.
? That is not good. That is a separate and more pressing problem.
First, let's start with original problem:
just tell me which AV , firewall and router you have.
Re: 1001: Error connecting to server. (11003)
Posted: 2014-02-05 15:51
by LITOralis.nMd
Second problem related to the critical error:
I'd prefer seeing the exact error msg, so please recreate, then screencap or write down, then post the info in this thread.
Re: 1001: Error connecting to server. (11003)
Posted: 2014-02-05 16:06
by Aka Izayoi
Not too sure what to say, maybe the new year spooked her while I was out. Seemed to be working just fine back in December. But, right to the topic, I use Avira and Windows' built in firewall with a Motorola router/modem.
Finished on one, now working on to Guess 2. In the mean-time, you may gander at the little log it keeps stating for me:
Code: Select all
Project Reality Log File
PRLauncher.exe started at: 2014-02-05T06:04:01
Critical Error: An unhandled exception has occured. Details are as follows:
Object reference not set to an instance of an object.
Further details can be found in the following file:
[url]C:\Battlefield 2\mods\pr\bin\PRLauncher.log[/url]
Please report this error to the Project Reality Team, and include the log file in your report.
[url=https://www.realitymod.com/forum/f27-pr-bf2-support]Visit Support Forum[/url]
> System.NullReferenceException: Object reference not set to an instance of an object.
at Reality.BF2.GameSpy.GameSpyConnection..()
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Re: 1001: Error connecting to server. (11003)
Posted: 2014-02-05 16:07
by Aka Izayoi
Actually, this is the updated one, sorry about that.
Code: Select all
Project Reality Log File
PRLauncher.exe started at: 2014-02-05T06:05:59
Critical Error: An unhandled exception has occured. Details are as follows:
Object reference not set to an instance of an object.
Further details can be found in the following file:
[url]C:\Battlefield 2\mods\pr\bin\PRLauncher.log[/url]
Please report this error to the Project Reality Team, and include the log file in your report.
[url=https://www.realitymod.com/forum/f27-pr-bf2-support]Visit Support Forum[/url]
> System.NullReferenceException: Object reference not set to an instance of an object.
at Reality.BF2.GameSpy.GameSpyConnection..()
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Critical Error: An unhandled exception has occured. Details are as follows:
Object reference not set to an instance of an object.
Further details can be found in the following file:
[url]C:\Battlefield 2\mods\pr\bin\PRLauncher.log[/url]
Please report this error to the Project Reality Team, and include the log file in your report.
[url=https://www.realitymod.com/forum/f27-pr-bf2-support]Visit Support Forum[/url]
> System.NullReferenceException: Object reference not set to an instance of an object.
at Reality.BF2.GameSpy.GameSpyConnection..()
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Re: 1001: Error connecting to server. (11003)
Posted: 2014-02-05 18:41
by LITOralis.nMd
Right, something is blocking your connection to the GameSpy servers,
those are the online login auth servers for BF2.
Two ways to troubleshoot this:
1. Your router might be acting foolish in regards to forwarding ports to your PC:
You can try this automated solution
[quote=""'[R-COM"]LITOralis.nMd']
WarGrade" wrote:I think that i found a solution!!!!
(This worked for me and i don't know if it will work for others)
1. Download
'Portforward Setup Static IP Adress' (completely free)
2. Install it......
3. When you run it, at the bottom there should be a button that says 'Make it Dynamic' click that button and it will make your IP address dynamic.
4. Run the PR launcher and you should get an update.
It should be FIXED!
I'm sorry if it doesn't work for anyone else.
[/QUOTE]
2. You can manually enter the TDP and UDP ports that BF2 and PR need to operate:
[quote=""'[R-COM"]LITOralis.nMd']
thepalerider" wrote:You guys sure when you get disconnected PnkBstrB is still running and all 3 instances are still set to auto-restart?
When is the last time you ran PBsetup to update Punkbuster (first thing you should do when you have a disconnect out of the blue)
Check your router's logs for "**UDP Flood to Host**" or similar warnings ( from:
router / connection problem / voip / multiple lan players) Check if your router has "IP Flood Detection" enabled. If so turn it off.
Make sure these ports are open on your router
(my router 'D-link Gamers lounge' auto opens these ports for BF2)
TCP
80,Battle recorder port
4711,Remote console
29900,Client+Server
29901,Client Not in use yet
29920,Server Standard Port
28910, Client
44301= PnkBstrA
45301= PnkBstrB
UDP
1500 - 4999,General use
16567,Game port
27900,Stats port
29900,Gamespy port
29910,gamespy port
27901,Stats port
44301 = PnkBstrA,
45301 = PnkBstrB,
55123,VOIP ports
55124,VOIP ports
55215,VOIP ports
Not sure what ports (TCP/UDP)
port for PnkBstrA =
44301
port for PnkBstrB =
45301
should be, so opened for both
I'll try to think of something else, but anyone reading this thread feel free to jump in with new ideas.
Good luck
[/QUOTE]
Most important will be ports 29900, and 29901 for both udp and tcp.
Basically you need to either forward or trigger the ports 27900~27901 and 29900~29910.
SO depending on your router, you'll find a menu called something like
Port Triggering
and enter these values.
Some Name 27900 ~ 27901 27900 ~ 27901 enabled
Some Name2 29900 ~ 29901 29900 ~ 29901 enabled
Re: 1001: Error connecting to server. (11003)
Posted: 2014-02-06 06:28
by Aka Izayoi
Alright, back on to the computers. That was the answers I also saw regarding similar problems, so I took a look at my ports and went according to the description given in the prior threads. I did set up my ports and all that fancy stuff, but still went on persisting. Of course, that's where we get to now. But, you're the chief, so I'll reset it all back up for the heck of it. In mean while, seems you're right on that pressing issue. Something did bug me when all of a sudden my Windows Update was turned off out of the blue and wouldn't start. Guess it's time to dig up what's happening and fix it. The main computer (The computer in question) is having its Service Pack 1 uninstalled and reinstalled. After which, we'll see if I can get those Updates back up and running, and finally get that .Net Framework in working shape. Glad to see some support out here.
Re: 1001: Error connecting to server. (11003)
Posted: 2014-02-06 08:50
by Daniel
So, is BF2 working right now but PR not?
Re: 1001: Error connecting to server. (11003)
Posted: 2014-02-06 09:25
by Aka Izayoi
That's correct. I could jump into BF2 vanilla, log into my online account and jump into a server. I can also jump into PR Offline, play around, and jump off just as fine. But, I cannot connect to my online gamespy account via PR Launcher. The PR Launcher is also stating at the bottom "Error loading news....". I'm starting to suspect this is just the tip of the iceburg, since my Windows Update refusing to start up, I can't reinstall my .Net Frameworks (Fails to install), and my BITS is calling back with an error code. Sure does sound like a sign of infection to me, but I'm already ahead of the crowd. System scans with Avira, MBAM, and Super Anti-spyware all came in clean. CCleaner helped tidy loose files here and there. Rkill and RogueKiller both coming clean for any active Malware Root-kits. I'm moving on the motion that something fishy with my System files, particularly with my registry. SFC is reporting system files are a-okay, and Chkdsk is coming with clean reports. I'm leaning back and forth on restoring my registry.
Re: 1001: Error connecting to server. (11003)
Posted: 2014-02-06 19:47
by LITOralis.nMd
and my BITS is calling back with an error code.
A general troubleshooting strategy here, should help googling the BITS problem which is a serious serious problem:
Boot into safe mode, uninstall and reinstall BITS.
reregister the (I think 4) dlls associated with BITS.
You need to head to the MBAM support website or bleepingcomputer forum probably, you need to run Hijackthis and other more specific rootkits scanners... if BITS is broken.
The last time I had this problem I ended up doing a full reformat... but that was winXP and like 6 years ago.
Re: 1001: Error connecting to server. (11003)
Posted: 2014-02-07 03:22
by Aka Izayoi
Naturally, google is a nice way of working through things. Hopped on and searched here and there. I already did try clean booting and safe mode, it remained the same still. The other assortments of solutions didn't help settle the problem as well. As I was searching around, I found out I was searching for more solutions to different problems. I realized that it wasn't an isolated error, and that there is something generally wrong with my Windows files/setting. Since there wasn't any single posts out there that defined my problem specifically, I concluded that either my SP was installed or some type of Windows update but something went wrong, causing all sorts of havoc. Since it was a broad range of problems, I reinstalled my OS. It's finally good to see those Updates up and running again. Got BF2 and PR reinstalled again. Haha, you don't know how happy I am too see the news streaming again at the bottom of the PR Launcher. Online account with PR is working once again. Thanks mate, if you didn't bring my attention to the Support Log crash, I would have still been tinkering with the PR Launcher settings and what not. If you're ever in the field, just give me a shout. I'll be there in a drop of a dime! Just do me a favor, and try not to bleed in my choppers.