Alright guys (and girls)
Seems to be a lot of problems with everyone connecting.
I had similar issues, but i hate to be defeated so had a play and have found what seems to be a possible solution.
I have a system which worked fine when i first installed Defcon. It authenticated and i could see other people playing. i just couldnt seem to get anoyone to connect to me.
I had a play and suddenly my system did all the stuff you guys are having.......authentication status on "checking" and no servers listed for me to join.....
In the end I have found the following works for me:
Set ports 5008-5011 to allow send/recieve UDP in your SOFTWARE firewall. This has already been done by most of you (if not, get on with it)
If you have a router you obviously need to mess with port forwarding. This seems to be the bit thats causing the issue!
I found forwarding ports 5008-5011 (all of which defcon uses) allowed people to connect to me, but i couldnt authenticate or connect to others.
Disabling the forwarding let me join to other peoples games and authenticate, but they couldnt join to me???
Upshot of this is....ONLY FORWARD PORT 5010. DO NOT set port forwarding on ports 5008-5009 and port 5011. these will stop you authenticating!
Wierd Eh?
Note: also set 'port forwarding' in DEFCON network setttings to 'Enabled'
These are based on default PORTS as instaled by DEFCON.
I've done a fair bit of testing and this seems to fix all problems. I have tried this on 3 of the 5 terminals on my network, using WIN XP and win 2k. Zonealarm and norton firewall. This fixes every one I have done the tests on so far.
Hope this helps some of you guys.
Auth problems? Hosting issues? no servers listed? *ReadMe*!!
Moderator: Defcon moderators
-
- level0
- Posts: 6
- Joined: Thu Oct 05, 2006 9:22 pm
- Mighty Santa
- level2
- Posts: 150
- Joined: Tue Sep 19, 2006 5:10 pm
- Location: London, UK
- Contact:
Another important thing (I just found out after painful hours of wondering why my DefCon won't auth)
I didn't try this with a direct version from IV yet, but it solved all my problems with my Steam version.
DefCon(Steam) does send a DNS request everytime it starts, trying to find metaserver.introversion.co.uk. Now, in my home/company network, we got 2 DNS servers. One for Internet stuff and one for Intranet. Now, if you only got the Intranet-DNS set in your connection settings (this was the case for the auto-configuration I received from our DHCP), you'll have a hard time getting a reply for a DNS-request about an Internet server.
Solution: Set the Internet-DNS as the primary DNS server in your connection settings and the Intranet one as the alternative (may also work vice versa)
IF THIS DOESN'T HELP: I found this out by simply using a packet sniffer on my PC: Wireshark. It showed me that my PC sent an UDP-packet with a DNS request for metaserver.introversion.co.uk and as an answer got an ICMP-packet that it can't find the server because the port is unreachable. This way it lead me to my solution. What I want to say with this is: IF my solution didn't help you, and you're somewhat computer savvy and/or got enough patience to look through the logs any try to find out what's happening: Download Wireshark and find out!
I didn't try this with a direct version from IV yet, but it solved all my problems with my Steam version.
DefCon(Steam) does send a DNS request everytime it starts, trying to find metaserver.introversion.co.uk. Now, in my home/company network, we got 2 DNS servers. One for Internet stuff and one for Intranet. Now, if you only got the Intranet-DNS set in your connection settings (this was the case for the auto-configuration I received from our DHCP), you'll have a hard time getting a reply for a DNS-request about an Internet server.
Solution: Set the Internet-DNS as the primary DNS server in your connection settings and the Intranet one as the alternative (may also work vice versa)
IF THIS DOESN'T HELP: I found this out by simply using a packet sniffer on my PC: Wireshark. It showed me that my PC sent an UDP-packet with a DNS request for metaserver.introversion.co.uk and as an answer got an ICMP-packet that it can't find the server because the port is unreachable. This way it lead me to my solution. What I want to say with this is: IF my solution didn't help you, and you're somewhat computer savvy and/or got enough patience to look through the logs any try to find out what's happening: Download Wireshark and find out!
Who is online
Users browsing this forum: No registered users and 6 guests