Intermitant XP Network Problems

[AndyR]

If this isn't posted to the correct group, please let me know...

I have a Win2K domain server that 2 XP Pro PC's log into. Both XP machines log in
fine, and can see each other while brosing the network. I have a test SQL Server
database on one of the XP PC's (#1), which I would like the other XP PC (#2) to see.
The problem is that #2 intermitantly loses it's connection(s) to #1. This isn't a SQL
problem -- because when this happens, #2 also loses its mapped drives to #1. It can
still see the name in Network Places -- but when it double-clicks on the name, it gets
the error "<ServerName> is not accessible. You might not have permission to use this
network resource."

Very rarely, #2 will reconnect to #1 after some delay (minutes or hours). But usually the
only way I have been able to get reconnected again is to reboot. I don't reboot #2 --
just #1. Most of the time, it can connect again -- but sometimes it takes several
reboots. Then, it will lose it's connection again some time in the future (could be 15
minutes, 2 hours, 2 days, etc. -- always variable). I have disabled all firewall and virus
software without any success. But, I don't suspect this to be the problem since #2 can
connect to #1 fine with virus protection/firewall enabled. Once it loses its connection,
only a reboot of #1 will usually fix the problem. Through all of this, both PC's can always
see and access the server resources without any problems. So, I don't suspect that it's
a hardware issue (cables, etc.).

Could this be in relation to XP Pro's "10 concurrent connections" feature (even though
the single XP PC is the only one accessing it)? What else would cause the intermitant
network connectivity issues?

Thanks for any help.
Andy

 

[Robert L [MS-MVP]]

I am thinking it is name resolution issue. Any errors in the event viewer?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<AndyR> wrote in message If this isn't posted to the correct group, please let me know...

I have a Win2K domain server that 2 XP Pro PC's log into. Both XP machines log in
fine, and can see each other while brosing the network. I have a test SQL Server
database on one of the XP PC's (#1), which I would like the other XP PC (#2) to see.
The problem is that #2 intermitantly loses it's connection(s) to #1. This isn't a SQL
problem -- because when this happens, #2 also loses its mapped drives to #1. It can
still see the name in Network Places -- but when it double-clicks on the name, it gets
the error "<ServerName> is not accessible. You might not have permission to use this
network resource."

Very rarely, #2 will reconnect to #1 after some delay (minutes or hours). But usually the
only way I have been able to get reconnected again is to reboot. I don't reboot #2 --
just #1. Most of the time, it can connect again -- but sometimes it takes several
reboots. Then, it will lose it's connection again some time in the future (could be 15
minutes, 2 hours, 2 days, etc. -- always variable). I have disabled all firewall and virus
software without any success. But, I don't suspect this to be the problem since #2 can
connect to #1 fine with virus protection/firewall enabled. Once it loses its connection,
only a reboot of #1 will usually fix the problem. Through all of this, both PC's can always
see and access the server resources without any problems. So, I don't suspect that it's
a hardware issue (cables, etc.).

Could this be in relation to XP Pro's "10 concurrent connections" feature (even though
the single XP PC is the only one accessing it)? What else would cause the intermitant
network connectivity issues?

Thanks for any help.
Andy

 

[AJR]

Probably is a name issue - however I take it that following is a snapshot of the problem : Server with two XPs - when XPs cannot "communicate" with each other both XPs still can access the server.

May be a dumb question - when XPs cannot see each other can the server see each XP?


I am thinking it is name resolution issue. Any errors in the event viewer?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<AndyR> wrote in message If this isn't posted to the correct group, please let me know...

I have a Win2K domain server that 2 XP Pro PC's log into. Both XP machines log in
fine, and can see each other while brosing the network. I have a test SQL Server
database on one of the XP PC's (#1), which I would like the other XP PC (#2) to see.
The problem is that #2 intermitantly loses it's connection(s) to #1. This isn't a SQL
problem -- because when this happens, #2 also loses its mapped drives to #1. It can
still see the name in Network Places -- but when it double-clicks on the name, it gets
the error "<ServerName> is not accessible. You might not have permission to use this
network resource."

Very rarely, #2 will reconnect to #1 after some delay (minutes or hours). But usually the
only way I have been able to get reconnected again is to reboot. I don't reboot #2 --
just #1. Most of the time, it can connect again -- but sometimes it takes several
reboots. Then, it will lose it's connection again some time in the future (could be 15
minutes, 2 hours, 2 days, etc. -- always variable). I have disabled all firewall and virus
software without any success. But, I don't suspect this to be the problem since #2 can
connect to #1 fine with virus protection/firewall enabled. Once it loses its connection,
only a reboot of #1 will usually fix the problem. Through all of this, both PC's can always
see and access the server resources without any problems. So, I don't suspect that it's
a hardware issue (cables, etc.).

