PDA

Bekijk de volledige versie : WL-500W blocking google?



Spam007
26-11-2006, 15:55
Hi

Im having a bit of a problem with my new router (Asus WL-500W).

Problem
My laptop is unable to go to www.google.com and certain other web pages when using the wireless connection..the screen just times out after a while. However I can ping www.google.com without any problems. When I connect the laptop to the router with cable directly google + all other sites works.

I have:


tried resetting my router to default settings
updated my router and laptops wireless card (Intel(R) PRO/Wireless 2200BG Network Connection) with the latest drivers/firmware
contacted my ISP to get special settings but were told to use auto on all, DNS etc.
searching my laptop for spyware and virus with Adaware, AVG anti spyware and NAV with no result
opening C:/windows/system32/drivers/etc/hosts to check if there is anything there blocking google


What is going on?

vlx
27-11-2006, 16:03
Hi

Im having a bit of a problem with my new router (Asus WL-500W).

Problem
My laptop is unable to go to www.google.com and certain other web pages when using the wireless connection..the screen just times out after a while. However I can ping www.google.com without any problems. When I connect the laptop to the router with cable directly google + all other sites works.

I have:


tried resetting my router to default settings
updated my router and laptops wireless card (Intel(R) PRO/Wireless 2200BG Network Connection) with the latest drivers/firmware
contacted my ISP to get special settings but were told to use auto on all, DNS etc.
searching my laptop for spyware and virus with Adaware, AVG anti spyware and NAV with no result
opening C:/windows/system32/drivers/etc/hosts to check if there is anything there blocking google


What is going on?

Hi, that is strange,
Try tracert -d www.google.com [in windows]. To see if there are not some strange routes..
But problably not. Probably firewalls settings are the couse.
If you sill could not see what the problem is, then you probably have to use tcpdump on asus or list firewall rules.

EddieZ
27-11-2006, 17:04
Thanks for your well descibed post! You've clanly described circumstances and actions already undertaken. Doesn't happen that often :-)

Seems like the wireless part of the router is using the firewall and the wired part is not hindered by it. Could you list your settings in the router setup, esp. Internet Firewall?

You might also try to manually configure the DNS servers used by the Asus.

Spam007
27-11-2006, 20:56
Tracert looks like this:



Tracing route to www.google.com [209.85.129.104]
over a maximum of 30 hops:

1 <1 ms <1 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 23 ms 8 ms 8 ms 83.88.9.194
4 24 ms 9 ms 10 ms 83.88.12.34
5 30 ms 12 ms 9 ms 83.88.20.22
6 14 ms 9 ms 9 ms 83.88.12.78
7 14 ms 9 ms 9 ms 195.215.109.2
8 12 ms 9 ms 14 ms 213.248.65.9
9 27 ms 23 ms 23 ms 213.248.65.146
10 38 ms 26 ms 23 ms 80.91.249.198
11 38 ms 25 ms 24 ms 213.248.96.102
12 42 ms 25 ms 25 ms 66.249.95.133
13 39 ms 25 ms 24 ms 72.14.232.140
14 108 ms 108 ms 96 ms 72.14.232.209
15 118 ms 102 ms 102 ms 72.14.232.201
16 123 ms 101 ms 102 ms 72.14.233.210
17 123 ms 36 ms 67 ms 209.85.129.104

Trace complete.

Does that look strange?

Working on the TCPDump.....

vlx
28-11-2006, 00:59
Tracert looks like this:



Tracing route to www.google.com [209.85.129.104]
over a maximum of 30 hops:

1 <1 ms <1 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 23 ms 8 ms 8 ms 83.88.9.194
4 24 ms 9 ms 10 ms 83.88.12.34
5 30 ms 12 ms 9 ms 83.88.20.22
6 14 ms 9 ms 9 ms 83.88.12.78
7 14 ms 9 ms 9 ms 195.215.109.2
8 12 ms 9 ms 14 ms 213.248.65.9
9 27 ms 23 ms 23 ms 213.248.65.146
10 38 ms 26 ms 23 ms 80.91.249.198
11 38 ms 25 ms 24 ms 213.248.96.102
12 42 ms 25 ms 25 ms 66.249.95.133
13 39 ms 25 ms 24 ms 72.14.232.140
14 108 ms 108 ms 96 ms 72.14.232.209
15 118 ms 102 ms 102 ms 72.14.232.201
16 123 ms 101 ms 102 ms 72.14.233.210
17 123 ms 36 ms 67 ms 209.85.129.104

