XP PC lost ability to network

[Wayne McBryde]

Unable to browse network, 2nd time for this problem but
different PC this time. Problem started after a failure
of our battery backup that caused the PC to loose power.
There were no new programs loaded and this PC had been on
the network for 6 months or so. Our network has 3 XP
Pro, 1 Win 98, 1 Win 95, and 2 networked laser
printers. Before this problem started all PC's
could "Talk" to each other. 1 of the XP PC's is acting
at the Gateway (not sure this is the correct term) for
the others for internet access. The PC with the problem
is 1 of the other XP PC's.

The PC with the problem can "See" the group (some times)
but not the other PC's, nor print to the laser printers.
I have deleted the Ethernet adapter and reinstalled it.
I have gone to Windows add/remove components and removed
networking, then reboot and reinstall them. I have gone
through the network setup wizard countless times. I
disabled the Ethernet adapter on the motherboard,
rebooted and reinstalled it. I have also shut down
EVERYTHING dealing with the network and restarted. All
were no help and did not change the symptoms. However I
can ping the other PC's.

I disabled the Ethernet adapter on the mother board and
installed an Intel 10/100 Pro Ethernet card. Used the
network wizard to set it up. At this point it can "See"
the XP PC that is the gateway but not the others. The
Gateway PC can not see it. If it sits for a while, it
will not be able to "See" the gateway PC.

I don't want to format the hard drive in this PC but I
did install another spare hard drive. Installed XP Pro,
went through the network setup wizard and all works. All
PC's can "See and Talk" to each other. So the problem is
Software, but what?

Also, about 3 months ago my "Gateway" PC did the same
thing. I had to reformat the hard drive on it. It did
not have a power failure. It just quit networking.

All help is appreciated.
Wayne

[Robert L [MS-MVP]]

sounds like master browser issue. can you ping each other?

--
For more information, go to http://www25.brinkster.com/ChicagoTech

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Windows & Network Support, Tips and FAQs on
http://www25.brinkster.com/ChicagoTech
This posting is provided "AS IS" with no warranties.

"Wayne McBryde" > wrote in message
...
> Unable to browse network, 2nd time for this problem but
> different PC this time. Problem started after a failure
> of our battery backup that caused the PC to loose power.
> There were no new programs loaded and this PC had been on
> the network for 6 months or so. Our network has 3 XP
> Pro, 1 Win 98, 1 Win 95, and 2 networked laser
> printers. Before this problem started all PC's
> could "Talk" to each other. 1 of the XP PC's is acting
> at the Gateway (not sure this is the correct term) for
> the others for internet access. The PC with the problem
> is 1 of the other XP PC's.
>
> The PC with the problem can "See" the group (some times)
> but not the other PC's, nor print to the laser printers.
> I have deleted the Ethernet adapter and reinstalled it.
> I have gone to Windows add/remove components and removed
> networking, then reboot and reinstall them. I have gone
> through the network setup wizard countless times. I
> disabled the Ethernet adapter on the motherboard,
> rebooted and reinstalled it. I have also shut down
> EVERYTHING dealing with the network and restarted. All
> were no help and did not change the symptoms. However I
> can ping the other PC's.
>
> I disabled the Ethernet adapter on the mother board and
> installed an Intel 10/100 Pro Ethernet card. Used the
> network wizard to set it up. At this point it can "See"
> the XP PC that is the gateway but not the others. The
> Gateway PC can not see it. If it sits for a while, it
> will not be able to "See" the gateway PC.
>
> I don't want to format the hard drive in this PC but I
> did install another spare hard drive. Installed XP Pro,
> went through the network setup wizard and all works. All
> PC's can "See and Talk" to each other. So the problem is
> Software, but what?
>
> Also, about 3 months ago my "Gateway" PC did the same
> thing. I had to reformat the hard drive on it. It did
> not have a power failure. It just quit networking.
>
> All help is appreciated.
> Wayne
>

[Wayne McBryde]

Yes, I just pinged to and from the problem PC.

