TCP failure

Has anyone experienced a connection failure (possibly due
to a virus)with the following symptoms:
1. The NIC is operational.
2. It can obtain/renew an IP from DHCP during startup.
3. Ipconfig shows the correct IP and autoconfig data.
4. Ping localhost and locally assigned IP.
5. Can not ping any other server on the subnet.

Hi Tony,

If your computer can gent DHCP assigned IP then it can communicate with
server on the network... Still did you check cables, switches, etc...

Make sure that servers you are trying to ping don't have personal firewall
enabled. Once you ping them run this on the computer

arp -a

Do you get any entries?

Can any servers or clients ping this server?

Mike

"Tony" <(E-Mail Removed)> wrote in message
news:41e801c4a01c$4e4f12f0$(E-Mail Removed)...
> Has anyone experienced a connection failure (possibly due
> to a virus)with the following symptoms:
> 1. The NIC is operational.
> 2. It can obtain/renew an IP from DHCP during startup.
> 3. Ipconfig shows the correct IP and autoconfig data.
> 4. Ping localhost and locally assigned IP.
> 5. Can not ping any other server on the subnet.
>

Arp -a is empty.

192.168.2.55 server A
192.168.2.1 Hub (DNS, DHCP, and gateway)
192.168.2.40 Bad Server B

A can ping hub and internet, A can not ping B, A works 100%

B can ping itself and localhosts, B can not ping hub
(destination host unreachable"), B can not ping A,
ipconfig /renew fails because "unable to contact DHCP
server"

possibly something in the registry?

>-----Original Message-----
>Hi Tony,
>
>If your computer can gent DHCP assigned IP then it can
communicate with
>server on the network... Still did you check cables,
switches, etc...
>
>Make sure that servers you are trying to ping don't have
personal firewall
>enabled. Once you ping them run this on the computer
>
>arp -a
>
>Do you get any entries?
>
>Can any servers or clients ping this server?
>
>Mike
>
>"Tony" <(E-Mail Removed)> wrote in
message
>news:41e801c4a01c$4e4f12f0$(E-Mail Removed)...
>> Has anyone experienced a connection failure (possibly
due
>> to a virus)with the following symptoms:
>> 1. The NIC is operational.
>> 2. It can obtain/renew an IP from DHCP during startup.
>> 3. Ipconfig shows the correct IP and autoconfig data.
>> 4. Ping localhost and locally assigned IP.
>> 5. Can not ping any other server on the subnet.
>>
>
>
>.
>

Try plugging into a different port on the switch and using a different cable
to see if it makes a difference. A virus could have also corrupted or
changed something with networking. Run the netdiag support tool to see if
any failed/tests/errors are reported and pay special attention to the
winsock test. Possible other things to try are to go into device manager and
unistall the network card and reboot, reinstall know good drivers, reinstall
tcp/ip, repair winsock registry entries, try using safe mode woth
networking, run System File Checker as in sfccannow, or restore from a
recent System State Backup. The links below have more details. If this is a
domain controller it is more complicated to reinstall tcp/ip. --- Steve

http://support.microsoft.com/?id=285034
http://support.microsoft.com/default...en-us%3B321708
http://support.microsoft.com/default...en-us%3b817571 -- winsock
repair
http://support.microsoft.com/default...b;en-us;222471 -- System
File Checker. If using W2K and not SP4 it may override hotfix files.

"Tony" <(E-Mail Removed)> wrote in message
news:41e801c4a01c$4e4f12f0$(E-Mail Removed)...
> Has anyone experienced a connection failure (possibly due
> to a virus)with the following symptoms:
> 1. The NIC is operational.
> 2. It can obtain/renew an IP from DHCP during startup.
> 3. Ipconfig shows the correct IP and autoconfig data.
> 4. Ping localhost and locally assigned IP.
> 5. Can not ping any other server on the subnet.
>

Can you replace a cable that goes from your computer to switch or hub? Also
try different port on switch/hub.

Still it could be local problem on the server. Check also what Steven posted
and here are some additional resources that might be useful.

How to reset "Internet Protocol (TCP/IP) " in Windows Server 2003
http://support.microsoft.com/default...uct=winsvr2003

How to determine and recover from Winsock2 corruption
http://support.microsoft.com/default.aspx?kbid=811259

How to remove and reinstall TCP/IP on a Windows Server 2003 domain
controller
http://support.microsoft.com/default...uct=winsvr2003

Which server is this? Windows 2000 or Windows 2003?

Mike

<(E-Mail Removed)> wrote in message
news:100a01c4a028$fda288c0$(E-Mail Removed)...
> Arp -a is empty.
>
> 192.168.2.55 server A
> 192.168.2.1 Hub (DNS, DHCP, and gateway)
> 192.168.2.40 Bad Server B
>
> A can ping hub and internet, A can not ping B, A works 100%
>
> B can ping itself and localhosts, B can not ping hub
> (destination host unreachable"), B can not ping A,
> ipconfig /renew fails because "unable to contact DHCP
> server"
>
> possibly something in the registry?
>
> >-----Original Message-----
> >Hi Tony,
> >
> >If your computer can gent DHCP assigned IP then it can
> communicate with
> >server on the network... Still did you check cables,
> switches, etc...
> >
> >Make sure that servers you are trying to ping don't have
> personal firewall
> >enabled. Once you ping them run this on the computer
> >
> >arp -a
> >
> >Do you get any entries?
> >
> >Can any servers or clients ping this server?
> >
> >Mike
> >
> >"Tony" <(E-Mail Removed)> wrote in
> message
> >news:41e801c4a01c$4e4f12f0$(E-Mail Removed)...
> >> Has anyone experienced a connection failure (possibly
> due
> >> to a virus)with the following symptoms:
> >> 1. The NIC is operational.
> >> 2. It can obtain/renew an IP from DHCP during startup.
> >> 3. Ipconfig shows the correct IP and autoconfig data.
> >> 4. Ping localhost and locally assigned IP.
> >> 5. Can not ping any other server on the subnet.
> >>
> >
> >
> >.
> >