Router blocking my games?

[Zlain]

I don't know what is wrong, but every time I connect to a server on Enemy Territory, it immediately disconnects. Whenever I try to play Gunz the duel, I get 999 pings too, so it must be something wrong with my PC.

Can anyone help?

I have made sure Windows Firewall isn't blocking them and I don't have any other firewalls.

Sun, 2009-08-02 11:42:40 - TCP Packet - Source:114.180.98.9,2050 Destination:81.97.236.74,445 - [Any(ALL) rule match]

Sun, 2009-08-02 11:43:01 - TCP Packet - Source:59.97.209.144,45046 Destination:81.97.236.74,445 - [Any(ALL) rule match]

Sun, 2009-08-02 11:43:26 - UDP Packet - Source:78.47.89.97,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 11:43:30 - TCP Packet - Source:124.63.97.122,16340 Destination:81.97.236.74,445 - [Any(ALL) rule match]

Sun, 2009-08-02 11:43:32 - UDP Packet - Source:78.47.89.97,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 11:44:08 - TCP Packet - Source:125.65.165.139,12200 Destination:81.97.236.74,8080 - [Any(ALL) rule match]

Sun, 2009-08-02 11:44:59 - UDP Packet - Source:78.47.89.97,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 11:47:26 - Administrator login successful - IP:192.168.0.2

That was some of my log. What does that all mean? It's getting really annoying now.

I have Malwarebytes, spyware blaster, WinPatrol and AVG anti-virus.

My router is Netgear DG834G

upon making the post, these appeared in the log:

Sun, 2009-08-02 11:49:48 - TCP Packet - Source:125.198.2.177,1314 Destination:81.97.236.74,445 - [Any(ALL) rule match]

Sun, 2009-08-02 11:51:00 - ICMP Packet - Source:80.166.186.211 Destination:81.97.236.74 - [Any(ALL) rule match]

[+BudMan MVC]

To play games behind a NAT router you need to forward the ports the game uses to your PCs internal IP 192.168.x.x, etc.

Or the Game needs to use UPnP and that needs to be enabled on your router.

For games that use ping times to allow you on, etc. etc. You need to allow your router to answer pings.. I would suggest your RTFM on your router on how to allow for port forwards and pings.

You can also look up your router and game here.

http://portforward.com/

See that traffic inbound to

Sun, 2009-08-02 11:43:26 - UDP Packet - Source:78.47.89.97,27960 Destination:192.168.0.2,27960 - [DOS]

That looks like your game to me.

http://www.rtcw.jolt.co.uk/content/faq/ene..._faq.html#ports

Wolfenstein: Enemy Territory FAQ

Return to Castle Wolfenstein relies on Internet communication via the IP protocol and UDP ports 27950, 27960, 27965 and 27952

[Zlain]

To play games behind a NAT router you need to forward the ports the game uses to your PCs internal IP 192.168.x.x, etc.

Or the Game needs to use UPnP and that needs to be enabled on your router.

For games that use ping times to allow you on, etc. etc. You need to allow your router to answer pings.. I would suggest your RTFM on your router on how to allow for port forwards and pings.

You can also look up your router and game here.

http://portforward.com/

I have absolutely no idea what any of that means.

Also, I tried disabling the firewall, and I can't connect to anything and I can't browse the internet. The connection remains "connected" but no pages load. When I enable the firewall, I can browse the internet but the same problem as I posted above happens before.

It's frustrating because I don't have a clue how any of this ping and wan and port rubbish works. I just want to play a FPS with a wired connection and it seems I can't even do that at the moment. The help files are all just useless because they make it even more confusing.

I tried portforward before, and they wanted me to make some weird static address thing. I have no idea how to do that and their help files don't work. I never once had this problem with an older Belkin router either.

Ok, I found some list of services and firewall rules and I'll add all those ports. Do you know the ports that I need for Gunz too?

Also, why do I need to portforward, because I didn't need to do this with my Belkin router.

Edited August 2, 2009 by djpailo

[Zlain]

I felt I needed to make a new post to show you what happened:

I forwarded the ports and allowed them on always for inbound and outbound services. The server connected and it was stable albeit very laggy for about 5-10 seconds. It then disconnected once more.

- [ET rule match]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:23 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:24 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:25 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:26 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:27 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:28 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:192.168.0.2,27960 Destination:84.243.214.43,27960 - [ET rule match]

Sun, 2009-08-02 14:01:29 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

[+BudMan MVC]

"I have absolutely no idea what any of that means."

Not sure how to answer that.. you have been pointed to where your problem is, and how to correct it.