Could this be in relation to XP Pro's "10 concurrent connections" feature (even though
the single XP PC is the only one accessing it)? What else would cause the intermitant
network connectivity issues?

Thanks for any help.
Andy

 

[Chuck]

If this isn't posted to the correct group, please let me know...

I have a Win2K domain server that 2 XP Pro PC's log into. Both XP machines log in
fine, and can see each other while brosing the network. I have a test SQL Server
database on one of the XP PC's (#1), which I would like the other XP PC (#2) to see.
The problem is that #2 intermitantly loses it's connection(s) to #1. This isn't a SQL
problem -- because when this happens, #2 also loses its mapped drives to #1. It can
still see the name in Network Places -- but when it double-clicks on the name, it gets
the error "<ServerName> is not accessible. You might not have permission to use this
network resource."

Very rarely, #2 will reconnect to #1 after some delay (minutes or hours). But usually the
only way I have been able to get reconnected again is to reboot. I don't reboot #2 --
just #1. Most of the time, it can connect again -- but sometimes it takes several
reboots. Then, it will lose it's connection again some time in the future (could be 15
minutes, 2 hours, 2 days, etc. -- always variable). I have disabled all firewall and virus
software without any success. But, I don't suspect this to be the problem since #2 can
connect to #1 fine with virus protection/firewall enabled. Once it loses its connection,
only a reboot of #1 will usually fix the problem. Through all of this, both PC's can always
see and access the server resources without any problems. So, I don't suspect that it's
a hardware issue (cables, etc.).

Could this be in relation to XP Pro's "10 concurrent connections" feature (even though
the single XP PC is the only one accessing it)? What else would cause the intermitant
network connectivity issues?

Thanks for any help.
Andy

Andy,

When you mention server access thru Network Places, this sounds like a browser
issue.
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html

Browser issues can be caused by many thing, and the most commonly noted one here
is a firewall or other security setting. Please note that many personal
firewalls are known for not reacting properly when "disabled". Virus programs,
also, may contain an antiworm product that can cause firewall type problems.
The latter may not be disablable at all.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

When you talk about a random connectivity issue, the network card on Computer
#1, and its power setting, is a possibility.
<http://nitecruzr.blogspot.com/2005/06/does-your-computer-lose-network.html>
http://nitecruzr.blogspot.com/2005/06/does-your-computer-lose-network.html

 

[Andy]

Thanks for the responses.

No events at all are created in either of the XP clients or on the server. And yes: when the client XP cannot connect to the host XP, the Win2K server can still see and connect to both XP's fine. However, the client XP can ping the host XP by name, and it returns the proper IP.

Probably is a name issue - however I take it that following is a snapshot of the problem : Server with two XPs - when XPs cannot "communicate" with each other both XPs still can access the server.

May be a dumb question - when XPs cannot see each other can the server see each XP?


I am thinking it is name resolution issue. Any errors in the event viewer?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<AndyR> wrote in message If this isn't posted to the correct group, please let me know...

I have a Win2K domain server that 2 XP Pro PC's log into. Both XP machines log in
fine, and can see each other while brosing the network. I have a test SQL Server
database on one of the XP PC's (#1), which I would like the other XP PC (#2) to see.
The problem is that #2 intermitantly loses it's connection(s) to #1. This isn't a SQL
problem -- because when this happens, #2 also loses its mapped drives to #1. It can
still see the name in Network Places -- but when it double-clicks on the name, it gets
the error "<ServerName> is not accessible. You might not have permission to use this
network resource."

Very rarely, #2 will reconnect to #1 after some delay (minutes or hours). But usually the
only way I have been able to get reconnected again is to reboot. I don't reboot #2 --
just #1. Most of the time, it can connect again -- but sometimes it takes several
reboots. Then, it will lose it's connection again some time in the future (could be 15
minutes, 2 hours, 2 days, etc. -- always variable). I have disabled all firewall and virus
software without any success. But, I don't suspect this to be the problem since #2 can
connect to #1 fine with virus protection/firewall enabled. Once it loses its connection,
only a reboot of #1 will usually fix the problem. Through all of this, both PC's can always
see and access the server resources without any problems. So, I don't suspect that it's
a hardware issue (cables, etc.).