Wayne
>-----Original Message-----
>sounds like master browser issue. can you ping each
other?
>
>--
>For more information, go to
http://www25.brinkster.com/ChicagoTech
>
>Don't send e-mail or reply to me except you need
consulting services.
>Posting on MS newsgroup will benefit all readers and you
may get more help.
>
>Robert Lin, MS-MVP, MCSE & CNE
>Windows & Network Support, Tips and FAQs on
>http://www25.brinkster.com/ChicagoTech
>This posting is provided "AS IS" with no warranties.
>
>"Wayne McBryde" > wrote in message
...
>> Unable to browse network, 2nd time for this problem but
>> different PC this time. Problem started after a
failure
>> of our battery backup that caused the PC to loose
power.
>> There were no new programs loaded and this PC had been
on
>> the network for 6 months or so. Our network has 3 XP
>> Pro, 1 Win 98, 1 Win 95, and 2 networked laser
>> printers. Before this problem started all PC's
>> could "Talk" to each other. 1 of the XP PC's is acting
>> at the Gateway (not sure this is the correct term) for
>> the others for internet access. The PC with the
problem
>> is 1 of the other XP PC's.
>>
>> The PC with the problem can "See" the group (some
times)
>> but not the other PC's, nor print to the laser
printers.
>> I have deleted the Ethernet adapter and reinstalled it.
>> I have gone to Windows add/remove components and
removed
>> networking, then reboot and reinstall them. I have
gone
>> through the network setup wizard countless times. I
>> disabled the Ethernet adapter on the motherboard,
>> rebooted and reinstalled it. I have also shut down
>> EVERYTHING dealing with the network and restarted. All
>> were no help and did not change the symptoms. However
I
>> can ping the other PC's.
>>
>> I disabled the Ethernet adapter on the mother board and
>> installed an Intel 10/100 Pro Ethernet card. Used the
>> network wizard to set it up. At this point it
can "See"
>> the XP PC that is the gateway but not the others. The
>> Gateway PC can not see it. If it sits for a while, it
>> will not be able to "See" the gateway PC.
>>
>> I don't want to format the hard drive in this PC but I
>> did install another spare hard drive. Installed XP
Pro,
>> went through the network setup wizard and all works.
All
>> PC's can "See and Talk" to each other. So the problem
is
>> Software, but what?
>>
>> Also, about 3 months ago my "Gateway" PC did the same
>> thing. I had to reformat the hard drive on it. It did
>> not have a power failure. It just quit networking.
>>
>> All help is appreciated.
>> Wayne
>>
>
>
>.
>

[Wayne McBryde]

More info:
I can ping to the IP address but not the name.

I went to
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;q299357
and ran this utility, It did not help.

I went to:
http://www.practicallynetworked.com/sharing/troubleshoot/
Unless I missed something it did not fix my problem

I ran System restore on the first PC that had this
problem, it did not fix the problem.

I went through the trouble shooter for network problems
on the PC. It did not fix the problem.

Still looking for a fix.

Wayne

