Computer not responding to ping

[Guest]

Four computers on an ethernet (cat5) through a LinkSys hub, three of which are XP Pro. Machines are configured for Microsoft Client and TCP/IP. New computer (Dell Dimension 4600) cannot be reached from other machines. It can read Shareddocs on other xp machine. Dell can ping any of the machines on the net and get prompt response but cannot be pinged from those machines and will not respond to its own url ping. When pinged the error "timed out" is reported. When attempting to reach the Dell from one of the other XP machines a message saying "the Dell cannot be reached and .... may not have access" is reported
I believe that the fire wall was once set but has been disabled.
Any suggestions would be appreciated
W Adams

 

[Chuck]

Four computers on an ethernet (cat5) through a LinkSys hub, three of which are XP Pro. Machines are configured for Microsoft Client and TCP/IP. New computer (Dell Dimension 4600) cannot be reached from other machines. It can read Shareddocs on other xp machine. Dell can ping any of the machines on the net and get prompt response but cannot be pinged from those machines and will not respond to its own url ping. When pinged the error "timed out" is reported. When attempting to reach the Dell from one of the other XP machines a message saying "the Dell cannot be reached and .... may not have access" is reported.
I believe that the fire wall was once set but has been disabled.
Any suggestions would be appreciated.
W Adams

What firewall was once set and then disabled? Some firewalls don't disable
properly.

On any XP Pro system, check to see if Simple File Sharing (Control Panel -
Folder Options - View - Advanced settings) is enabled or disabled. With XP Pro,
you need to have the SFS settings set properly on each computer.

If SFS is disabled, check the Local Security Policy (Control Panel -
Administrative Tools). Under Local Policies - Security Options, look at
"Network access: Sharing and security model", and ensure it's set to "Classic -
local users authenticate as themselves".

If you set the Local Security Policy to "Guest only", make sure that the Guest
account is enabled, and has an identical, non-blank, password on all computers.
If "Classic", setup and use a common account with identical, non-blank, password
on all computers.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[C4jun]

If you mean the Internet Connection Firewall (built into XP)....
Open the control panel...
Click "network connections"...
If the firewall is on ther should be a lock on the connection icon...
If there is a lock...
Right click the connection and select properties...
Click the advanced tab...
Uncheck the firewall check box.

Hope this helps.

C4jun

which are XP Pro. Machines are configured for Microsoft Client and TCP/IP.
New computer (Dell Dimension 4600) cannot be reached from other machines.
It can read Shareddocs on other xp machine. Dell can ping any of the
machines on the net and get prompt response but cannot be pinged from those
machines and will not respond to its own url ping. When pinged the error
"timed out" is reported. When attempting to reach the Dell from one of the
other XP machines a message saying "the Dell cannot be reached and .... may
not have access" is reported.

 

[Guest]

Sorry guys, I tried all of the suggesions and still no ability to communicate from the other computers to the Dell. Any more thoughts?

 

[Chuck]

Sorry guys, I tried all of the suggesions and still no ability to communicate from the other computers to the Dell. Any more thoughts?

OK, don't give up. Let's do a bit of analysis.

Please provide ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.
Label each ipconfig with name and version of operating system, and identify the
problem computer also.

From the problem computer, and from one good computer, verify connectivity:
1) Ping the other by name.
2) Ping the other by ip address.
3) Ping itself by name.
4) Ping itself by ip address.
5) Ping 127.0.0.1.
6) Ping the router.
Report precise errors from of each of 12 pings.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Guest]

----- Chuck wrote: ----

On Tue, 18 May 2004 05:16:11 -0700, "W Adams

Sorry guys, I tried all of the suggesions and still no ability to communicate from the other computers to the Dell. Any more thoughts

OK, don't give up. Let's do a bit of analysis

Please provide ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the comman
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post
Label each ipconfig with name and version of operating system, and identify th
problem computer also

From the problem computer, and from one good computer, verify connectivity
1) Ping the other by name
2) Ping the other by ip address
3) Ping itself by name
4) Ping itself by ip address
5) Ping 127.0.0.1
6) Ping the router
Report precise errors from of each of 12 pings

Cheers
Chuc
Paranoia comes from experience - and is not necessarily a bad thing

Chuck,
Thanks for your help
Since that machine is not on the net I have copied the info you asked for.

Host Name: Managemen
Primary DNS suffix: blan
Node type: Mixe
IP Routing Enabled: N
IP Proxy Enabled: N

Ether Net Adapter Local Area Connectio

