1017 error firewall example

F

Fadeuken

Dalayan Beginner
1.Version of Windows (including any service packs and exact version e.g Windows XP home edition SP 2):
Windows XP home edition SP2

2.Firewall in use. Did turning it off give any apparent effect at all:
Zonealarm – Running all the time but I have tried reducing the protection level with no improvement.

3.Router (If any) and firmware version:
Not connected to the internet via a router. Connected via a USB ADSL modem.

4.Type of graphics card/Driver version:
Nvidia 6800gt. Forceware version 84.40

5.Processor type and amount and type of computer memory (e.g. Athlon 3500+, DDR PC3200 2x512Meg):
Athlon 3500+. 1 gig RAM (2x512 PC3200)

6.Type of internet connection (if possible with ISP) and country:
Two Meg ADSL connection in the UK with Tiscali broadband.

9. Does logging on at different times of the day reduce or increase the error:
Does not seem to effect the error. There can be any number of players on the server and the error will still be there. However sometimes I can get connected quicker and not drop when zoning as much, but this seems to be at random intervals.

10. Have you tried logging on on another computer in your location or elsewhere:
This I have not done as my friends are xbox fans.

11. Any filesharing background programs running or installed (please include which):
I have Limewire installed but not running.

12. How long have you had this problem:
Since I set up my account last month.

13. Which steps have you taken to fix this:
I have tired all the suggested fixes on various posts in the forum.

14. Other. Anything you've noticed or feel is relevant to the error.
I was able to connect to the official servers just a few weeks before I changed to Shards of Dalaya. I had no issues whatsoever in playing the game.

Now paste you dbg.txt file to the end of the entry showing the part where the error is seen.
[Fri Apr 07 19:24:46 2006]00020:Creating font list...
[Fri Apr 07 19:24:46 2006]00021:Deleting obsolete sound drivers.

[Fri Apr 07 19:24:46 2006]00022:Deleting bad files list.

[Fri Apr 07 19:24:46 2006]00023:Display init start.

[Fri Apr 07 19:24:46 2006]00024:Display init point a.

[Fri Apr 07 19:24:46 2006]00025:Display init done.

[Fri Apr 07 19:24:49 2006]00026:net_connect(), (g_rdp=0x00000000, g_world=0x00000000) before receive

[Fri Apr 07 19:24:49 2006]00027:net_connect: rdp 0x0257e680 is connecting to 209.172.32.20:9000...

[Fri Apr 07 19:24:49 2006]00028:net_connect: I am connected to 209.172.32.20:9000...

[Fri Apr 07 19:24:49 2006]00029:net_connect: returning 0...

[Fri Apr 07 19:24:49 2006]00030:WorldAuthenticate. sending on conn 0x0335fa48...

[Fri Apr 07 19:24:49 2006]00031:wait_message(), (g_rdp=0x0257e680, g_world=0x00000000) before receive

[Fri Apr 07 19:24:59 2006]00032:wait_message(), after receive, msg is 0x00000000

[Fri Apr 07 19:24:59 2006]00033:*** ERROR: wait_message(), no message, bailing

[Fri Apr 07 19:24:59 2006]00034:*** ERROR: WorldAuthenticate. My message arrival was NULL, the net has been shutdown...
 
I split your topic because it really really looks like firewall, especially since I've seen many many people have problem with zonealarm.

Try shutting it off and see if that works.
 
I didn't think it was the cause of the error but I shut down zonealarm completely and no difference. Zonealarm is not the culprit.

From my dbg file:

[Fri Apr 07 23:52:57 2006]00076:Creating font list...
[Fri Apr 07 23:52:57 2006]00077:Deleting obsolete sound drivers.

[Fri Apr 07 23:52:57 2006]00078:Deleting bad files list.

[Fri Apr 07 23:52:57 2006]00079:Display init start.

[Fri Apr 07 23:52:57 2006]00080:Display init point a.

[Fri Apr 07 23:52:57 2006]00081:Display init done.

[Fri Apr 07 23:52:57 2006]00082:net_connect(), (g_rdp=0x00000000, g_world=0x00000000) before receive

[Fri Apr 07 23:52:57 2006]00083:net_connect: rdp 0x02506e50 is connecting to 209.172.32.20:9000...

[Fri Apr 07 23:52:57 2006]00084:net_connect: I am connected to 209.172.32.20:9000...

[Fri Apr 07 23:52:57 2006]00085:net_connect: returning 0...

[Fri Apr 07 23:52:57 2006]00086:WorldAuthenticate. sending on conn 0x025d1a80...

[Fri Apr 07 23:52:57 2006]00087:wait_message(), (g_rdp=0x02506e50, g_world=0x00000000) before receive

[Fri Apr 07 23:53:07 2006]00088:wait_message(), after receive, msg is 0x00000000

[Fri Apr 07 23:53:07 2006]00089:*** ERROR: wait_message(), no message, bailing

[Fri Apr 07 23:53:07 2006]00090:*** ERROR: WorldAuthenticate. My message arrival was NULL, the net has been shutdown...
 
And go on the internet naked? Not very likely!

I do have the windows firewall turned off when Zonealarm is active so I'm not double firewalled. I would think at least 99% of people connecting to the internet will be firewalled by either of these two as its asking for trouble to connect otherwise.
 
I don't mean to permanently disable them. Just disable them both for three minutes when attempting to connect. If it works, you know where the issue is.
 
Sorry to doubt you. I run the program without either the Zone Alarm or Windows firewall and it logged in. Tried twice to confirm and result.

So the issue is a firewall one, but why do some computers have firewall issues and some don't....Hmmm...If you can figure this out you will have my eternal gratitude. :roll:
 
In most cases an external firewall is better than a software firewall. For example: I have my hardware firewall/router set up so that any computer from within my network has full access out (meaning if my PC initiates communication out it allows that connection full access through whatever ports the program needs). But on the flip side if an outside IP/virus tries to get in, it's denied. Hardware firewalls give you many different types of options you can configure based on your internal networks demands. A software one can too, but the software ones are typically not efficiently coded, and you don't have much flexibility with them as they may appear.
 
I may have to look into a hardware firewall then. But its strange how I did not have this problem with official servers. SoD must be ran under older server code from them, and I suspect the Service Pack version could be the root of the problem.
 
You must log in or register to reply here.
Back
Top Bottom