XP Client can't connect (or ping) Host XP machine over wired LAN

[Fastener Ron]

Hello, I am new to the Forum but am somewhat capable with PCs. I am the home
IT guy and daughter's XP Client machine, previously coneccted (pre summer
vacation) to our working XP home network, will now NOT print to host XP
machine over wired LAN (same workgroup). I deleted the printer on the client
then tried to add it again using the wizard but could not find the LAN
workgroup. There are other wired & wireless machines still connected &
communicating over the LAN. All are XP machines, fully updated with Windows
Update (no Vista machines attached).

I tried the obvious things including running the network setup wizard to try
& add the workgroup to the stubborn Client. The wizard runs but still can't
seem to add the workgroup (named: BPC on all the other machines, including
the Host). The XP client has file & print sharing enabled AND the windows
firewall has the box checked for file & print sharing exception.

McAfee is running on all the XP machines so I disabled the firewalls on it.
Also, I was able to use McAfee Network settings to connect to the XP host and
the stubborn XP Client. According to McAfee, the XP Client & Host are
connected. Still, I can't seem to get this XP client to locate the workgroup
or the XP Host machine and it's USB attacthed printer.

Any help with this would be appreciated. Thanks!

 

[Jack [MVP-Networking]]

Hi
Do not keep running the wizards.
If it does not work at the first run or two, it just adds unneeded entries
to the system.
Configure the Network Manually from scratch.
Maybe this can Help, http://www.ezlan.net/debug.html
Windows XP File Sharing -
http://support.microsoft.com/default.aspx?scid=kb;en-us;304040
http://support.microsoft.com/default.aspx?scid=kb;en-us;304040
Printer Sharing XP -
http://www.microsoft.com/windowsxp/using/networking/expert/honeycutt_july2.mspx
Windows Native Firewall setting for Sharing XP -
http://support.microsoft.com/kb/875357
Jack (MS, MVP-Networking).

 

[Fastener Ron]

Jack,

Thanks for your reply. Some more notes:

* Internet is working fine from the stubborn XP client.
* I believe all machines (Host & Client) have sp3 installed but am unsure.
* I believe all machines (Host & Client) have XP pro installed but am unsure.

Here is what I found after checking my system:

(1) No ghost devices appear in the device manager.

(2) There are 3 Network Connection devices shown under "Network Connection":

(a) 1394 Connection (shows "connected" but no data is flowing).
(b) Ralink Turbo Wireless LAN Card (I disabled since we are hard-wired).
(c) Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC (connected &
actively moving data).

(3) Properties of (a) & (c) are set per ezlan except that (c) had the box
checked beside "QoS Packet Scheduler which I then Unchecked and also (c) had
"AEGIS Protocol (IEEE 802. 1x) v3.5.3.0" box checked which I left checked.

(4) The TCP/IP properties for (a) & (b) both were set to "Obtain an IP
address automatically" and "Obtain DNS server automatically".

(5) I did Not try the next 2 ezlan steps (Check & Repair the Socket Layers,
winsock and or refresh the TCP/IP stack -and- Optimize the TCP/IP stack)
since it appeared they were directed to restoring an internet connection
(which we already have working OKAY on the stubborn XP client machine).

