![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
First, let me explain my network ... 2 comps in my room connecting to a Netgear 4-port hub. Netgear 4-port hub connects to Kingston 8-port switch. 2 comps, a printer, a Linksys BEFSR11, and a Linksys WAP11 also connect to Kingston 8-port switch. Linksys BEFSR11 connects to cable modem, Comcast is the ISP. 1 computer connects to the WAP11 at the moment. The BEFSR11 is doing DHCP. All systems are running Windows XP.
All of the computers can get onto the internet just fine except for the one that connects to the WAP11. I figure this is a WAP11 problem since the thing is a piece of shit. The laptop gets all of the proper information (i.e. IP address, DNS info, etc.) but cannot resolve any DNS. I did an ipconfig /flushdns and it can resolve names if I use the nslookup command, but it cannot ping anything and says that the hostname cannot be found. I told the system to use my workplace's DNS boxes as primary and secondary DNS, and that works flawlessly. Why isn't the laptop allowing the Comcast DNS boxes to resolve names for it?
Furthermore, here's a trace from my system (but it could be any of the systems, since they all do the same thing) to Google:
Why does my trace look that strange?
All of the computers can get onto the internet just fine except for the one that connects to the WAP11. I figure this is a WAP11 problem since the thing is a piece of shit. The laptop gets all of the proper information (i.e. IP address, DNS info, etc.) but cannot resolve any DNS. I did an ipconfig /flushdns and it can resolve names if I use the nslookup command, but it cannot ping anything and says that the hostname cannot be found. I told the system to use my workplace's DNS boxes as primary and secondary DNS, and that works flawlessly. Why isn't the laptop allowing the Comcast DNS boxes to resolve names for it?
Furthermore, here's a trace from my system (but it could be any of the systems, since they all do the same thing) to Google:
Code:
C:\Documents and Settings\evildre>tracert -d [url]www.google.com[/url]
Tracing route to [url]www.google.akadns.net[/url] [216.239.41.104]
over a maximum of 30 hops:
1 12 ms * 12 ms 24.13.48.1
2 11 ms * 11 ms 68.87.226.189
3 11 ms * 10 ms 68.87.229.161
4 15 ms * 12 ms 12.244.72.246
5 15 ms * 15 ms 12.123.6.58
6 13 ms * 12 ms 12.123.6.65
7 14 ms * 13 ms 208.175.10.93
8 34 ms * 34 ms 206.24.226.99
9 36 ms * 35 ms 206.24.238.38
10 35 ms * 35 ms 216.109.66.82
11 38 ms * 37 ms 216.109.88.218
12 38 ms * 37 ms 64.233.174.133
13 36 ms * 34 ms 216.239.49.37
14 38 ms * 36 ms 216.239.41.104
Trace complete.
C:\Documents and Settings\evildre>Why does my trace look that strange?
), and it still didn't do it. Looks like I'll be stuck with the shitty trace indefinitely