Can't accesss google
Thrax
🐌Austin, TX Icrontian
Hosts file has been blanked to eliminate that.
The domain resolves an IP.
I can't ping the resolved IP.
Two other computers in my house can reach google.
There are no abnormal resident programs.
There are no popup blockers.
Work this one out. :sad2:
I have a Linksys BEFSR41 and Linksys WRT54G linked together. The BEFSR41 is handling the internet connection and outsources to two wired clients, the WRT54G is sitting in router mode (As opposed to gateway), handles my wireless card, and forwards all requests for internet to the BEFSR41 via static route. The routers are linked together through the BEFSR41's uplink port, and before last week there were no problems.
The only thing changed was Windows 2000 to Windows XP so I could use TKIP, but as of yet I have not set TKIP up, so that variable is eliminated. Windows XP worked with Google for approximately seven days.
The domain resolves an IP.
I can't ping the resolved IP.
Two other computers in my house can reach google.
There are no abnormal resident programs.
There are no popup blockers.
Work this one out. :sad2:
I have a Linksys BEFSR41 and Linksys WRT54G linked together. The BEFSR41 is handling the internet connection and outsources to two wired clients, the WRT54G is sitting in router mode (As opposed to gateway), handles my wireless card, and forwards all requests for internet to the BEFSR41 via static route. The routers are linked together through the BEFSR41's uplink port, and before last week there were no problems.
The only thing changed was Windows 2000 to Windows XP so I could use TKIP, but as of yet I have not set TKIP up, so that variable is eliminated. Windows XP worked with Google for approximately seven days.
0
Comments
Can't browse either by IP.
(sounding pretty damn weird man)
Also note that two other computers can access google on the same network setup, so it's local to the computer.
(Damn weird is right. I've never heard of anything like this.)
If that doesn't work, use http://www2.google.com as a temporary fix.
NS
A trace route to some of these addresses *may* help along with a route print.
I did so, and it's 100% ping timeout to google and the requested IPs (And short-media as a reference; WTF?!?!) as well as destination unreachable to everything beyond the first hop on traceroute (For google, my problem, and S-M + the requested IPs, my references).
What the ****ing hell?
(This is the time to drop the f-bomb!)
In case you are still trying, type 'route print' at a console and post the results.
DHCP starts at 192.168.1.2 and goes through .1.6
if that fails, reset the router to factory specs and reconfigure it, that is unless you have the firewall in to configured for a bunch of crap.
also you can run a tracert to SM and post that as well... TIA
Gobbles
Tracert to s-m also fails after first hop (router). Which means the modem is probably giving me the screw, or the router is failing to forward ICMP out of its eth. int.
Also, can you log into the router with the problematic client (I suspect you can as it is showing up in the tracert)?
Do the router logs show the outbound traffic or is the router dropping everything from the particular client?
I can also log into the router, yes.
Router logs are disabled, but they're also linksys logs which simply shows incoming/outgoing IPs as opposed to any real information.
TCP from 192.168.1.10:4111 to www.teamshort-media.com(198.64.191.210):80
from both a good and the bad client. We're running short of options here.
LAN: 192.168.1.5 Dest: 198.64.191.210 (Team Short-Media) Port: www (80) --- GOOD CLIENT
That's all there is. The WRT54G, does not, unfortunately use SNMP trapping for logging, so I can't use an SNMP client to intercept logs. It uses another protocol (syslog), but the WRT54G disallows the forwarding of logs to an IP address, so that's worthless.
Ghosts in the machine, maybe?
Ghosts in the machine indeed, pretty crappy ghost eh?
Still interesting that I cant traceroute or ping anything. Bah.
Thanks for all the help.