(6) I did Not try the KB article 304040
(http://support.microsoft.com/default.aspx?scid=kb;en-us;304040) yet since
the stubborn XP client machine was originally connected to the LAN workgroup
when I set it up so I am not sure (yet) I need to turn on Simple File sharing
on this sp3 XP machine. Correct me if you think this ought to be explored.

(7) The article you sent me about Print Sharing
(http://www.microsoft.com/windowsxp/using/networking/expert/honeycutt_july2.mspx)
was one I looked over already, after failing to get the wizard to locate the
workgroup or find the printer attached to the XP Host on the LAN workgroup.
Nothing seems to be helpful here.

(8) The article you sent about Windows Firewall
(http://support.microsoft.com/kb/875357) is new to me. However, I had already
checked that the firewall permitted "file sharing" as an exception. The
advanced information may be helpful but I am not sure what program is
blocking the stubborn XP client from connecting to the LAN workgroup.

At this point I will re-boot the stubborn XP client & try to connect to the
LAN workgroup (to find the LAN printer) again. I will report back in another
post.

Jack, thanks for your suggestions.

Ron B.

 

[Fastener Ron]

Jack,

I am still NOT able find the LAN Host printer on the BPC workgroup from the
stubborn XP Client.

Running the wizard to "connect" to the workgroup from the stubborn XP Client
seems to go without any errors but when I go to "My Network Places" and click
on "View Workgroup computers", the BPC workgroup is in the address bar but no
workgroup computers are shown.

Trying to add the printer fails when the wizard can't locate the printer (or
the workgroup). It only shows "Microsoft Windows Network" when I attempt to
browse for a printer (i.e. does not show the workgroup or it's attached
printer).

Also, I obtained the IP address for the XP Host and was able to successfully
PING it from the stubborn XP client.

Any further suggestions to try?

Thanks,
Ron B.

 

[John Wunderlich]

=?Utf-8?B?RmFzdGVuZXIgUm9u?= <Fastener
(e-mail address removed)> wrote in

[...]
daughter's XP Client machine, previously coneccted (pre summer
vacation) to our working XP home network, will now NOT print to
host XP machine over wired LAN (same workgroup). I deleted the
printer on the client then tried to add it again using the wizard
but could not find the LAN workgroup. There are other wired &
wireless machines still connected & communicating over the LAN.
[...]

From a command prompt, issue the command:
ipconfig /all
Examine the "Node Type" and make sure that it is not a "P-Type" or
"Peer to Peer" type. If it is, the following Microsoft article might
be of help:

"You cannot view other workgroup computers on the network on a
Windows XP-based computer"
<http://support.microsoft.com/kb/903267>

HTH,
John

 

[Fastener Ron]

Hi John,

Thanks for trying to help.

From the stubborn client machine I used the cmd prompt & entered "ipconfig
/all" and received the following reply:

C:\Documents and Settings\Ron>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Ally
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.pa.comcast.net.

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : hsd1.pa.comcast.net.
Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P)
PCI-E G
igabit Ethernet NIC
Physical Address. . . . . . . . . : 00-1F-D0-5E-99-1D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.119
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 68.87.75.198
68.87.64.150
NetBIOS over Tcpip. . . . . . . . : Disabled
Lease Obtained. . . . . . . . . . : Wednesday, September 09, 2009
7:23:2
4 PM
Lease Expires . . . . . . . . . . : Thursday, September 10, 2009
7:23:24
PM

Going further, after first setting a restore point, I tried the KB903267
registry edit anyway. Looking at the Registry Subkey
"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NetBt\Parameters", I
found the following values:

* Node Type (<- this value was not present)

* DHCP Node Type REG_DWORD 0X00000001 (1)

Then I deleted the "DHCP Node Type REG_DWORD 0X00000001 (1)" entry,
Rebooted, and then tried to add the printer. No Luck.

Further tried adding the workgroup then adding the printer. Also No Luck.

Any other suggestions?

Thanks,
Ron B.

=?Utf-8?B?RmFzdGVuZXIgUm9u?= <Fastener
(e-mail address removed)> wrote in

[...]
daughter's XP Client machine, previously coneccted (pre summer
vacation) to our working XP home network, will now NOT print to
host XP machine over wired LAN (same workgroup). I deleted the
printer on the client then tried to add it again using the wizard
but could not find the LAN workgroup. There are other wired &
wireless machines still connected & communicating over the LAN.
[...]

From a command prompt, issue the command:
ipconfig /all
Examine the "Node Type" and make sure that it is not a "P-Type" or
"Peer to Peer" type. If it is, the following Microsoft article might
be of help:

"You cannot view other workgroup computers on the network on a
Windows XP-based computer"
<http://support.microsoft.com/kb/903267>

HTH,
John

 

[John Wunderlich]

From the stubborn client machine I used the cmd prompt & entered
"ipconfig /all" and received the following reply:

C:\Documents and Settings\Ron>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Ally
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.pa.comcast.net. [...]
NetBIOS over Tcpip. . . . . . . . : Disabled

[...]

What stands out to me here is that "NetBIOS over TCPIP" (NetBT) is
disabled. Try enabling it in the Network Connections Control Panel.
Procedure is described in the following Microsoft article:

"You cannot access shared files and folders or browse computers in
the workgroup with Windows XP"
<http://support.microsoft.com/kb/318030>

In addition your Node Type is labeled "Unknown". Although it
shouldn't affect the problem you're having, you might want to read
the following article as well:

""Ipconfig /All" Command Shows the Node Type as Unknown"
<http://support.microsoft.com/kb/310570>

HTH,
John

 

[Fastener Ron]