Trace complete.

Does that look strange?



Hmm, not so much...
Only strange thing is 2nd hop router which is not reponding to TTL timeout. But its kind a common thing..
Try to list iptables rules:
iptables -nvL
iptables -t nat -nvL
iptables -t mangle -nvL

if its possible [what firmware are you using on Asus anyway?]
antother story is tcpdump and then to look what is going on wire..

Moody Blue
28-11-2006, 01:09
Are you using PPPoE ? If yes, have you setup the MTU of your wireless card to 1492 ? There's a utility, DRTCP, that can change MTU on any LAN card. You can find DRTCP for example in http://www.dslreports.com/

Spam007
28-11-2006, 19:38
Firmware is standard Asus version 1.9.7.3.
Firewall is disabled.
I am not using PPPoE.

Tried downloading tcpdump for windows but did not catch any trafic at all. Does tcpdump need any attributes to run? Will Ethereal work as an alternative?

Will try iptables as soon as I figure out where to get it and how to install....

Thank you all for helping!! : )

PS. Does anyone else have the same problems with WL-500W? Could it be a n-draft related problem?

vlx
29-11-2006, 09:29
Firmware is standard Asus version 1.9.7.3.
Firewall is disabled.
I am not using PPPoE.

Tried downloading tcpdump for windows but did not catch any trafic at all. Does tcpdump need any attributes to run? Will Ethereal work as an alternative?

Will try iptables as soon as I figure out where to get it and how to install....

Thank you all for helping!! : )

PS. Does anyone else have the same problems with WL-500W? Could it be a n-draft related problem?

Standard 1.9.7.3... download olegs firmware and try that.

yeah, ethereal is better. Or use packetyzer in windows [the best :) !].
But i meant to use tcpdump on asus..
Anyway firstly try it in windows..

PS: try: ping -t -l 1472 www.google.com in windows..

Spam007
30-11-2006, 07:12
Tried pinging with 1472


Pinging www.google.com [209.85.135.104] with 1472 bytes of data:

Reply from 209.85.135.104: bytes=56 (sent 1472) time=104ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=132ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=154ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=77ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=85ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=110ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=135ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=157ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=79ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=103ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=127ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=150ms TTL=245

Ping statistics for 209.85.135.104:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 157ms, Average = 117ms

By the way is there a difference between www.l.google.com and www.google.com....if I ping directly to screeen it shows me www.l.google.com but when I ping to a file it writes www.google.com???

Still working on:

Olegs firmware
Ethereal / Packetyzer

Could use some help on:
Tcpdump (do I have to telnet my router?)
IPTables (same)

Cheers

vlx
02-12-2006, 15:23
Tried pinging with 1472


Pinging www.google.com [209.85.135.104] with 1472 bytes of data:

Reply from 209.85.135.104: bytes=56 (sent 1472) time=104ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=132ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=154ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=77ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=85ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=110ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=135ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=157ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=79ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=103ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=127ms TTL=245
Reply from 209.85.135.104: bytes=56 (sent 1472) time=150ms TTL=245

Ping statistics for 209.85.135.104:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 157ms, Average = 117ms

By the way is there a difference between www.l.google.com and www.google.com....if I ping directly to screeen it shows me www.l.google.com but when I ping to a file it writes www.google.com???

Still working on:

Olegs firmware
Ethereal / Packetyzer

Could use some help on:
Tcpdump (do I have to telnet my router?)
IPTables (same)

Cheers

Another thing to try is to dissable LAN interface in windows if you are connecting through Wireless interface. Do you have WL500-W configured in bridged mode?
Post here a saved config of your router.
Next thing to try is a olegs firmware.
Then we can try to catch packets with packetyzer and tcpdump [you must use telnet] and analyze that.

Spam007
03-12-2006, 14:23
I am currently testing another router which seems to be working without any problems.

I will try Oleg on the Asus router later.

Thanks for all the help for now!