If ports and static IPs are gibberish to you I would suggest you ask a local friend to help then. What exactly are you looking for -- someone to tell you to push the Red Shiny button and it will all work??

edit: Well it looks like you have your ports forwarded.. Thought you said this stuff was all gibberish? Your problem is

Sun, 2009-08-02 14:01:22 - UDP Packet - Source:84.243.214.43,27960 Destination:192.168.0.2,27960 - [DOS]

Your routers firewall is seeing that traffic as a "Denial of Service" so blocking it -- Allow for this traffic on your routers firewall, or turn of the extra checks..

As to why you did not need to do it on your other router -- did you put yourself in the DMZ? Or where you using UPnP? If you want inbound traffic to go to machine through a nat router -- you either have to setup the forwards, UPnP has to do it for you - or you have to be in the dmz of the router -- all traffic is sent to your machine, etc.

[Zlain]

"I have absolutely no idea what any of that means."

Not sure how to answer that.. you have been pointed to where your problem is, and how to correct it.

If ports and static IPs are gibberish to you I would suggest you ask a local friend to help then. What exactly are you looking for -- someone to tell you to push the Red Shiny button and it will all work??

With all due respect, not everyone is tech saavy. I have a wired connection to avoid hassle with wireless networks. It's connected to an Ethernet Port. As I mentioned before, and in my post above, you can clearly see I have allowed access for those ports and I followed those guides from portforward even though many are unclear. I still have no idea what a Static IP address is and after doing some research, many people seem to not recommend setting one up.

I don't know what other services are blocking this. I just allowed TCP connections through the ports too.

I have UPnP enabled already too- it was enabled by factory default.

I don't know what DMZ is, and the only reference I can find to it from my router settings is this:

Edited August 2, 2009 by djpailo

[offroadaaron]

To play games behind a NAT router you need to forward the ports the game uses to your PCs internal IP 192.168.x.x, etc.

Or the Game needs to use UPnP and that needs to be enabled on your router.

WOW thats completely incorrect!

Going by this statement if I wanted to look at a website on port 80 I would have to forward that port! So this is completely incorrect.

This doesn't seem like a NAT/PAT issue.

As to why you did not need to do it on your other router -- did you put yourself in the DMZ? Or where you using UPnP? If you want inbound traffic to go to machine through a nat router -- you either have to setup the forwards, UPnP has to do it for you - or you have to be in the dmz of the router -- all traffic is sent to your machine, etc.

Why would he place himself in a DMZ, talk about opening this computer up to everything.

And why would you forward ports or put uPnP on for connecting to game servers?

none of that makes any sense to me.

djpailo you do not need to forward any ports, but I would turn the firewall off on the router or change some of the settings... Use a personal firewall on the computer instead.

Edited August 2, 2009 by offroadaaron

[+BudMan MVC]

A static IP is just that -- static, one that does not change..

The reason its suggested with port forwards, is if your PC internal IP changes from say 192.168.0.2 to 192.168.0.3 your forwards to .2 are not going to work for you -- now are they ;)

Not sure where you read that you should not set one up - but that just nonsense.

You clearly have the traffic being sent to 192.168.0.2 -- is that your machines IP address? If not then no the game is never going to work.

But where I see a problem is that your router is DOS that traffic -- Denial of Service -- so your machine on the IP address of 192.168.0.2 is never getting it.

You can either set a static on the machine.. Portforward site gives instructions on how to do it.. Or if your router supports it you can set a reservation.. So the dhcp server on the router always gives your machine the SAME address.. Some routers call this static dhcp, etc. Kind of BS term if you ask me -- its a "reservation".

But no its not required to have a static -- as long as your forwards are set to your machines IP your good. Just need to know that they will break if your IP changes.

"Going by this statement if I wanted to look at a website on port 80 I would have to forward that port! So this is completely incorrect."

Where and the F do you come up with that??? :blink: Nor did I say that.. To allow traffic INBOUND that is unrequested by your machine -- you have to setup a forward plain and SIMPLE!!

Or your software needs to forward the traffic using UPnP, or your machine needs to be in the DMZ.. Port forwards have NOTHING to do with you talking to a server on port 80 and it answering you on your source port.

He has the ports forwarded.. He is getting a DOS on the 27060 port.

edit: And why would you forward ports or put uPnP on for connecting to game servers?

You do NOT always need them - But YES some games require inbound ports to be forwarded!! I did NOT tell him to put his box into the DMZ.. I stated that might of been why it worked on his other router... Or listed it as a method to allow for INBOUND traffic.

Now upon reading a bit further on this game..