Hi John,

Thanks for your latest suggestions. Here is what I tried:

(1) Using KB 318030:

(a) I enabled NetBIOS over TCPIP" (NetBT) in Network Connections.
(b) I checked the Computer Browser Service but it said it was "started"
(i.e. the "Start" button was shaded).
(c) I verifed that "File & Print Sharing" was enabled through Windows
Firewall.

(2) Using KB 310570:

(a) I attempted to use Registry Editor (Regedit.exe) to locate the following
key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Parameters\
and Change the value of the EnableProxy value in the preceding registry key
to 0 or 1.

However, there was no "EnableProxy" key shown. I then added it & set the
value to "1".

(b) After rebooting the computer & running ipconfig /all, here are the
settings:

C:\Documents and Settings\Ron>ipconfig /all


C:\Documents and Settings\Ron>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Ally
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : hsd1.pa.comcast.net.

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : hsd1.pa.comcast.net.
Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P)
PCI-E G
igabit Ethernet NIC
Physical Address. . . . . . . . . : 00-1F-D0-5E-99-1D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.119
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 68.87.75.198
68.87.64.150
NetBIOS over Tcpip. . . . . . . . : Disabled
Lease Obtained. . . . . . . . . . : Saturday, September 12, 2009
10:19:4
3 AM
Lease Expires . . . . . . . . . . : Sunday, September 13, 2009
10:19:43
AM

C:\Documents and Settings\Ron>

Needless to say, I still can't see other PC's in the BPC workgroup nor can I
add the network printer.

Any other suggestions?

Thanks,
Ron Bartlett

From the stubborn client machine I used the cmd prompt & entered
"ipconfig /all" and received the following reply:

C:\Documents and Settings\Ron>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Ally
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.pa.comcast.net. [...]
NetBIOS over Tcpip. . . . . . . . : Disabled

[...]

What stands out to me here is that "NetBIOS over TCPIP" (NetBT) is
disabled. Try enabling it in the Network Connections Control Panel.
Procedure is described in the following Microsoft article:

"You cannot access shared files and folders or browse computers in
the workgroup with Windows XP"
<http://support.microsoft.com/kb/318030>

In addition your Node Type is labeled "Unknown". Although it
shouldn't affect the problem you're having, you might want to read
the following article as well:

""Ipconfig /All" Command Shows the Node Type as Unknown"
<http://support.microsoft.com/kb/310570>

HTH,
John

 

[John Wunderlich]

Hi John,

Thanks for your latest suggestions. Here is what I tried:

(1) Using KB 318030:

(a) I enabled NetBIOS over TCPIP" (NetBT) in Network Connections.
(b) I checked the Computer Browser Service but it said it was
"started" (i.e. the "Start" button was shaded).
(c) I verifed that "File & Print Sharing" was enabled through
Windows Firewall.

(2) Using KB 310570:

(a) I attempted to use Registry Editor (Regedit.exe) to locate the
following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Paramete
rs\ and Change the value of the EnableProxy value in the preceding
registry key to 0 or 1.

However, there was no "EnableProxy" key shown. I then added it &
set the value to "1".

(b) After rebooting the computer & running ipconfig /all, here are
the settings:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Ally
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : hsd1.pa.comcast.net.

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : hsd1.pa.comcast.net.
Description . . . . . . . . . . . : Realtek RTL8168C P)/8111C(P) PCI-E Gigabit Ethernet NIC
Physical Address. . . . . . . . . : 00-1F-D0-5E-99-1D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.119
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 68.87.75.198
68.87.64.150
NetBIOS over Tcpip. . . . . . . . : Disabled
Lease Obtained. . . . . . . . . . : Saturday, September 12, 2009 10:19:43 AM
Lease Expires . . . . . . . . . . : Sunday, September 13, 2009 10:19:43 AM

Needless to say, I still can't see other PC's in the BPC workgroup
nor can I add the network printer.

Any other suggestions?

This is strange. You say you enabled "NetBIOS over Tcpip" in the
control panel although the ipconfig /all command still says that it
is disabled. I found a couple more KB articles that may help but
I'm about out of ideas. See if any of these do anything for you:

""Network Location Cannot be Reached" when accessing shares"
<http://support.microsoft.com/kb/946937>

"Event ID 7001 Is Logged in the System Event Log"
<http://support.microsoft.com/kb/278658>
(Apparently there is a hidden entry in the device manager that
can disable NetBIOS over TCP/IP.)

