PC not recognised on network

I have an SBS 2000 network using static IP addressing.
One PC has full network access to other resources and can ping other
machines, the server, default gateway, etc.
The problem is that no other machine or the server can ping this PC - the
request is timed out.
Due to this I cannot remotely manage this PC as the server cannot see it.
--
John

Hi John,

did this work at some time? Is this new configuration? What changed?

Did you check the switches (hubs), cables?

Can you post here the result of

ipconfig /all

from your working PC (the PC that can ping everything) and PC that can't
ping the working PC.

--
Mike
Microsoft MVP - Windows Security

"John McC" <(E-Mail Removed)> wrote in message
news:763E636C-8B07-4526-81EC-(E-Mail Removed)...
>I have an SBS 2000 network using static IP addressing.
> One PC has full network access to other resources and can ping other
> machines, the server, default gateway, etc.
> The problem is that no other machine or the server can ping this PC - the
> request is timed out.
> Due to this I cannot remotely manage this PC as the server cannot see it.
> --
> John

Do you have the windows firewall on and configured to block incoming
pings and other ports? How about a hardware firewall router? Do you
ping the names of other machines or their IP address's? Is DNS
configured and working correctly?

As the previous poster suggested, try the ipconfig /all
Check your settings.

On Fri, 28 Apr 2006 04:27:01 -0700, John McC
<(E-Mail Removed)> wrote:

>I have an SBS 2000 network using static IP addressing.
>One PC has full network access to other resources and can ping other
>machines, the server, default gateway, etc.
>The problem is that no other machine or the server can ping this PC - the
>request is timed out.
>Due to this I cannot remotely manage this PC as the server cannot see it.

Miha,

The system did work previously and all hubs, cables, etc are fine.

Below is the result from another fully recognised PC when trying to contact
the faulty PC

Z:\>ping traffic1

Pinging traffic1.ExpressParcels.local [192.168.16.31] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.16.31:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Z:\>ping 192.168.16.31

Pinging 192.168.16.31 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.16.31:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Z:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : TESTPARCELS
Primary Dns Suffix . . . . . . . : ExpressParcels.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ExpressParcels.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-11-09-3D-43-E8
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.16.85
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.16.254
DNS Servers . . . . . . . . . . . : 192.168.16.2

Z:\>

This is the result from the faulty PC - the only difference being the
additional network card

Z:\>ping testparcels

Pinging TESTPARCELS.ExpressParcels.local [192.168.16.85] with 32 bytes of
data:

Reply from 192.168.16.85: bytes=32 time<1ms TTL=128
Reply from 192.168.16.85: bytes=32 time<1ms TTL=128
Reply from 192.168.16.85: bytes=32 time<1ms TTL=128
Reply from 192.168.16.85: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.16.85:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Z:\>ping 192.168/16.2
Ping request could not find host 192.168/16.2. Please check the name and try
aga
in.

Z:\>ping 192.168.16.2

Pinging 192.168.16.2 with 32 bytes of data:

Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.16.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Z:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : TRAFFIC1
Primary Dns Suffix . . . . . . . : ExpressParcels.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ExpressParcels.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit
Cont
roller
Physical Address. . . . . . . . . : 00-14-22-31-2A-56
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.16.31
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.16.254
DNS Servers . . . . . . . . . . . : 192.168.16.2

Ethernet adapter {9AFD4B60-04E1-4A34-90C7-B45615424031}:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Check Point Virtual Network
Adapter
For SecureClient - Packet Scheduler Miniport
Physical Address. . . . . . . . . : 54-55-43-44-52-03

Z:\>
--
I don't know if any of this will help but thanks anyway

John


"Miha Pihler [MVP]" wrote:

> Hi John,
>
> did this work at some time? Is this new configuration? What changed?
>
> Did you check the switches (hubs), cables?
>
> Can you post here the result of
>
> ipconfig /all
>
> from your working PC (the PC that can ping everything) and PC that can't
> ping the working PC.
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "John McC" <(E-Mail Removed)> wrote in message
> news:763E636C-8B07-4526-81EC-(E-Mail Removed)...
> >I have an SBS 2000 network using static IP addressing.
> > One PC has full network access to other resources and can ping other
> > machines, the server, default gateway, etc.
> > The problem is that no other machine or the server can ping this PC - the
> > request is timed out.
> > Due to this I cannot remotely manage this PC as the server cannot see it.
> > --
> > John
>
>
>

