Thread: Your mother

Originally Posted by belowzeros

so I had some developments...

After trying just about everything on my PC and router I connected directly to my modem as a last result. To my surprise the game and connected worked fine. I didn't think I had a router problem because everything else seems to work fine.

So now I'm trying to figure out what exactly my dlink DIR-655 is doing that is blocking L4D. I have a static IP for this machine, I have Steam ports forwarded, I have SPI turned off now (didn't solve this problem).

Is there anything else anyone can think off that a router would do to interfere with steam or L4D?

Yep, that is a great question. Routers do get funky some times. I know I have had to periodically reset my router (Linksys WRT54G) back to it's factory defaults when I was having problems.

I don't think it is a port forwarding problem, because my setup runs just fine, and I don't have ANY ports forwarded for L4D or Steam.

I dunno...

Originally Posted by BigAzzGunz

I also have the D-Link DIR-655, and was experiencing issues creating and joining internet games (dedicated). I’ve purchase the router to replace my aging WRT54G about a month ago and was unable to resolve the issue until today.

Here’s what I did to resolve the issue.
1. Downgrade to 1.20 firmware (from 1.21)
2. After the downgrade I tried to create a “Best available dedicated server”…and it worked!. Rebooted and created and joined a few more dedicated servers without any issues.

I do not think the downgrade did anything to resolve the issue. But, I did notice that when I configured the router to port forward the steam ports it actually replicated the issue.

TCP 27030-27039
UDP 1200,27000-27015

Conclusion: Try removing the port forward rule for steam. If that does not work, try downgrading/upgrading the routers firmware to 1.20 and give it a shot.
D-Link DIR-655 Xtreme N Gigabit Router

Sweet, glad you got it working!!