>-----Original Message-----
>Yes, I just pinged to and from the problem PC.
>
>Wayne
>>-----Original Message-----
>>sounds like master browser issue. can you ping each
>other?
>>
>>--
>>For more information, go to
>http://www25.brinkster.com/ChicagoTech
>>
>>Don't send e-mail or reply to me except you need
>consulting services.
>>Posting on MS newsgroup will benefit all readers and
you
>may get more help.
>>
>>Robert Lin, MS-MVP, MCSE & CNE
>>Windows & Network Support, Tips and FAQs on
>>http://www25.brinkster.com/ChicagoTech
>>This posting is provided "AS IS" with no warranties.
>>
>>"Wayne McBryde" > wrote in message
...
>>> Unable to browse network, 2nd time for this problem
but
>>> different PC this time. Problem started after a
>failure
>>> of our battery backup that caused the PC to loose
>power.
>>> There were no new programs loaded and this PC had
been
>on
>>> the network for 6 months or so. Our network has 3 XP
>>> Pro, 1 Win 98, 1 Win 95, and 2 networked laser
>>> printers. Before this problem started all PC's
>>> could "Talk" to each other. 1 of the XP PC's is
acting
>>> at the Gateway (not sure this is the correct term) for
>>> the others for internet access. The PC with the
>problem
>>> is 1 of the other XP PC's.
>>>
>>> The PC with the problem can "See" the group (some
>times)
>>> but not the other PC's, nor print to the laser
>printers.
>>> I have deleted the Ethernet adapter and reinstalled
it.
>>> I have gone to Windows add/remove components and
>removed
>>> networking, then reboot and reinstall them. I have
>gone
>>> through the network setup wizard countless times. I
>>> disabled the Ethernet adapter on the motherboard,
>>> rebooted and reinstalled it. I have also shut down
>>> EVERYTHING dealing with the network and restarted.
All
>>> were no help and did not change the symptoms.
However
>I
>>> can ping the other PC's.
>>>
>>> I disabled the Ethernet adapter on the mother board
and
>>> installed an Intel 10/100 Pro Ethernet card. Used the
>>> network wizard to set it up. At this point it
>can "See"
>>> the XP PC that is the gateway but not the others. The
>>> Gateway PC can not see it. If it sits for a while, it
>>> will not be able to "See" the gateway PC.
>>>
>>> I don't want to format the hard drive in this PC but I
>>> did install another spare hard drive. Installed XP
>Pro,
>>> went through the network setup wizard and all works.
>All
>>> PC's can "See and Talk" to each other. So the
problem
>is
>>> Software, but what?
>>>
>>> Also, about 3 months ago my "Gateway" PC did the same
>>> thing. I had to reformat the hard drive on it. It
did
>>> not have a power failure. It just quit networking.
>>>
>>> All help is appreciated.
>>> Wayne
>>>
>>
>>
>>.
>>
>.
>

[Ron Lowe]

"Wayne McBryde" > wrote in message
...
> More info:
> I can ping to the IP address but not the name.
>
<snipage>

Sounds like NetBIOS name resolution failure.

Just to go over some basics again:

From the broken machine, go to a command prompt and try to ping
another machine by IP address and then by name.
Eg:

ping 192.168.0.10
ping OtherBox

If the first works, but the second fails then this indicates
NetBIOS name resolution failure.

1) Ensure all firewalls are disabled or preferably un-installed
as per the mfr's instructions prior to any fault-finding.

2) Go to TCP/IP properties, advanced button, WINS tab
and ensure NetBIOS-over-TCP/IP is enabled;

3) Go to a command prompt, and issue the command:
IPCONFIG /ALL.
Look at the Node Type.
If it's P-to-P, that's a problem.

In this case, go to Start | Run | regedit.
Go to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Netbt\Parameters

If either of the following values are present, delete them:

NodeType;
DhcpNodeType.

This should cause the node type to default correctly.
( the node type will report as 'Unknown' in the default case. )

For futher details, see this article:
Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177


Post back with what you find...



--
Best Regards,
Ron Lowe
MS-MVP Windows Networking

[Wayne McBryde]

Ron,

From broken machine I can ping other PC by IP or name (it
can also ping itself by name or IP).

From good machine I can ping broken machine by IP but not
Name (gets host not found).

No firewall on broken PC.

TCP/IP Properties was set to Default (like the other
PC's) but I changed it to NetBIOS-over-TCP/IP.

With the command ipconfig /all, node type is "mixed".

Ran regedit, I had the line for DhcpNodeType but not
NodeType. I deleted DhcpNodeType.

I rebooted the PC after each action. The symptoms never
changed.

Wayne


>-----Original Message-----
>"Wayne McBryde" > wrote in message
...
>> More info:
>> I can ping to the IP address but not the name.
>>
><snipage>
>
>Sounds like NetBIOS name resolution failure.
>
>Just to go over some basics again:
>
>From the broken machine, go to a command prompt and try
to ping
>another machine by IP address and then by name.
>Eg:
>
>ping 192.168.0.10
>ping OtherBox
>
>If the first works, but the second fails then this
indicates
>NetBIOS name resolution failure.
>
>1) Ensure all firewalls are disabled or preferably un-
installed
>as per the mfr's instructions prior to any fault-finding.
>
>2) Go to TCP/IP properties, advanced button, WINS tab
> and ensure NetBIOS-over-TCP/IP is enabled;
>
>3) Go to a command prompt, and issue the command:
> IPCONFIG /ALL.
> Look at the Node Type.
> If it's P-to-P, that's a problem.
>
> In this case, go to Start | Run | regedit.
> Go to:
>
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Netbt
\Parameters
>
> If either of the following values are present, delete
them:
>
> NodeType;
> DhcpNodeType.
>
> This should cause the node type to default correctly.
> ( the node type will report as 'Unknown' in the
default case. )
>
> For futher details, see this article:
> Default Node Type for Microsoft Clients
> http://support.microsoft.com/default.aspx?scid=kb;en-
us;160177
>
>
>Post back with what you find...
>
>
>
>--
>Best Regards,
>Ron Lowe
>MS-MVP Windows Networking
>
>
>
>.
>