Could this be in relation to XP Pro's "10 concurrent connections" feature (even though
the single XP PC is the only one accessing it)? What else would cause the intermitant
network connectivity issues?

Thanks for any help.
Andy

 

[Andy]

Thanks for your response.

I don't think that it's a browser issue -- because both XP's can always see
each other, they just can't connect resources to each other. I can refresh
the list of network PC's, and both PC's are always visible.

If the virus/firewall software was a problem -- wouldn't it *always* be a
problem? Because I can connect between the 2 XP PC's fine, but that
connection is lost after a variable amount of time.

I turned off the power features on the network card -- hopefully it makes a
difference. But the host PC (#1) never loses network connectivity (Internet,
server access, etc.) -- #2 just can't connect to #1's resources.

Thanks,
Andy

 

[Chuck]

Thanks for your response.

I don't think that it's a browser issue -- because both XP's can always see
each other, they just can't connect resources to each other. I can refresh
the list of network PC's, and both PC's are always visible.

If the virus/firewall software was a problem -- wouldn't it *always* be a
problem? Because I can connect between the 2 XP PC's fine, but that
connection is lost after a variable amount of time.

I turned off the power features on the network card -- hopefully it makes a
difference. But the host PC (#1) never loses network connectivity (Internet,
server access, etc.) -- #2 just can't connect to #1's resources.

Thanks,
Andy

Hi Andy,

A browser conflict is amorphous. If you read my article, and the Microsoft
white paper linked from it, you'll see that asymmetrical access / visibility
problems, where a target might be visible but not accessible, are part of a
browser conflict. And a browser conflict is the only networking glitch that I
know of, short of the power management disconnection, or maybe a physical
equipment issue, that can come and go seemingly randomly.

The browser works well in a client-server domain environment, but not so well in
a peer-peer workgroup. A segmented workgroup, with cached browse entries, can
happen if your workgroup ever undergoes a master browser election with the
master browser separated, for any reason, from any other browser.
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html

What type of networking hardware is involved here? Have you done any graphical
analysis, maybe PingPlotter or equivalent, supporting your observations?
<http://nitecruzr.blogspot.com/2006/02/diagnosing-network-problems-using_11.html>
http://nitecruzr.blogspot.com/2006/02/diagnosing-network-problems-using_11.html

 

[Andy]

Hi Chuck,

Thanks for the additional information. After reading your article, I have
disabled the Browser service on my 2 client PC's. However, both of these do
log into a domain (the Win2K server that both can always access -- and which
always can access them). Your article stated that domains don't have so much
of a browser problem as peer-to-peer networks, so I'm not too sure how much
improvement there will be -- but I will let you know.

Some of the other suggestions pointed at a possible name resolution issue --
how would I check/fix this?

I have downloaded PingPlotter and will let you know the results.

Thanks,
Andy

 

[Chuck]

Hi Chuck,

Thanks for the additional information. After reading your article, I have
disabled the Browser service on my 2 client PC's. However, both of these do
log into a domain (the Win2K server that both can always access -- and which
always can access them). Your article stated that domains don't have so much
of a browser problem as peer-to-peer networks, so I'm not too sure how much
improvement there will be -- but I will let you know.

Some of the other suggestions pointed at a possible name resolution issue --
how would I check/fix this?

I have downloaded PingPlotter and will let you know the results.

Thanks,
Andy

Andy,

In a domain, you generally have servers (computers dedicated as servers), and
generally there will be 1 server for every 32 client computers. Servers
typically stay online constantly, so you have no browser problems.

You get browser problems when you have client computers running as a browser,
which is normal in a home or workgroup environment. Client computers are turned
off / disconnected / carried out of range of the network, etc. When a client
computer goes offline, the computers depending upon it have to get a new browser
relationship. That's where the problems start.

If your two computers only login to the domain when accessing other computers,
the domain browser infrastructure will take care of them. If your clients have
to function when away from the domain, too, we will have to deal with that.

Microsoft Windows computers have to function in so many different ways, and in
so many different configurations. It's no wonder that there are problems.

If you want to consider name resolution issues, start from my "Error = 53"
article.
<http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html

You never realise how complicated Windows Networking is, until you look at
browser, name resolution, and authentication issues, and see how easily each
type of problem can cause symptoms that appear as other problems.
<http://nitecruzr.blogspot.com/2005/07/windows-networking.html>
http://nitecruzr.blogspot.com/2005/07/windows-networking.html