With a simple gateway using Network Address Translation (NAT), there is no limit on outgoing traffic and the game will probably work for client machines, but not servers, without any need to customize the gateway.

So yes he can prob play this game without port forwards.. But his router is blocking it on a DOS.. but if he wanted to host the game, then yes he would need the ports forwarded.

Edited August 2, 2009 by BudMan

[Aldur82]

WOW thats completely incorrect!

Going by this statement if I wanted to look at a website on port 80 I would have to forward that port! So this is completely incorrect.

This doesn't seem like a NAT/PAT issue.

Actually you're wrong. The way firewalls/NATs work is more than 'block/allow'. Suffice to say, if you want to play a game that uses UDP packets then you NEED to set up port forwarding.

Website browsing works because your computer initiates the connection, the firewall logs this activity, and for that session it allows the data through both ways so long as it comes from the same address you sent it to. The nature of UDP packets is, the firewall doesn't know which side initiates the connection, so it blocks all incoming traffic...stopping your game from working.

Believe me when I say, Budman knows what he's talking about and I've learnt a lot from his posts on topics like this.

[offroadaaron]

A static IP is just that -- static, one that does not change..

The reason its suggested with port forwards, is if your PC internal IP changes from say 192.168.0.2 to 192.168.0.3 your forwards to .2 are not going to work for you -- now are they ;)

Not sure where you read that you should not set one up - but that just nonsense.

You clearly have the traffic being sent to 192.168.0.2 -- is that your machines IP address? If not then no the game is never going to work.

But where I see a problem is that your router is DOS that traffic -- Denial of Service -- so your machine on the IP address of 192.168.0.2 is never getting it.

You can either set a static on the machine.. Portforward site gives instructions on how to do it.. Or if your router supports it you can set a reservation.. So the dhcp server on the router always gives your machine the SAME address.. Some routers call this static dhcp, etc. Kind of BS term if you ask me -- its a "reservation".

But no its not required to have a static -- as long as your forwards are set to your machines IP your good. Just need to know that they will break if your IP changes.

"Going by this statement if I wanted to look at a website on port 80 I would have to forward that port! So this is completely incorrect."

Where and the F do you come up with that??? :blink: Nor did I say that.. To allow traffic INBOUND that is unrequested by your machine -- you have to setup a forward plain and SIMPLE!!

Or your software needs to forward the traffic using UPnP, or your machine needs to be in the DMZ.. Port forwards have NOTHING to do with you talking to a server on port 80 and it answering you on your source port.

He has the ports forwarded.. He is getting a DOS on the 27060 port.

He is connecting out, he isn't listening for traffic on the port!!!!!!

my statement still stands!

He does not need to forward any ports to connect to a server, he makes an outbound connection....

Read up on NAT/PAT please!

And he doesn't need to setup static IP addresses!

-----------

He would only need to forward ports if he is the server machine, which he isn't he is the client.

NAT/PAT is for when.

1- your hosting a server and you want someone to access it.

2- so when the client connects to the server the on a particually port (PAT) that it forwards that port to the desired machine (eg. I want to connect to neowin.net:80, they have 1 IP address 55.55.55.55, they setup DNS to point 55.55.55.55 to neowin.net and delegate their domain to the DNS...... but if you were to go to neowin.net it would hit the routers single IP address 55.55.55.55:80 and just die in the ass because it doesn't know where to route that traffic..... so they setup a port forward NAT/PAT for port 80 to go to the internal IP address...... now when you go to 55.55.55.55:80 it directs the traffic to port 80 or whatever they have assigned it to on the inside IP address)

Edited August 2, 2009 by offroadaaron

[Zlain]

Ok, I tried changing the ports to forward it too 192.168.0.1

The same thing happened where it connects for a few seconds then it shows that their is a lost connection.

LAN Port

MAC Address EDITED OUT

IP Address 192.168.0.1

DHCP On

IP Subnet Mask 255.255.255.0

That is what it says on my "router status page", so my ports are now forwarded to the correct PC but it isn't working still :(

[offroadaaron]

don't forward any ports!!!!!!!! it will not do anything!!!!

turn the firewall off and test!

:argue: :argh: :omg: :angry: :no:

[+BudMan MVC]

Offroadaaron is correct on the port forwarding "for this game" From what I read on the page I linked to for that game, the ports are only needed to be forwarded if your HOSTING the game, ie running the server other people connect to.

But from your logs your getting a DOS hit on that traffic.. And if you were forwarding it to the wrong IP, then yeah that would of caused problems ;)

btw: Is your computer IP 192.168.0.1 or is that your routers IP?