Hi,

Sorry for delay. Did you manage to solve this problem or do you still need
assistance with this?

--
Mike
Microsoft MVP - Windows Security

"John McC" <(E-Mail Removed)> wrote in message
news:AD295F75-FCA2-4D13-956D-(E-Mail Removed)...
> Miha,
>
> The system did work previously and all hubs, cables, etc are fine.
>
> Below is the result from another fully recognised PC when trying to
> contact
> the faulty PC
>
> Z:\>ping traffic1
>
> Pinging traffic1.ExpressParcels.local [192.168.16.31] with 32 bytes of
> data:
>
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
>
> Ping statistics for 192.168.16.31:
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>
> Z:\>ping 192.168.16.31
>
> Pinging 192.168.16.31 with 32 bytes of data:
>
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
>
> Ping statistics for 192.168.16.31:
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>
> Z:\>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : TESTPARCELS
> Primary Dns Suffix . . . . . . . : ExpressParcels.local
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : ExpressParcels.local
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet
> Adapter
> Physical Address. . . . . . . . . : 00-11-09-3D-43-E8
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.16.85
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.16.254
> DNS Servers . . . . . . . . . . . : 192.168.16.2
>
> Z:\>
>
> This is the result from the faulty PC - the only difference being the
> additional network card
>
> Z:\>ping testparcels
>
> Pinging TESTPARCELS.ExpressParcels.local [192.168.16.85] with 32 bytes of
> data:
>
> Reply from 192.168.16.85: bytes=32 time<1ms TTL=128
> Reply from 192.168.16.85: bytes=32 time<1ms TTL=128
> Reply from 192.168.16.85: bytes=32 time<1ms TTL=128
> Reply from 192.168.16.85: bytes=32 time<1ms TTL=128
>
> Ping statistics for 192.168.16.85:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> Z:\>ping 192.168/16.2
> Ping request could not find host 192.168/16.2. Please check the name and
> try
> aga
> in.
>
> Z:\>ping 192.168.16.2
>
> Pinging 192.168.16.2 with 32 bytes of data:
>
> Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
> Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
> Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
> Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
>
> Ping statistics for 192.168.16.2:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> Z:\>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : TRAFFIC1
> Primary Dns Suffix . . . . . . . : ExpressParcels.local
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : ExpressParcels.local
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit
> Cont
> roller
> Physical Address. . . . . . . . . : 00-14-22-31-2A-56
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.16.31
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.16.254
> DNS Servers . . . . . . . . . . . : 192.168.16.2
>
> Ethernet adapter {9AFD4B60-04E1-4A34-90C7-B45615424031}:
>
> Media State . . . . . . . . . . . : Media disconnected
> Description . . . . . . . . . . . : Check Point Virtual Network
> Adapter
> For SecureClient - Packet Scheduler Miniport
> Physical Address. . . . . . . . . : 54-55-43-44-52-03
>
> Z:\>
> --
> I don't know if any of this will help but thanks anyway
>
> John
>
>
> "Miha Pihler [MVP]" wrote:
>
>> Hi John,
>>
>> did this work at some time? Is this new configuration? What changed?
>>
>> Did you check the switches (hubs), cables?
>>
>> Can you post here the result of
>>
>> ipconfig /all
>>
>> from your working PC (the PC that can ping everything) and PC that can't
>> ping the working PC.
>>
>> --
>> Mike
>> Microsoft MVP - Windows Security
>>
>> "John McC" <(E-Mail Removed)> wrote in message
>> news:763E636C-8B07-4526-81EC-(E-Mail Removed)...
>> >I have an SBS 2000 network using static IP addressing.
>> > One PC has full network access to other resources and can ping other
>> > machines, the server, default gateway, etc.
>> > The problem is that no other machine or the server can ping this PC -
>> > the
>> > request is timed out.
>> > Due to this I cannot remotely manage this PC as the server cannot see
>> > it.
>> > --
>> > John
>>
>>
>>