[Ron Lowe]

"Wayne McBryde" > wrote in message
...
> Sill waiting for help.
>
> Wayne


I'm sorry, Wayne.
I've moving house right now, so I'm a bit off-line.

I'm afraid I don't know the answer.

An inability for a machine to resolve a remote machine's IP address by
issuing NetBIOS broadcasts usually indicates a nodetype error on the local
machine.

An inability of a machine to *respond* to NetBIOS name requests usually
indicates a firewall issue on the non-respoding machine.

I'd double-check there is not a firewall up, and if there ever has been,
that it was un-installed correctly. Badly un-installed f/ws can cause this
type of issue.

--
Best Regards,
Ron Lowe
MS-MVP Windows Networking

[Wayne McBryde]

Ron,

Thanks, This PC has a copy of Etrust EZ Armor. It
includes a firewall. However we were not using the
firewall. After reading your response, I started the
firewall then shut it down (I did not remove it). Now
this PC works on the network like it did before the
problem started.

Thanks for your help.

Wayne McBryde


>-----Original Message-----
>"Wayne McBryde" > wrote in message
...
>> Sill waiting for help.
>>
>> Wayne
>
>
>I'm sorry, Wayne.
>I've moving house right now, so I'm a bit off-line.
>
>I'm afraid I don't know the answer.
>
>An inability for a machine to resolve a remote machine's
IP address by
>issuing NetBIOS broadcasts usually indicates a nodetype
error on the local
>machine.
>
>An inability of a machine to *respond* to NetBIOS name
requests usually
>indicates a firewall issue on the non-respoding machine.
>
>I'd double-check there is not a firewall up, and if
there ever has been,
>that it was un-installed correctly. Badly un-installed
f/ws can cause this
>type of issue.
>
>--
>Best Regards,
>Ron Lowe
>MS-MVP Windows Networking
>
>
>.
>

[Ron Lowe]

"Wayne McBryde" > wrote in message
...
> Sill waiting for help.
>
> Wayne


I'm sorry, Wayne.
I've moving house right now, so I'm a bit off-line.

I'm afraid I don't know the answer.

An inability for a machine to resolve a remote machine's IP address by
issuing NetBIOS broadcasts usually indicates a nodetype error on the local
machine.

An inability of a machine to *respond* to NetBIOS name requests usually
indicates a firewall issue on the non-respoding machine.

I'd double-check there is not a firewall up, and if there ever has been,
that it was un-installed correctly. Badly un-installed f/ws can cause this
type of issue.

--
Best Regards,
Ron Lowe
MS-MVP Windows Networking

[Wayne McBryde]

Ron,

Thanks, This PC has a copy of Etrust EZ Armor. It
includes a firewall. However we were not using the
firewall. After reading your response, I started the
firewall then shut it down (I did not remove it). Now
this PC works on the network like it did before the
problem started.

Thanks for your help.

Wayne McBryde


>-----Original Message-----
>"Wayne McBryde" > wrote in message
...
>> Sill waiting for help.
>>
>> Wayne
>
>
>I'm sorry, Wayne.
>I've moving house right now, so I'm a bit off-line.
>
>I'm afraid I don't know the answer.
>
>An inability for a machine to resolve a remote machine's
IP address by
>issuing NetBIOS broadcasts usually indicates a nodetype
error on the local
>machine.
>
>An inability of a machine to *respond* to NetBIOS name
requests usually
>indicates a firewall issue on the non-respoding machine.
>
>I'd double-check there is not a firewall up, and if
there ever has been,
>that it was un-installed correctly. Badly un-installed
f/ws can cause this
>type of issue.
>
>--
>Best Regards,
>Ron Lowe
>MS-MVP Windows Networking
>
>
>.
>