You would find your computers IP by using from a command prompt ipconfig. From the manual for that router, its IP is 192.168.0.1 It sure and the F is not going to working if your forwarding traffic to the routers IP address.

edit: Read up on NAT/PAT please!

Your F'ing kidding me!! I am quite aware of HOW NAT/PAT works :rofl:

I would suggest you read up on the FACT that some games require forwards to PLAY, not just host.

Edited August 2, 2009 by BudMan

[Zlain]

don't forward any ports!!!!!!!! it will not do anything!!!!

turn the firewall off and test!

:argue: :argh: :omg: :angry: :no:

Everytime I disable the firewall, the internet doesn't work at all and I can't connect to anything nor can I browse any site. The connection remains connected though.

I tried forwarding it to port 192.168.0.3 but that didn't work either.

So I've tried port forward to the following IP's:

192.168.0.1

192.168.0.2

192.168.0.3

None worked. I myself am not running a server so I don't know why it is blocking this traffic. The problem is I can't disable the firewall because it cuts of all internet activity. So what should I do now? :s

[offroadaaron]

Offroadaaron is correct on the port forwarding "for this game" From what I read on the page I linked to for that game, the ports are only needed to be forwarded if your HOSTING the game, ie running the server other people connect to.

But from your logs your getting a DOS hit on that traffic.. And if you were forwarding it to the wrong IP, then yeah that would of caused problems ;)

no if your forwarding it to the wrong IP address it doesn't matter! has nothing to do with port forwards! Port forwards have 0 to do with this topic trust me!!!!!!

you can forward the port anywhere you like it will not do anything unless you have a server on the IP and port.

I feel like I'm going around in a circle........ round and round! :argh:

Everytime I disable the firewall, the internet doesn't work at all and I can't connect to anything nor can I browse any site. The connection remains connected though.

I tried forwarding it to port 192.168.0.3 but that didn't work either.

So I've tried port forward to the following IP's:

192.168.0.1

192.168.0.2

192.168.0.3

None worked. I myself am not running a server so I don't know why it is blocking this traffic. The problem is I can't disable the firewall because it cuts of all internet activity. So what should I do now? :s

You should probably get an IT professional to have a look at it, I'm almost 100% positive its a firewall somewhere!

Just allow all traffic to go to your machine then, so allow any any in your firewall and test.

Edited August 2, 2009 by offroadaaron

[Zlain]

no if your forwarding it to the wrong IP address it doesn't matter! has nothing to do with port forwards! Port forwards have 0 to do with this topic trust me!!!!!!

you can forward the port anywhere you like it will not do anything unless you have a server on the IP and port.

I feel like I'm going around in a circle........ round and round! :argh:

You should probably get an IT professional to have a look at it, I'm almost 100% positive its a firewall somewhere!

If it is a firewall issue, then surely there must be some setting which I just need to turn off, but what setting could that be?

[offroadaaron]

If it is a firewall issue, then surely there must be some setting which I just need to turn off, but what setting could that be?

maybe just allow all traffic to your machine in the firewall and test! Theres an idea ;)

[Zlain]

maybe just allow all traffic to your machine in the firewall and test! Theres an idea ;)

how do I do that??

[+BudMan MVC]

"no if your forwarding it to the wrong IP address it doesn't matter!"

Sorry -- but if um yeah if yoru forwarding traffic to the WRONG IP, that is needed -- yes it can cause a PROBLEM!

But as stated, and agreed this game does not need ports forwarded to PLAY, only to host.

Remove all the port forward rules.

And then try and play -- and post up your logs again.. Your problem is your seeing a DOS rule.. The routers firewall is blocking the traffic because it thinks its a DOS "denial of service" attack.

[Eric Veteran]

He is connecting out, he isn't listening for traffic on the port!!!!!!

my statement still stands!

He does not need to forward any ports to connect to a server, he makes an outbound connection....

Read up on NAT/PAT please!

And he doesn't need to setup static IP addresses!

-----------

He would only need to forward ports if he is the server machine, which he isn't he is the client.

NAT/PAT is for when.

1- your hosting a server and you want someone to access it.