Connect specdific DNS Suffix: mshome.ne
Description: Intel(R) Pro/100 VE Network Connectio
Physical Address: 00-0C-F1-D1-3D-2
Dhcp Enabled: ye
Auto Config Enabled: ye
IP Address: 192.168.0.3
Sub Mask : 255.255.255.
Default Gateway: 192.168.0.
DHCP Server 192.168.0.
DNS Server: 192.168.0.
Lease Obtained: Tues, May 18:47:19 A
Lease Expires : Tues, May 25:47:19 A

 

[Chuck]

----- Chuck wrote: -----



OK, don't give up. Let's do a bit of analysis.

Please provide ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.
Label each ipconfig with name and version of operating system, and identify the
problem computer also.

From the problem computer, and from one good computer, verify connectivity:
1) Ping the other by name.
2) Ping the other by ip address.
3) Ping itself by name.
4) Ping itself by ip address.
5) Ping 127.0.0.1.
6) Ping the router.
Report precise errors from of each of 12 pings.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

Chuck,
Thanks for your help.
Since that machine is not on the net I have copied the info you asked for.

Host Name: Management
Primary DNS suffix: blank
Node type: Mixed
IP Routing Enabled: NO
IP Proxy Enabled: NO

Ether Net Adapter Local Area Connection

Connect specdific DNS Suffix: mshome.net
Description: Intel(R) Pro/100 VE Network Connection
Physical Address: 00-0C-F1-D1-3D-2C
Dhcp Enabled: yes
Auto Config Enabled: yes
IP Address: 192.168.0.34
Sub Mask : 255.255.255.0
Default Gateway: 192.168.0.1
DHCP Server 192.168.0.1
DNS Server: 192.168.0.1
Lease Obtained: Tues, May 18:47:19 AM
Lease Expires : Tues, May 25:47:19 AM

That's a good start. How about ipconfig data for the other computers?

And can you please run the pings as I suggested? It's a lot easier to see the
problem when all of the symptoms are organised.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Chuck]

OK so here are all the results you asked for:

Results from Dell (offender)


Tests made on Dell (problem computer)


Windows IP Configuration



Host Name . . . . . . . . . . . . : MANAGEMENT

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Mixed

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : mshome.net

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection

Physical Address. . . . . . . . . : 00-0C-F1-D1-3D-2C

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.34

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

Lease Obtained. . . . . . . . . . : Tuesday, May 18, 2004 11:52:19 AM

Lease Expires . . . . . . . . . . : Tuesday, May 25, 2004 11:52:19 A


DeLL Computer is named Management

From Dell Ping Management
Enter: ping management
Pinging MANAGEMENT [192.168.0.03] with 32 bytes of data:

Request timed out.
Requist timed out.
Request timed out.
request timed out.

Ping statistics for 192.168.0.93:
Packest: Sent = 4, Received = 0, Lost = 4 <100% loss>

From Dell Ping 192.168.0.93

Pinging 192.168.0.93 with 32 byts of data:

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

Ping statistics for 192.168.0.93:

Pinging statistics for 192.168.0.93:
Packest: Sent = 4, Received = 0, Lost = 4 <100% loss>

Ping 127.0.0.1

Pinging 127.0.0.1 with bytes=32 of data:
Pinging 127.0.0.1 with bytes=32 of data:
Pinging 127.0.0.1 with bytes=32 of data:
Pinging 127.0.0.1 with bytes=32 of data:

Ping statistics for 127.0.0.1:

Pinging statsistics for 127.0.0.1:
Packests: Sent = 4, Received = 4 Lost = 0 <0% loss>,
Approximate round trip time in milli-seconds
Minimum = 0ms. Maximum = 0ms, Average = 0 ms

Response to nestat

Proto Local Address Foreign Address State
TCP MANAGEMENT:1027 localhost:1151 ESTABLISHED
TCP MANAGEMENT:1151 localhost:1027 ESTABLISHEDTCP MANAGEMENT:1152 67-114-52-34.deploy.akamaitechnologies.net:http ESTABLISHED

Ping LAPTOP FROM DELL

Pinging LAPTOP.mshome.net [192.168.0.125] with 32 bytes of data:

Reply from 192.168.0.125: bytes=32 TIME<1ms TLL=128
Reply from 192.168.0.125: bytes=32 TIME<1ms TLL=128
Reply from 192.168.0.125: bytes=32 TIME<1ms TLL=128
Reply from 192.168.0.125: bytes=32 TIME<1ms TLL=128

Pinging statsistics for 192.168.0.125:
Packests: Sent = 4, Received = 4 Lost = 0 <0% loss>,
Approximate round trip time in milli-seconds
Minimum = 0ms. Maximum = 0ms, Average = 0 ms


