Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
2 xp machines- #2 cant ping #1 1
- Thread starter karmel
- Start date
- Thread starter
- #2
-
1
- #3
Are there two routers, or just one?
Is DHCP enabled on the routers, or are you just using static IPs, or both?
Why are you using Netbui?
See if this is close:
Modem --> D-Link Router -> PCs
There are two computers.
Both use XP.
DHCP is enabled on the router.
Netbui is the client protocol.
TCP/IP is configured with static IPs on both machines.
PC #2 cannot ping PC #1.
My guess is that either:
. PC #2 has a bad cable, or bad NIC, or both;
. They were inadvertantly given different subnets.
Could you post the results of IPCONFIG /all for both machines?
Is DHCP enabled on the routers, or are you just using static IPs, or both?
Why are you using Netbui?
See if this is close:
Modem --> D-Link Router -> PCs
There are two computers.
Both use XP.
DHCP is enabled on the router.
Netbui is the client protocol.
TCP/IP is configured with static IPs on both machines.
PC #2 cannot ping PC #1.
My guess is that either:
. PC #2 has a bad cable, or bad NIC, or both;
. They were inadvertantly given different subnets.
Could you post the results of IPCONFIG /all for both machines?
- Thread starter
- #4
-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI TX NIC
(3C905B-TX)
Physical Address. . . . . . . . . : 00-10-5A-A7-94-3F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.125
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 204.60.203.179
66.73.20.40
i have netbui because i saw in one of these threads to do that.
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI TX NIC
(3C905B-TX)
Physical Address. . . . . . . . . : 00-10-5A-A7-94-3F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.125
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 204.60.203.179
66.73.20.40
i have netbui because i saw in one of these threads to do that.
- Thread starter
- #5
computer#1
PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-03-47- Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 204.60.203.179
66.73.20.40
Primary WINS Server . . . . . . . : 192.168.3.1
PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-03-47- Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 204.60.203.179
66.73.20.40
Primary WINS Server . . . . . . . : 192.168.3.1
- Thread starter
- #7
It is not a configuration issue with the router. That is not to say every setting is correct, but the router DHCP is assigning addresses in the same subnet, and the Gateway and DNS addresses look fine on both computers.
If the only problem is the lack of ping I suspect it might have something to do with the VPN on PC #1. Disable the VPN and ping again.
It also could be that the entry in the WINS server is wrong. You are using DHCP addressing and it looks like at least PC #2 has been reset 24 times within the lease interval of the DHCP server.
You could try pinging by name; e.g. ping \\computer2
Don't worry about the ping as long as your Internet Access works, and your Network works.
If the only problem is the lack of ping I suspect it might have something to do with the VPN on PC #1. Disable the VPN and ping again.
It also could be that the entry in the WINS server is wrong. You are using DHCP addressing and it looks like at least PC #2 has been reset 24 times within the lease interval of the DHCP server.
You could try pinging by name; e.g. ping \\computer2
Don't worry about the ping as long as your Internet Access works, and your Network works.
- Thread starter
- #9
karmel,
Then on both computers, right-click the tray icon for your network connection, Properties, right click Network Connection, Properties, highlight TCP/IP, Advanced, WINS, and enable Netbios over TCP/IP.
It may take several minutes for both computers to appear in Network Neighborhood.
Then on both computers, right-click the tray icon for your network connection, Properties, right click Network Connection, Properties, highlight TCP/IP, Advanced, WINS, and enable Netbios over TCP/IP.
It may take several minutes for both computers to appear in Network Neighborhood.
- Thread starter
- #11
1. Both computers need to have shared something, a folder, and/or a printer.
2. Both computers need the Guest account turned on in Control Panel, User Accounts
3. Both computers need to be made members of a Workgroup, with different computer names but identical Workgroup name.
4. When prompted at startup, you must hit enter or Okay to login. Hitting Cancel or the Escape key will deny you access to the network.
5. It is generally recommended that User #1 add User #2 as a user on the Computer, and User #2 do the same for User #1 on his computer.
Once this is set on each machine in My Network Places hit View, Refresh. It can take several minutes to fully populate the Neighborhood display as the Computer Browsing Service on each computer discovers the existence of the other.
Once discovered their existence will be persistant.
Whle you do not need Netbui in this setting, there are some tricks to setting it up properly for Windows XP. One idea is to use the Win2k version of Netbui under XP. There are other tricks. Please see this article for a discussion:
2. Both computers need the Guest account turned on in Control Panel, User Accounts
3. Both computers need to be made members of a Workgroup, with different computer names but identical Workgroup name.
4. When prompted at startup, you must hit enter or Okay to login. Hitting Cancel or the Escape key will deny you access to the network.
5. It is generally recommended that User #1 add User #2 as a user on the Computer, and User #2 do the same for User #1 on his computer.
Once this is set on each machine in My Network Places hit View, Refresh. It can take several minutes to fully populate the Neighborhood display as the Computer Browsing Service on each computer discovers the existence of the other.
Once discovered their existence will be persistant.
Whle you do not need Netbui in this setting, there are some tricks to setting it up properly for Windows XP. One idea is to use the Win2k version of Netbui under XP. There are other tricks. Please see this article for a discussion:
- Thread starter
- #13
Forgive me for resurrecting this thread but I'm having the same issue. I have followed all the steps outlined by bcastner above without success.
I can ping the IP and the computername of PC#2 (a laptop) from PC#1 (a desktop), and can view PC#2's shared folders using net view and nbtstat. However, I am unable to ping the desktop from the laptop. The network had worked fine until I took the laptop on the road last weekend. I made no connections with the laptop while away but when I plugged it back in, it wouldn't connect. I appreciate any advice.
I can ping the IP and the computername of PC#2 (a laptop) from PC#1 (a desktop), and can view PC#2's shared folders using net view and nbtstat. However, I am unable to ping the desktop from the laptop. The network had worked fine until I took the laptop on the road last weekend. I made no connections with the laptop while away but when I plugged it back in, it wouldn't connect. I appreciate any advice.
I assume you are pinging the desktop from the laptop because you cannot see shares either, so it is not just a ping issue.
Likely what happened while you were away is something was changed on the desktop.
Your basic connectivity seems fine. The only other possibility is a firewall. This week someone complained of exactly this because they had installed an Anti-virus software and unknown to them it includes a firewall. The program was PC-Illan. Has this or any other firewall product or anti-virus been either installed or upgraded on the desktop?
Likely what happened while you were away is something was changed on the desktop.
Your basic connectivity seems fine. The only other possibility is a firewall. This week someone complained of exactly this because they had installed an Anti-virus software and unknown to them it includes a firewall. The program was PC-Illan. Has this or any other firewall product or anti-virus been either installed or upgraded on the desktop?
Thanks for the response. You are correct that I cannot see shares or otherwise detect the desktop from the laptop. Nothing changed on the desktop that I was aware of (no one else using it). I had been using Zone Alarm without any difficulties. When this trouble began, I uninstalled Zone Alarm (using the info posted on the ZoneLabs site) but that didn't correct the problem.
Agree that it seemed like a firewall was still in place since all I was getting was basically a one-way connection. Neither machine had Windows ICF running. In frustration, I finally installed NetBEUI and that allowed full connectivity between the two. It's very puzzling, however.
Agree that it seemed like a firewall was still in place since all I was getting was basically a one-way connection. Neither machine had Windows ICF running. In frustration, I finally installed NetBEUI and that allowed full connectivity between the two. It's very puzzling, however.
There are some puzzling things about mixed-OS settings. Using Netbui is fine as far as I am concerned. There may even be advantages. The only question I have about Netbui is its suitability for wireless clients. A good discussion of Netbui, including the suggestion and a link for using the Win2k Netbui service instead of the XP one is in this article by Scott Finnie:
- Status