2- so when the client connects to the server the on a particually port (PAT) that it forwards that port to the desired machine (eg. I want to connect to neowin.net:80, they have 1 IP address 55.55.55.55, they setup DNS to point 55.55.55.55 to neowin.net and delegate their domain to the DNS...... but if you were to go to neowin.net it would hit the routers single IP address 55.55.55.55:80 and just die in the ass because it doesn't know where to route that traffic..... so they setup a port forward NAT/PAT for port 80 to go to the internal IP address...... now when you go to 55.55.55.55:80 it directs the traffic to port 80 or whatever they have assigned it to on the inside IP address)

It's a game. It has to be able to communicate in both directions. When the game server sends data that wasn't solicited with an outbound request the router has to know which client to route the data to. If it's not a known service then the client either has to have set up port-fowarding manually, via UPnP, or the client machine needs to be the DMZ destination. HTTP traffic is a well-known service and routers already know how to redirect the traffic for it.

[offroadaaron]

"no if your forwarding it to the wrong IP address it doesn't matter!"

Sorry -- but if um yeah if yoru forwarding traffic to the WRONG IP, that is needed -- yes it can cause a PROBLEM!

incorrect completely.

Go forward 80 to a random PC and see if you can browse the web still on a completely different PC..... bet you anything you can and it won't cause any issues AT ALLLL :angry: (again, read up on NAT/PAT)

Round and round (circles!!!!! I'm seeing circles)

There maybe an option in the firewall for DOS attacks which you can disable somewhere.

[+BudMan MVC]

"Go forward 80 to a random PC and see if you can browse the web still on a completely different PC"

WTF does that have to do with anything!!!!! The source port is NOT 80 now is it!! Take your own and advice and read up on how NAT/PAT works!!!

There would be no inbound traffic to 80 to forward unless hosting a http server..

As to the DOS issue

And the other is to allow your route to respond to pings -- so that should allow games that require certain ping times to ping you.

BTW to your example of forwarding to the wrong IP not causing issues -- go Forward your P2P port to the wrong IP and see how well your P2P app works ;)

This is EXACTLY correct from GreyWolf:

"When the game server sends data that wasn't solicited with an outbound request the router has to know which client to route the data to."

If his machine is 192.168.0.100 and he has set his router to send all traffic on port XXX UDP to .101 -- he is going to have ISSUES now isnt he!! If his games requires port XXX to work.

Edited August 2, 2009 by BudMan

[offroadaaron]

It's a game. It has to be able to communicate in both directions. When the game server sends data that wasn't solicited with an outbound request the router has to know which client to route the data to. If it's not a known service then the client either has to have set up port-fowarding manually, via UPnP, or the client machine needs to be the DMZ destination. HTTP traffic is a well-known service and routers already know how to redirect the traffic for it.

Completely incorrect again.

I router knows HTTP? Are you completely serious?

"Go forward 80 to a random PC and see if you can browse the web still on a completely different PC"

WTF does that have to do with anything!!!!! The source port is NOT 80 now is it!! Take your own and advice and read up on how NAT/PAT works!!!

There would be no inbound traffic to 80 to forward unless hosting a http server..

As to the DOS issue

WOW look at that I pointed him to the correct option!!!

crazy.

BTW it has everything to do with everything.

HTTP or a game its the same thing..... IP:PORT! it doesn't matter if its HTTP or ICMP or whatever else!!! its all the same thing IP:PORT.

BTW to your example of forwarding to the wrong IP not causing issues -- go Forward your P2P port to the wrong IP and see how well your P2P app works wink.gif

Thats for inbound connections!!!!!!!!!!! not outbound connections!!!!!!!!

your computer listens on that port you are basically a server just like everyone else on the P2P network, same with torrentz!

Read this: http://en.wikipedia.org/wiki/Port_forwarding

Edited August 2, 2009 by offroadaaron

[+BudMan MVC]

Your completely clueless..

As I already posted

This is EXACTLY correct from GreyWolf:

"When the game server sends data that wasn't solicited with an outbound request the router has to know which client to route the data to."

If his machine is 192.168.0.100 and he has set his router to send all traffic on port XXX UDP to .101 -- he is going to have ISSUES now isnt he!! If his games requires port XXX to work.

Your forwarding 80 to the wrong IP example is utter nonsense --- no one is has ever been talking about outbound traffic!!! Only inbound.. And I told he had a problem with DOS back before you even joined the thread.

As GreyWolf correctly stated -- and I have been saying all along.. Some games require inbound Ports to be forwarded.. If your forwarding the wrong freaking IP then YES your going to have issues.

This game might not need forwards.. But it needs XXX on UDP and he has a specific rule on his router to send that traffic to .101 and his machine is .100 --- Yes he can have issues... That has nothing to do with your nonsense port 80 forwarding example.. Since nothing would be talking to my router INBOUND on port 80 for me to view websites.. So NO freaking **** I would be able to browse them from every machine on the inside of my router.

Take your own advice and read up on NAT/PAT!!

[Sethos]

offroadaaron, could you please stop acting like a 12 year old, read up on the stuff your preaching and THEN come back? Because you are completely clueless.