And for Sony Laptop brought in to use in test.

Note: LAPTOP is a Sony PCG R505 running XP Pro that I brought in and had no trouble getting on the net.


Windows IP Configuration



Host Name . . . . . . . . . . . . : LAPTOP

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : Yes



Ethernet adapter Local Area Connection 2:



Connection-specific DNS Suffix . : mshome.net

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection

Physical Address. . . . . . . . . : 08-00-46-4F-06-3E

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.115

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

Lease Obtained. . . . . . . . . . : Tuesday, May 18, 2004 11:47:01 AM

Lease Expires . . . . . . . . . . : Tuesday, May 25, 2004 11:47:01 AM

Ping tests

ping LAPTOP

Pinging LAPTOP [192.168.0.125] with 32 bytes of data:

Reply form 192.168.0.125: bytes=32 time<1ms TTL=128
Reply form 192.168.0.125: bytes=32 time<1ms TTL=128
Reply form 192.168.0.125: bytes=32 time<1ms TTL=128
Reply form 192.168.0.125: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.125:
Packets: Sent = 4, Received = 4, Lost = 0 <0% loss>
Approximate round trip times in milli-seconds:
Minimm - 0 ms, Maximum = 0 ms, Average = 0ms

Ping 192.168.0.125

Pinging 192.168.0.125 with 32 bytes of data:

Reply form 192.168.0.125: bytes=32 time<1ms TTL=128
Reply form 192.168.0.125: bytes=32 time<1ms TTL=128
Reply form 192.168.0.125: bytes=32 time<1ms TTL=128
Reply form 192.168.0.125: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.125:
Packets: Sent = 4, Received = 4, Lost = 0 <0% loss>
Approximate round trip times in milli-seconds:
Minimm - 0 ms, Maximum = 0 ms, Average = 0ms

Ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:

Reply form 127.0.0.1: bytes=32 time<1ms TTL=128
Reply form 127.0.0.1: bytes=32 time<1ms TTL=128
Reply form 127.0.0.1: bytes=32 time<1ms TTL=128
Reply form 127.0.0.1: bytes=32 time<1ms TTL=128


Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 <0% loss>
Approximate round trip times in milli-seconds:
Minimm - 0 ms, Maximum = 0 ms, Average = 0ms

There is no router. We are using a Hub.

Response from netstat:

Active Connections

Proto Local Address Foreign Address State
TCP LAPTOP:3032 localhost:3033 Established
TCP LAPTOP:3033 localhost:3032 Established
TCP LAPTOP:3075 SCORE1.mshome.net:2869 CLOSE_WAIT
TCP LAPTOP:5000 SCORE1:mshome.net.3770 Established

Note: The other XP Pro computer on the net is SCORE1

Ping MANAGEMENT from LAPTOP

Pinging MANAGEMENT.mshome.net [192.168.0.93] with 32 bytes of data:

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

Ping statistics for 192:168.0.93:
Packets: Sent = 4, Received = 0, Lost = 4 <100% loss>,

Ping SCORE1 from LAPTOP

Pinging SCORE1.mshome.net [192.168.0.1] with 32 byets of data:

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

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0, <0% loss>
Approximate round trip timnes in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0 ms

As I noted we do not have a router but use a Lincsys 5 port hub.

Hope this gives you something to work on.

WAdams

I would like you to start by describing your network in detail - what devices
(make / model) are connected where.

You have a very interesting set of diagnostics above.

Both Laptop and Management appear to be getting DHCP, DNS, and internet (Default
Gateway) from something with an ip address 192.168.0.1. That's not a hub - hubs
have no DHCP, DNS, or Gateway ability.

Is it possible that you have more than one DHCP server on your network? Look at
the ipconfig listings for Laptop and Management. Then look at the pings. You
have different ip addresses everywhere. Is Management 192.168.0.115,
192.168.0.03, or 192.168.0.93? Is Laptop 192.168.0.115 or 192.168.0.125?

There's your problem, anyway. NBT (NetBIOS Over TCP/IP) uses IP Addresses to
access data shared thru NetBIOS (named shares). If a computer uses one ip
address to attach to the network, but the name resolver associates that computer
name with another address, you have a computer that can access shares on other
computers, but can't be accessed by those computers.

Here's a useful tool - Softperfect Network Scanner, free, from
<http://www.softperfect.com/>. Netscan will scan your subnet, ip by ip,
identify which addresses respond, resolve each address, and generate a report.
And finally export the report to a text file. If you were to do that from both
Management and Laptop, and compare the two, you might find some interesting
clues.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.