A Windows XP help forum. PCbanter

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.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Networking and the Internet with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

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



 
 
Thread Tools Display Modes
  #16  
Old September 12th 09, 11:49 PM posted to microsoft.public.windowsxp.network_web
John Wunderlich
external usenet poster
 
Posts: 1,466
Default XP Client can't connect (or ping) Host XP machine over wired L

=?Utf-8?B?RmFzdGVuZXIgUm9u?=
wrote in :

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\Servic es\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

Ads
  #17  
Old September 12th 09, 11:49 PM posted to microsoft.public.windowsxp.network_web
John Wunderlich
external usenet poster
 
Posts: 1,466
Default XP Client can't connect (or ping) Host XP machine over wired L

=?Utf-8?B?RmFzdGVuZXIgUm9u?=
wrote in :

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\Servic es\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

  #18  
Old September 14th 09, 12:05 AM posted to microsoft.public.windowsxp.network_web
Fastener Ron[_2_]
external usenet poster
 
Posts: 12
Default XP Client can't connect (or ping) Host XP machine over wired L

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...fm/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\Servic es\NetBT\Parameters

http://i51.photobucket.com/albums/f3...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/sear...IOS+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" wrote:

=?Utf-8?B?RmFzdGVuZXIgUm9u?=
wrote in :

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\Servic es\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


  #19  
Old September 14th 09, 12:05 AM posted to microsoft.public.windowsxp.network_web
Fastener Ron[_2_]
external usenet poster
 
Posts: 12
Default XP Client can't connect (or ping) Host XP machine over wired L

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...fm/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\Servic es\NetBT\Parameters

http://i51.photobucket.com/albums/f3...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/sear...IOS+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" wrote:

=?Utf-8?B?RmFzdGVuZXIgUm9u?=
wrote in :

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\Servic es\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


  #20  
Old September 14th 09, 08:26 PM posted to microsoft.public.windowsxp.network_web
John Wunderlich
external usenet poster
 
Posts: 1,466
Default XP Client can't connect (or ping) Host XP machine over wired L

=?Utf-8?B?RmFzdGVuZXIgUm9u?=
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\Servic es\NetBT\Paramete
rs

http://i51.photobucket.com/albums/f3...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/sear...IOS+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

  #21  
Old September 14th 09, 08:26 PM posted to microsoft.public.windowsxp.network_web
John Wunderlich
external usenet poster
 
Posts: 1,466
Default XP Client can't connect (or ping) Host XP machine over wired L

=?Utf-8?B?RmFzdGVuZXIgUm9u?=
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\Servic es\NetBT\Paramete
rs

http://i51.photobucket.com/albums/f3...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/sear...IOS+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

  #22  
Old September 26th 09, 06:19 PM posted to microsoft.public.windowsxp.network_web
Fastener Ron[_2_]
external usenet poster
 
Posts: 12
Default XP Client can't connect (or ping) Host XP machine over wired L

The PC was finally fixed using WinSock XP Fix:

http://www.snapfiles.com/get/winsockxpfix.html
  #23  
Old September 26th 09, 06:19 PM posted to microsoft.public.windowsxp.network_web
Fastener Ron[_2_]
external usenet poster
 
Posts: 12
Default XP Client can't connect (or ping) Host XP machine over wired L

The PC was finally fixed using WinSock XP Fix:

http://www.snapfiles.com/get/winsockxpfix.html
  #24  
Old September 27th 09, 06:54 AM posted to microsoft.public.windowsxp.network_web
John Wunderlich
external usenet poster
 
Posts: 1,466
Default XP Client can't connect (or ping) Host XP machine over wired L

=?Utf-8?B?RmFzdGVuZXIgUm9u?=
wrote in :

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
  #25  
Old September 27th 09, 06:54 AM posted to microsoft.public.windowsxp.network_web
John Wunderlich
external usenet poster
 
Posts: 1,466
Default XP Client can't connect (or ping) Host XP machine over wired L

=?Utf-8?B?RmFzdGVuZXIgUm9u?=
wrote in :

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
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 03:10 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.