[RESOLVED] Major network lag with client / server

[uasmatrix]

What I find interesting is that if I put the external IP in the .cfg file where the LAN IP used to be, it has no issues and it even says the IP is my external. Yet the server still doesn't show up.

Also, according to Valve, the +ip has to be internal or a wildcard (https://developer.valvesoftware.com/wiki/Command_Line_Options#Command-line_parameters_4)
"-ip
Specifies the address to use for the bind(2) syscall, which controls on which IP addresses the program is reachable on. It must either be a local address (an addresses of the host it runs on) or 0.0.0.0 (the wildcard). This has nothing to do with externally-visible addresses in NAT setups. "

"+ip - Specifies the IP when multiple network cards are installed (Old, but still works). " (This doesn't fully apply to me however)

I also have run the HLDSupdatetool a few times, still nothing.

I also can't join via 'connect' command if I use my WAN IP, nor does it appear in my favorites if I use my WAN IP. However, other people can join fine (yet not everyone can see it in the internet tab)

[uasmatrix]

I found the solution!

I was browsing various other threads with this issue when I came across a post:
http://forums.srcds.com/viewtopic/11309/3

"I had this same issue. Troubleshot for days with my router, server.cfg, and whatever I could think of. I have a D-LINK DIR-655. I ended up getting my server to list in the steam server list by adding 27015 in my virtual server forwarding option. If your router has the ability to forward as a virtual server, try this instead of under the port forwarding section. Works great for me now. "

Luckily, I have that same exact router. I followed what that man did and it appears to have worked perfectly!

Again, thank you very much for your time and patience with my issue(s). I'm glad we figured all of this out and have everything working now!

[scso1502]

Glad you fixed it, though I must admit I'm blown away at the solution. If your ports are forwarded correctly, it should have worked using port forwarding too. Bizarre.

Ironically, I have two DIR-655 routers here at my house as well. I'm wondering if there's a firmware update for your router that may be needed to correct the issue? Either way, glad to hear it's up and running. Way to go!

Can you please add [RESOLVED] to your original post's subject line so people know you fixed it?

Take care!