|
windows
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Pinging problem from client PCsI have a small peer-to-peer network of three computers. All computers
are XP (SP2). >From the two client PCs, I can ping sites by IP number but not by name. What settings do I have to adjust (and on which PCs?) so that I canping correctly by both IP number and name? Thanks in anticitpation. TM trevormidg***@ntlworld.com wrote:
> I have a small peer-to-peer network of three computers. All computers If you are talking about pinging in terms of the Internet and not the> are XP (SP2). > >>From the two client PCs, I can ping sites by IP number but not by >>name. > > > What settings do I have to adjust (and on which PCs?) so that I can > ping correctly by both IP number and name? > > Thanks in anticitpation. lan, if you can ping/connect only with IP addresses and not human-readable names then your DNS is set incorrectly or there is a problem with the DNS server. If you are talking about connectivity internally between lan computers, you need to configure any firewalls to allow the lan IP range as trusted. Malke I'm talking about pinging in terms of the Internet and not the LAN - TM
On 30 Sep 2006 07:53:13 -0700, trevormidg***@ntlworld.com wrote:
>I have a small peer-to-peer network of three computers. All computers Start by looking at 2 possibilities - the NetBT setting, and node type.>are XP (SP2). > >>From the two client PCs, I can ping sites by IP number but not by name. > > >What settings do I have to adjust (and on which PCs?) so that I can >ping correctly by both IP number and name? > >Thanks in anticitpation. > >TM <http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html> http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html <http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html> http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html Or post "browstat status" and "ipconfig /all", from each computer, so we can diagnose the problem. Read this article, and linked articles, and follow instructions precisely (download browstat!): <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp> http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp -- Cheers, Chuck, MS-MVP [Windows - Networking] http://nitecruzr.blogspot.com/ Paranoia is not a problem, when it's a normal response from experience. My email is AT DOT actual address pchuck mvps org. ....or post "browstat status" and "ipconfig /all", from each computer...
Don't mean to be difficult, but when I run "ipconfig /all", I just get a black flash of screen, then it's gone! Nothing to see, nothing to save. What am I doing wrong? TM Sorry Chuck, forget this last post re ipconfig! I hadn't read your site
closely enough! I'll get back when I have all the details. Cheers - TM Chuck - sorry for the delay.
These are the ipconfig /all reports from my three computers. I'm having some difficulty getting Browstat to perform - I suspect I'm doing something wrong in "Using The Path" because I am getting the "'browstat' is not recognized as an internal or external command...". I'll keep working on that, but I thought that at least the ipconfig outputs might give you some indicator as to my problem. Cheers - TM **************************** Host Computer - Windows IP Configuration Host Name . . . . . . . . . . . . : BACK-COMPUTER Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC Physical Address. . . . . . . . . : 00-E0-20-00-F1-70 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 86.11.10.148 Subnet Mask . . . . . . . . . . . : 255.255.252.0 Default Gateway . . . . . . . . . : 86.11.8.1 DHCP Server . . . . . . . . . . . : 62.252.64.22 DNS Servers . . . . . . . . . . . : 194.168.8.100 194.168.4.100 NetBIOS over Tcpip. . . . . . . . : Disabled Lease Obtained. . . . . . . . . . : 01 October 2006 12:43:00 Lease Expires . . . . . . . . . . : 02 October 2006 13:16:22 Ethernet adapter Wireless Network Connection 3: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) AnyPoint(TM) Wireless II Network 11Mbps USB Adapter #2 Physical Address. . . . . . . . . : 00-90-4B-05-5F-D9 Dhcp Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.0.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 DNS Servers . . . . . . . . . . . : 192.168.0.1 Client #1 Computer Windows IP Configuration Host Name . . . . . . . . . . . . : FRONT-COMPUTER2 Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Mixed IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Wireless Network Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) AnyPoint(TM) Wireless II Network 11Mbps USB Adapter Physical Address. . . . . . . . . : 00-90-4B-05-51-B5 Dhcp Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.0.11 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : fe80::290:4bff:fe05:51b5%5 Default Gateway . . . . . . . . . : 192.168.0.1 DNS Servers . . . . . . . . . . . : 192.168.0.1 fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF Dhcp Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%4 Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter Automatic Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface Physical Address. . . . . . . . . : C0-A8-00-0B Dhcp Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.11%2 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Disabled Client #2 Computer Windows IP Configuration Host Name . . . . . . . . . . . . : Tinkerbell Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Mixed IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : mshome.net Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Controller Physical Address. . . . . . . . . : 00-C0-9F-8A-C4-F7 Ethernet adapter Wireless Network Connection: Connection-specific DNS Suffix . : mshome.net Description . . . . . . . . . . . : INPROCOMM IPN2220 Wireless LAN Card Physical Address. . . . . . . . . : 00-14-A4-06-53-B9 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.0.28 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. . . . . . . . . . : 26 September 2006 15:52:58 Lease Expires . . . . . . . . . . : 03 October 2006 15:52:58 On 1 Oct 2006 07:34:31 -0700, trevormidg***@ntlworld.com wrote:
>Chuck - sorry for the delay. <SNIP>> >These are the ipconfig /all reports from my three computers. > >I'm having some difficulty getting Browstat to perform - I suspect >I'm doing something wrong in "Using The Path" because I am >getting the "'browstat' is not recognized as an internal or external >command...". > >I'll keep working on that, but I thought that at least the ipconfig >outputs might give you some indicator as to my problem. Hi Trevor, OK, a couple interesting items. Three connections specify 192.168.0.1 as the DNS server (relay). Depending upon how the (router?) is setup, that may or may not work well. For that, we need to know what servers it's relaying the requests to. Then one connection uses two servers directly ("194.168.8.100" / "194.168.4.100"). This discrepancy could cause a variation. Also, FRONT-COMPUTER2 has IPV6 ("Teredo Tunneling"). I've known for that to cause various problems, generally with local connectivity. It's your choice whether to keep it. <http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html> http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html -- Cheers, Chuck, MS-MVP [Windows - Networking] http://nitecruzr.blogspot.com/ Paranoia is not a problem, when it's a normal response from experience. My email is AT DOT actual address pchuck mvps org. Chuck - Got 'em! Here are the browstat results for my three
computers. (BTW, I don't have a router as such; straight peer-to-peer with Back Computer being my gateway to the net.) All the best, and thanks - TM *********************** Host Computer Status for domain MSHOME on transport \Device\NwlnkNb Browsing is active on domain. Master name cannot be determined from GetAdapterStatus. Using \\BACK-COMPUT ER Master browser is running build 2600 1 backup servers retrieved from master BACK-COMPUTER \\BACK-COMPUTER There are 1 servers in domain MSHOME on transport \Device\NwlnkNb There are 1 domains in domain MSHOME on transport \Device\NwlnkNb Status for domain MSHOME on transport \Device\NetBT_Tcpip_{97CCFA9C-6EA0-45C0-82 DA-4C54B936AEEA} Browsing is active on domain. Master browser name is: BACK-COMPUTER Master browser is running build 2600 1 backup servers retrieved from master BACK-COMPUTER \\BACK-COMPUTER There are 3 servers in domain MSHOME on transport \Device\NetBT_Tcpip_{97CCF A9C-6EA0-45C0-82DA-4C54B936AEEA} There are 1 domains in domain MSHOME on transport \Device\NetBT_Tcpip_{97CCF A9C-6EA0-45C0-82DA-4C54B936AEEA} Status for domain MSHOME on transport \Device\NwlnkIpx Browsing is active on domain. Master name cannot be determined from GetAdapterStatus. Using \\BACK-COMPUT ER Master browser is running build 2600 1 backup servers retrieved from master BACK-COMPUTER \\BACK-COMPUTER There are 1 servers in domain MSHOME on transport \Device\NwlnkIpx There are 1 domains in domain MSHOME on transport \Device\NwlnkIpx Client #2 Computer Status for domain MSHOME on transport \Device\NetBT_Tcpip_{F447936F-0509-4DC3-89 4A-B50FE411A02D} Browsing is active on domain. Master browser name is: BACK-COMPUTER Could not connect to registry, error = 53 Unable to determine build of br owser master: 53 \\\\BACK-COMPUTER . Version:05.01 Flags: 51203 NT POTENTIAL MASTER 1 backup servers retrieved from master BACK-COMPUTER \\BACK-COMPUTER There are 3 servers in domain MSHOME on transport \Device\NetBT_Tcpip_{F4479 36F-0509-4DC3-894A-B50FE411A02D} There are 1 domains in domain MSHOME on transport \Device\NetBT_Tcpip_{F4479 36F-0509-4DC3-894A-B50FE411A02D} Client #3 Computer Status for domain MSHOME on transport \Device\NetBT_Tcpip_{DBADB2BF-E63C-47FC-9F 12-0A52AE98FF59} Browsing is active on domain. Master browser name is: BACK-COMPUTER Could not connect to registry, error = 53 Unable to determine build of br owser master: 53 \\\\BACK-COMPUTER . Version:05.01 Flags: 51203 NT POTENTIAL MASTER 1 backup servers retrieved from master BACK-COMPUTER \\BACK-COMPUTER There are 3 servers in domain MSHOME on transport \Device\NetBT_Tcpip_{DBADB 2BF-E63C-47FC-9F12-0A52AE98FF59} There are 1 domains in domain MSHOME on transport \Device\NetBT_Tcpip_{DBADB 2BF-E63C-47FC-9F12-0A52AE98FF59} On 1 Oct 2006 09:39:05 -0700, trevormidg***@ntlworld.com wrote:
Show quoteHide quote >Chuck - Got 'em! Here are the browstat results for my three OK, Trevor,>computers. > >(BTW, I don't have a router as such; straight peer-to-peer with Back >Computer being my gateway to the net.) > >All the best, and thanks - > > >TM > > >*********************** > > >Host Computer > > >Status for domain MSHOME on transport \Device\NwlnkNb > Browsing is active on domain. > Master name cannot be determined from GetAdapterStatus. Using >\\BACK-COMPUT >ER > Master browser is running build 2600 > 1 backup servers retrieved from master BACK-COMPUTER > \\BACK-COMPUTER > There are 1 servers in domain MSHOME on transport \Device\NwlnkNb > There are 1 domains in domain MSHOME on transport \Device\NwlnkNb > > >Status for domain MSHOME on transport >\Device\NetBT_Tcpip_{97CCFA9C-6EA0-45C0-82 >DA-4C54B936AEEA} > Browsing is active on domain. > Master browser name is: BACK-COMPUTER > Master browser is running build 2600 > 1 backup servers retrieved from master BACK-COMPUTER > \\BACK-COMPUTER > There are 3 servers in domain MSHOME on transport >\Device\NetBT_Tcpip_{97CCF >A9C-6EA0-45C0-82DA-4C54B936AEEA} > There are 1 domains in domain MSHOME on transport >\Device\NetBT_Tcpip_{97CCF >A9C-6EA0-45C0-82DA-4C54B936AEEA} > > >Status for domain MSHOME on transport \Device\NwlnkIpx > Browsing is active on domain. > Master name cannot be determined from GetAdapterStatus. Using >\\BACK-COMPUT >ER > Master browser is running build 2600 > 1 backup servers retrieved from master BACK-COMPUTER > \\BACK-COMPUTER > There are 1 servers in domain MSHOME on transport \Device\NwlnkIpx > There are 1 domains in domain MSHOME on transport \Device\NwlnkIpx > > >Client #2 Computer > >Status for domain MSHOME on transport >\Device\NetBT_Tcpip_{F447936F-0509-4DC3-89 >4A-B50FE411A02D} > Browsing is active on domain. > Master browser name is: BACK-COMPUTER >Could not connect to registry, error = 53 Unable to determine >build of br >owser master: 53 > \\\\BACK-COMPUTER . Version:05.01 Flags: 51203 NT POTENTIAL >MASTER > 1 backup servers retrieved from master BACK-COMPUTER > \\BACK-COMPUTER > There are 3 servers in domain MSHOME on transport >\Device\NetBT_Tcpip_{F4479 >36F-0509-4DC3-894A-B50FE411A02D} > There are 1 domains in domain MSHOME on transport >\Device\NetBT_Tcpip_{F4479 >36F-0509-4DC3-894A-B50FE411A02D} > > >Client #3 Computer > >Status for domain MSHOME on transport >\Device\NetBT_Tcpip_{DBADB2BF-E63C-47FC-9F >12-0A52AE98FF59} > Browsing is active on domain. > Master browser name is: BACK-COMPUTER >Could not connect to registry, error = 53 Unable to determine >build of br >owser master: 53 > \\\\BACK-COMPUTER . Version:05.01 Flags: 51203 NT POTENTIAL >MASTER > 1 backup servers retrieved from master BACK-COMPUTER > \\BACK-COMPUTER > There are 3 servers in domain MSHOME on transport >\Device\NetBT_Tcpip_{DBADB >2BF-E63C-47FC-9F12-0A52AE98FF59} > There are 1 domains in domain MSHOME on transport >\Device\NetBT_Tcpip_{DBADB >2BF-E63C-47FC-9F12-0A52AE98FF59} The good news is that all 3 computers show the same thing: There are 3 servers in domain MSHOME on transport \Device\NetBT_Tcpip Now BACK-COMPUTER also shows IPX/SPX ("\Device\NwlnkNb"), which is unnecessary. This shouldn't affect the ability to ping Internet servers though. That's going to be a DNS issue, involving the issues that I mentioned in my previous post. See my previous post for discussion about gratuitous protocols too. What is the actual problem - why are you pinging Internet servers? -- Cheers, Chuck, MS-MVP [Windows - Networking] http://nitecruzr.blogspot.com/ Paranoia is not a problem, when it's a normal response from experience. My email is AT DOT actual address pchuck mvps org. Hi Chuck - thanks for coming back.
The reason I was pinging Internet servers is that I was finding that I could neither send nor receive e-mails from either of the client PCs. POP and SMTP settings were all OK (exactly as on the host machine), but I was getting "server name you specified cannot be found" whenever I tried to connect from the clients. Then, as part of my diagnostic procedure, I found I couldn't ping websites by name from the client machines. I solved my "e-mail access from the clients" by pinging the POP and SMTP servers by name from the host, noting down the IP addresses, and substituting these for the normal POP and SMTP server details in my clients' e-mail program. But that still left me wanting to know a) why I couldn't ping by name from the clients, and b) how I could correct the setting. You've made several interesting comments / suggestions, for which I'm grateful. Could I perhaps ask for a little further clarification? Re: 1) BACK-COMPUTER also shows IPX/SPX ("\Device\NwlnkNb"), which is unnecessary 2) Three connections specify 192.168.0.1 as the DNS server (relay). Depending upon how the (router?) is setup, that may or may not work well. For that, we need to know what servers it's relaying the requests to. 3) ...one connection uses two servers directly ("194.168.8.100" / "194.168.4.100"). This discrepancy could cause a variation. 4) FRONT-COMPUTER2 has IPV6 ("Teredo Tunneling"). I've known for that to cause various problems, generally with local connectivity. .... my question would be, how / where do I address these? Other than setting 192.168.0.1 as Preferred DNS Servers on all three machines, I don't think I've had any hand in configuring any of the others. Thanks for your time and trouble. It is much appreciated, but I'm on a rather steep learning curve! All the best - TM On 2 Oct 2006 06:42:29 -0700, trevormidg***@ntlworld.com wrote:
Show quoteHide quote >Hi Chuck - thanks for coming back. Trevor,> >The reason I was pinging Internet servers is that I was finding that I >could neither send nor receive e-mails from either of the client PCs. > >POP and SMTP settings were all OK (exactly as on the host machine), but >I was getting "server name you specified cannot be found" whenever >I tried to connect from the clients. > >Then, as part of my diagnostic procedure, I found I couldn't ping >websites by name from the client machines. > >I solved my "e-mail access from the clients" by pinging the POP and >SMTP servers by name from the host, noting down the IP addresses, and >substituting these for the normal POP and SMTP server details in my >clients' e-mail program. > >But that still left me wanting to know a) why I couldn't ping by name >from the clients, and b) how I could correct the setting. > >You've made several interesting comments / suggestions, for which >I'm grateful. Could I perhaps ask for a little further clarification? > >Re: >1) BACK-COMPUTER also shows IPX/SPX ("\Device\NwlnkNb"), which is >unnecessary > >2) Three connections specify 192.168.0.1 as the DNS server (relay). >Depending upon how the (router?) is setup, that may or may not work >well. For that, we need to know what servers it's relaying the >requests to. > >3) ...one connection uses two servers directly ("194.168.8.100" / >"194.168.4.100"). This discrepancy could cause a variation. > >4) FRONT-COMPUTER2 has IPV6 ("Teredo Tunneling"). I've known for that >to cause various problems, generally with local connectivity. > >... my question would be, how / where do I address these? Other than >setting 192.168.0.1 as Preferred DNS Servers on all three machines, I >don't think I've had any hand in configuring any of the others. > >Thanks for your time and trouble. It is much appreciated, but I'm on >a rather steep learning curve! IPX/SPX (aka NwlnkNb) and IPV6 (aka Teredo Tunneling) are network components that can cause problems with local networking (what you see in My Network Places / Network Neighbourhood). Most small LANs use Server Message Blocks (aka SMBs) for name resolution. If some computers have excessive network components like IPX/SPX or IPV6, and others don't have those components, it's like tourists in a foreign land that don't speak the language. SMBs get lost, and name resolution fails. <http://nitecruzr.blogspot.com/2005/07/windows-networking.html> http://nitecruzr.blogspot.com/2005/07/windows-networking.html From looking at the ipconfig logs, it appears that the NAT router (192.168.0.1) is seen by several computers as the DNS server. The NAT router, though, has to get the DNS information from a dedicated DNS server - it only relays DNS requests. So your router has to have the addresses of the actual DNS servers, probably 194.168.8.100 ("cache2.ntli.net" in Luton, UK) / 194.168.4.100 ("cache1.ntli.net" somewhere in the UK). Even if the router does use the same upstream servers, though, it could introduce variances in the DNS process, so it's best of you setup all computers the same. Pick one - just be consistent. <http://nitecruzr.blogspot.com/2006/03/dns-server-settings-on-your-computer.html> http://nitecruzr.blogspot.com/2006/03/dns-server-settings-on-your-computer.html -- Cheers, Chuck, MS-MVP [Windows - Networking] http://nitecruzr.blogspot.com/ Paranoia is not a problem, when it's a normal response from experience. My email is AT DOT actual address pchuck mvps org. Thanks, Chuck - been away for a couple of days.
Working on it... All the best - TM In news:1159627993.246106.306540@i42g2000cwa.googlegroups.com, trevormidg***@ntlworld.com <trevormidg***@ntlworld.com> typed:> I have a small peer-to-peer network of three computers. All computers Do you have a DHCP server on your network? For example, via a hardware > are XP (SP2). > >> From the two client PCs, I can ping sites by IP number but not by >> name. > > > What settings do I have to adjust (and on which PCs?) so that I can > ping correctly by both IP number and name? > > Thanks in anticitpation. > > TM firewall/gateway/router appliance? If so, make sure it is set up to 'dish out' the appropriate DNS server IPs to your clients - whatever public DNS servers your ISP gave you. If for some reason you are using static IPs configured on each workstation, compare them using ipconfig /all (in a command prompt - start | run | cmd <enter> ) and make sure they're all using the same DNS server IPs.
Beginner!! In my local network all PCs can use the DSL modem but...
No files showing Problem Networking an XP Home with two XP Pro Computers. Mapping Networked Printers Using Command Prompt What DNS addres to use on internal network? Linksys router with Quest DSL? Big problems with LAN connection to router. Firewall blocking some web browser functions Can't access networkdrives when connecting via vpn How can I setup this home network? |
|||||||||||||||||||||||