If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Can't access PC's by name - only IP
When using an HP 8730w notebook I try to access a resource (server, PC, etc)
on another node of our WAN, I get the following error message: "Windows cannot find '\\servername'. Check the spelling and try again, or try searching for the item by clicking the Start button and then clicking Search." This does not happen with any PC/laptop except this one. The error doesn't occur for LAN destinations - only WAN. The error only occurs when the nmae is used - not the IP address. I have matched the network configuration to a working unit. It occurs on either the wired or wireless connection. |
Ads |
#2
|
|||
|
|||
Can't access PC's by name - only IP
=?Utf-8?B?RGFuaWVs?= wrote in
: When using an HP 8730w notebook I try to access a resource (server, PC, etc) on another node of our WAN, I get the following error message: "Windows cannot find '\\servername'. Check the spelling and try again, or try searching for the item by clicking the Start button and then clicking Search." This does not happen with any PC/laptop except this one. The error doesn't occur for LAN destinations - only WAN. The error only occurs when the nmae is used - not the IP address. I have matched the network configuration to a working unit. It occurs on either the wired or wireless connection. Your computer is failing to resolve NetBT names that aren't on the local subnet. This function is performed by the WINS server. Bring up a command window (Start-Run-"Cmd") and enter the command: ipconfig /all First, make sure the correct "Primary/Secondary WINS server" IP addresses appear in the display and match your other computers. Then verify that the "Node Type" entry is _not_ "Broadcast" (if it is, then the WINS server is ignored). It should be either "Hybrid" or "Mixed". If it does show up as "Broadcast" then the following article might fix it: "You cannot view other workgroup computers on the network on a Windows XP-based computer" http://support.microsoft.com/kb/903267 HTH, John |
#3
|
|||
|
|||
Can't access PC's by name - only IP
We are running AD via Windows 2003 servers - native mode - We're not using
WINS. The settings between a working/non-working unit are identical except for the IP address and machine name. I've already changed the node type from Broadcast to Hybrid. I've run SFC - no difference. I've removed and reinstalled the Microsoft Networking component - no difference. What next? "John Wunderlich" wrote: =?Utf-8?B?RGFuaWVs?= wrote in : When using an HP 8730w notebook I try to access a resource (server, PC, etc) on another node of our WAN, I get the following error message: "Windows cannot find '\\servername'. Check the spelling and try again, or try searching for the item by clicking the Start button and then clicking Search." This does not happen with any PC/laptop except this one. The error doesn't occur for LAN destinations - only WAN. The error only occurs when the nmae is used - not the IP address. I have matched the network configuration to a working unit. It occurs on either the wired or wireless connection. Your computer is failing to resolve NetBT names that aren't on the local subnet. This function is performed by the WINS server. Bring up a command window (Start-Run-"Cmd") and enter the command: ipconfig /all First, make sure the correct "Primary/Secondary WINS server" IP addresses appear in the display and match your other computers. Then verify that the "Node Type" entry is _not_ "Broadcast" (if it is, then the WINS server is ignored). It should be either "Hybrid" or "Mixed". If it does show up as "Broadcast" then the following article might fix it: "You cannot view other workgroup computers on the network on a Windows XP-based computer" http://support.microsoft.com/kb/903267 HTH, John |
#4
|
|||
|
|||
Can't access PC's by name - only IP
=?Utf-8?B?RGFuaWVs?= wrote in
: We are running AD via Windows 2003 servers - native mode - We're not using WINS. The settings between a working/non-working unit are identical except for the IP address and machine name. I've already changed the node type from Broadcast to Hybrid. I've run SFC - no difference. I've removed and reinstalled the Microsoft Networking component - no difference. What next? Check to see that the "lmhosts" and "hosts" files are the same as on other machines. These files are by default in the directory: C:\Windows\System32\drivers\etc If that checks out, then there might be a problem with the DNS or the DNS Search order. The following Microsoft article might be of help: "Configuring IP Addressing and Name Resolution " http://technet.microsoft.com/en-us/library/bb457118.aspx Start about 1/3 the way down the page. Look for "Configuring DNS to Resolve Host Names and Domain Names" located right above Table 24-2. It's a bit detailed, but maybe it will give you a hint. HTH, John |
#5
|
|||
|
|||
Can't access PC's by name - only IP
On Sep 10, 5:38*pm, John Wunderlich wrote:
=?Utf-8?B?RGFuaWVs?= wrote : We are running AD via Windows 2003 servers - native mode - We're not using WINS. The settings between a working/non-working unit are identical except for the IP address and machine name. I've already changed the node type from Broadcast to Hybrid. I've run SFC - no difference. I've removed and reinstalled the Microsoft Networking component - no difference. What next? Check to see that the "lmhosts" and "hosts" files are the same as on other machines. *These files are by default in the directory: C:\Windows\System32\drivers\etc If that checks out, then there might be a problem with the DNS or the DNS Search order. *The following Microsoft article might be of help: "Configuring IP Addressing and Name Resolution " http://technet.microsoft.com/en-us/library/bb457118.aspx Start about 1/3 the way down the page. *Look for "Configuring DNS to Resolve Host Names and Domain Names" located right above Table 24-2. It's a bit detailed, but maybe it will give you a hint. HTH, * John It's possible that your wireless AP is putting the laptop on a separate VLAN. Also, WAN is used for Wide Area Network meaning your internet connection, you should abbreviate wireless LAN as WLAN. |
#6
|
|||
|
|||
Can't access PC's by name - only IP
Sorry, but I meant WAN in the context of a company Wide Area Network that is
comprised of multiple subnets - not Internet access as you inferred. I am not referring to a WLAN. I am not on a VLAN. My network configuration matches another laptop which works. It's not the physical connection either. I can take the working laptop and plug it in to the same cable from my problem laptop and the test laptop works fine. "Hodges" wrote: On Sep 10, 5:38 pm, John Wunderlich wrote: =?Utf-8?B?RGFuaWVs?= wrote : We are running AD via Windows 2003 servers - native mode - We're not using WINS. The settings between a working/non-working unit are identical except for the IP address and machine name. I've already changed the node type from Broadcast to Hybrid. I've run SFC - no difference. I've removed and reinstalled the Microsoft Networking component - no difference. What next? Check to see that the "lmhosts" and "hosts" files are the same as on other machines. These files are by default in the directory: C:\Windows\System32\drivers\etc If that checks out, then there might be a problem with the DNS or the DNS Search order. The following Microsoft article might be of help: "Configuring IP Addressing and Name Resolution " http://technet.microsoft.com/en-us/library/bb457118.aspx Start about 1/3 the way down the page. Look for "Configuring DNS to Resolve Host Names and Domain Names" located right above Table 24-2. It's a bit detailed, but maybe it will give you a hint. HTH, John It's possible that your wireless AP is putting the laptop on a separate VLAN. Also, WAN is used for Wide Area Network meaning your internet connection, you should abbreviate wireless LAN as WLAN. |
Thread Tools | |
Display Modes | |
|
|