[Ron Lowe]

"Wayne McBryde" > wrote in message
...
> Sill waiting for help.
>
> Wayne


I'm sorry, Wayne.
I've moving house right now, so I'm a bit off-line.

I'm afraid I don't know the answer.

An inability for a machine to resolve a remote machine's IP address by
issuing NetBIOS broadcasts usually indicates a nodetype error on the local
machine.

An inability of a machine to *respond* to NetBIOS name requests usually
indicates a firewall issue on the non-respoding machine.

I'd double-check there is not a firewall up, and if there ever has been,
that it was un-installed correctly. Badly un-installed f/ws can cause this
type of issue.

--
Best Regards,
Ron Lowe
MS-MVP Windows Networking

[Wayne McBryde]

Ron,

Thanks, This PC has a copy of Etrust EZ Armor. It
includes a firewall. However we were not using the
firewall. After reading your response, I started the
firewall then shut it down (I did not remove it). Now
this PC works on the network like it did before the
problem started.

Thanks for your help.

Wayne McBryde


>-----Original Message-----
>"Wayne McBryde" > wrote in message
...
>> Sill waiting for help.
>>
>> Wayne
>
>
>I'm sorry, Wayne.
>I've moving house right now, so I'm a bit off-line.
>
>I'm afraid I don't know the answer.
>
>An inability for a machine to resolve a remote machine's
IP address by
>issuing NetBIOS broadcasts usually indicates a nodetype
error on the local
>machine.
>
>An inability of a machine to *respond* to NetBIOS name
requests usually
>indicates a firewall issue on the non-respoding machine.
>
>I'd double-check there is not a firewall up, and if
there ever has been,
>that it was un-installed correctly. Badly un-installed
f/ws can cause this
>type of issue.
>
>--
>Best Regards,
>Ron Lowe
>MS-MVP Windows Networking
>
>
>.
>

[Ron Lowe]

"Wayne McBryde" > wrote in message
...
> Sill waiting for help.
>
> Wayne


I'm sorry, Wayne.
I've moving house right now, so I'm a bit off-line.

I'm afraid I don't know the answer.

An inability for a machine to resolve a remote machine's IP address by
issuing NetBIOS broadcasts usually indicates a nodetype error on the local
machine.

An inability of a machine to *respond* to NetBIOS name requests usually
indicates a firewall issue on the non-respoding machine.

I'd double-check there is not a firewall up, and if there ever has been,
that it was un-installed correctly. Badly un-installed f/ws can cause this
type of issue.

--
Best Regards,
Ron Lowe
MS-MVP Windows Networking

[Wayne McBryde]

Ron,

Thanks, This PC has a copy of Etrust EZ Armor. It
includes a firewall. However we were not using the
firewall. After reading your response, I started the
firewall then shut it down (I did not remove it). Now
this PC works on the network like it did before the
problem started.

Thanks for your help.

Wayne McBryde


>-----Original Message-----
>"Wayne McBryde" > wrote in message
...
>> Sill waiting for help.
>>
>> Wayne
>
>
>I'm sorry, Wayne.
>I've moving house right now, so I'm a bit off-line.
>
>I'm afraid I don't know the answer.
>
>An inability for a machine to resolve a remote machine's
IP address by
>issuing NetBIOS broadcasts usually indicates a nodetype
error on the local
>machine.
>
>An inability of a machine to *respond* to NetBIOS name
requests usually
>indicates a firewall issue on the non-respoding machine.
>
>I'd double-check there is not a firewall up, and if
there ever has been,
>that it was un-installed correctly. Badly un-installed
f/ws can cause this
>type of issue.
>
>--
>Best Regards,
>Ron Lowe
>MS-MVP Windows Networking
>
>
>.
>