Hello all Hammies...
This is a troubleshooting issue that has had me bogged down for a few
days now. Perhaps someone out there can shed some light...
I have a windows XP pro box connected, via a hub, to a linux machine
running rh8.0. the rh box has dhcp, dns and firewall services here at my
tmex tech shop (tmex.org), so I can get any and all new machines up on the
net safely and easily. This win xp box was getting it's DHCP ip real nice
and easy, no problems at all, pinging the 192.168.1.1 linux box no problem,
everything was honkey dorey, until a few days ago. It all seemed to happen
once I updated my McAffee virus program, and then all of a sudden, I
couldn't ssh in via putty as I normally did, said it couldn't find the ip
for 192.168.1.1. DHCP couldn't get an ip with 'ipconfig /release' or
'ipconfig /renew' (kept giving me auto-IP crap.) Tried assigning a static
IP for the nic in windows, with the dns server pointing to 192.168.1.1, no
luck. Strange thing is, machines on the hub that are pulling ghost images
off this windows box can get to it fine, so the nic is healthy and the link
layer's healthy... seems like the problem resides in the tcp/ip stack...
strange?!?!
Tried netsh varieties like 'netsh int reset ip' and other things, with
reboot, same issue. Anyone have any ideas of what I should try next to get
this damned xp's tcp stack back up to par?
Thanks for reading the lengthy problems everyone!
Sean
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
- Re: Craziness with Win XP Pro Jairo Medina
- Re: Craziness with Win XP Pro Sean Dembrosky
- Re: Craziness with Win XP Pro Sean Dembrosky
- Re: Craziness with Win XP Pro PinkFreud
