I could connect internally on the LAN IP - but not on the WAN IP. External users were unable to connect to my server from outside my network. They only got the message MSG: Contacting Server.

I'm using a Netgear WGR614 router.

Port forwarding was set up - but apparently the old server used TCP only and version 3.0 uses UDP as well.

Problem - the WGR614 does not allow you to specify the protocol. TCP is apparently assumed with the exception of a few forwarding schemes that are built in.

Solution - Under the advanced menu - go to the WAN setup page. Check on "Default DMZ server" and set it to the LAN IP of your Vent server. This will default all traffic to that IP that isn't specifically forwarded elsewhere (including UDP on port 3784).

This fixed my problem.

If you aren't using a WGR614 but aren't able to specify UDP forwarding - look for a similar setting on your router.

If you can specify UDP - make sure you create 2 rules... 1 for UDP and 1 for TCP. My understanding is that some people have had trouble when setting a single line UDP \ TCP rule.

Hopefully this helps at least one person out there!

Good luck all.

digi

Edit: I should disclose that this does essentially put your server in a DMZ so only do this if you are willing to accept the security risks inherent in doing so.

Hey I'm having the same problem w/ connecting to v3.0.1. I get the "Msg: Contacting Server." My Router is a Linksys WRT54G. I am very computer illiterate. I'm guessing that I'm having the same problem as this guy, but I wasn't sure which "Advanced" option he is referring to. I'm really just asking for a possible brief step by step on fixing this problem. I run on Windows if that helps.

If you can specify UDP - make sure you create 2 rules... 1 for UDP and 1 for TCP. My understanding is that some people have had trouble when setting a single line UDP \ TCP rule.

Hopefully this helps at least one person out there!

AAARGH! (But in a good way.) So I read this post about 18 times, but apparently I'm an arrogant SOB who said my Linksys router properly handles the TCP/UDP BOTH setting. Gee, that COULDN'T be why I'm not connecting could it?

Now, here I am reading it at 4 in the morning and I decide to make separate rule lines for 3784TCP, 3784UDP, and 6100UDP. CONNECT. READY...

Thanks DigiFreak! You can count me as your one person. For others out there who are arrogant SOBs and can't figure out why people can't connect to you, split your TCP and UDP rules into different lines.

If you’re connecting the client from a different PC than the server then configure the client to use one of the internal ipaddresses of the server. If you’re running the client on the same PC as the server then use 127.0.0.1 or “localhost” as the servername.