I wouldn't worry too much about Node Type Unknown.

I assume that in the Network control panel for the Local area
connection that "Client for Microsoft Networks" and "File and
Printer Sharing for Microsoft Networks" is present and checked.

HTH,
John

 

[Fastener Ron]

Hi John,

Thanks for your suggestions. I had already tried some of the KB 946937
ideas without any luck. The KB 278658 ideas were also examined but the
stubborn client did not have any problems with Netbios over TCPIP being
disabled.

The latest thing I tried was to uninstall McAfee on the client (everything,
especially the McAfee firewall) then reinstall ONLY the virsus scan module.
Still no dice.

I've tried googling "problems enabling NetBIOS over Tcpip" and found a
number of different threads on different forums, one of which seemed to be
similar to my problem:

http://forums.whirlpool.net.au/forum-replies-archive.cfm/579159.html

Still, there didn't seem to be anything there I haven't already tried.

Something else which may be a clue (?) to my problem: when I double click
on the Local Area Network icon (in the tray) and try to "repair" the
connection on the Support Tab (even though it says, Windows did not detect
any problems with this connection), I get the following "error":

WINDOWS COULD NOT FINISH REPAIRING THE PROBLEM BECAUSE THE FOLLOWING ACTION
COULD NOT BE COMPLETED: Clearing NetBT

Chasing down this (googling) led to a forum where a person was having
problems connecting to the internet and he practically had to remove &
reinstall his NIC then use a utility to repair his TCPIP and Winsock:

http://forums.speedguide.net/showthread.php?t=192288

Since I am unable to post them on this forum, here is a link to a screen
shot of the current Registry settings for this stubborn client:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters

http://i51.photobucket.com/albums/f366/Cheshie/NetBT_Parameters.jpg

The only alternatives I see now are to:

(1) Use System Restore to attempt to go back in time & reset parameters to a
time when the client DID connect to the network (if that is still possible).

(2) Try posting on some other forums such as:

http://networking.nitecruzr.net/search?q=NetBIOS+over+Tcpip

(3) Call the Geek Squad & try to stump THEM.

(4) Give up.

What frustrates me is that this is a virtually brand new, custom built PC
with lots of horsepower & memory & should not be having these kinds of
problems.

You have been most generous with your time and I thank you very much for
sharing it with me. If you have any other suggestions or ideas as to forums
which may be helpful (or to cross-post this thread elsewhere on the MSFT
forum) it would be greatly appreciated.

Thanks again,
Ron Bartlett

 

[John Wunderlich]

=?Utf-8?B?RmFzdGVuZXIgUm9u?= <[email protected]>
wrote in
[..]

Since I am unable to post them on this forum, here is a link to a
screen shot of the current Registry settings for this stubborn
client:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Paramete
rs

http://i51.photobucket.com/albums/f366/Cheshie/NetBT_Parameters.jpg

The only alternatives I see now are to:

(1) Use System Restore to attempt to go back in time & reset
parameters to a time when the client DID connect to the network
(if that is still possible).

(2) Try posting on some other forums such as:

http://networking.nitecruzr.net/search?q=NetBIOS+over+Tcpip

(3) Call the Geek Squad & try to stump THEM.

(4) Give up.

What frustrates me is that this is a virtually brand new, custom
built PC with lots of horsepower & memory & should not be having
these kinds of problems.

You have been most generous with your time and I thank you very
much for sharing it with me. If you have any other suggestions or
ideas as to forums which may be helpful (or to cross-post this
thread elsewhere on the MSFT forum) it would be greatly
appreciated.

Thanks again,
Ron Bartlett

At the despiration level, sometimes one of these programs will help.
If not and it were me, I'd probably totally uninstall everything
network and try reinstalling again. Maybe another set of eyes in
another forum might help as well. Often, completely reinstalling
Windows is faster than nailing the source of a problem.

LSPFix
<http://www.cexx.org/lspfix.htm>

WinsockXPFix:
<http://www.snapfiles.com/get/winsockxpfix.html>

Good Luck,
John

 

[Fastener Ron]

The PC was finally fixed using WinSock XP Fix:

http://www.snapfiles.com/get/winsockxpfix.html

 

[John Wunderlich]

The PC was finally fixed using WinSock XP Fix:

http://www.snapfiles.com/get/winsockxpfix.html

Thanks for the feedback.
Chalk one up to winsockXPfix!

-- John