slow access to networked computer

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have three computers on home network via router. One is Windows 2000, one
-Windows XP home and third on - Windows XP pro. When I acces other computers
from 2000 machin everything is fine. But when I access other computers from
both XP machines it is a notyiceable (up to 10 sec) delay in openning
networked computers and shared folders. What can be done?
 
I have three computers on home network via router. One is Windows 2000, one
-Windows XP home and third on - Windows XP pro. When I acces other computers
from 2000 machin everything is fine. But when I access other computers from
both XP machines it is a notyiceable (up to 10 sec) delay in openning
networked computers and shared folders. What can be done?
Click to expand...

I'd bet one of two possibilities - gratuitous protocols, or name resolution
problems.
Gratuitous Protocols:
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html
Name Resolution Problems:
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

Possible third thing to check - LSP / Winsock.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

Please let us know if any of these suggestions are of any help. What you learn
may help others in the future, and that's the purpose of these forums.
 
Hi Chuck

Sorry for such a delay, but I finally managed to use your advise and check
my network.

I have only two computers left on my network. One runs Windows 2000 SP 4 and
the other Windows XP Home SP 2. I connected to Internet through cable modem
and lan uses D-Link Router-hub. Computer with W2K also has NOC Extranet
Access adapter to connect to my wife's work network. Ipconfig for W2K show no
problems and for Windows XP - only node type "Unknown" and WINS proxy
"enabled". Editing Registry key did not change this. Sorry, but I could not
get how I can attach browstat files to this message, but they both have error
"53".

Also what I found that if I disable IPX/SPX on any of this two computers W2K
machine could not connest to Windows XP one, but the latter one would connect
to former with lightning speed. However, after enabling IPS/SPX, both
computers see each other, but Windows XP machine connects to another one with
20-sec delay.

BTW, Windows XP machine cannot show Windows Firewall settings - erroe
message reads "Due to unindentified problem, Windows cannot display Windows
Firewall settings."
 
Hi Chuck

Sorry for such a delay, but I finally managed to use your advise and check
my network.

I have only two computers left on my network. One runs Windows 2000 SP 4 and
the other Windows XP Home SP 2. I connected to Internet through cable modem
and lan uses D-Link Router-hub. Computer with W2K also has NOC Extranet
Access adapter to connect to my wife's work network. Ipconfig for W2K show no
problems and for Windows XP - only node type "Unknown" and WINS proxy
"enabled". Editing Registry key did not change this. Sorry, but I could not
get how I can attach browstat files to this message, but they both have error
"53".

Also what I found that if I disable IPX/SPX on any of this two computers W2K
machine could not connest to Windows XP one, but the latter one would connect
to former with lightning speed. However, after enabling IPS/SPX, both
computers see each other, but Windows XP machine connects to another one with
20-sec delay.

BTW, Windows XP machine cannot show Windows Firewall settings - erroe
message reads "Due to unindentified problem, Windows cannot display Windows
Firewall settings."
Click to expand...

OK, THERE is one problem. Running IPX/SPX and NetBIOS Over TCP/IP will cause
latency problems, exactly what you're complaining about. Please remove excess
protocols, and try again.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html
 
Hi Chuck,

Unfortunatel, I cannot remove anything on any of two my computers because
after that my W2K computer couldn't see th other one (except one case - I can
remove IPX binding for Client for Microsoft Networks in Advanced settings for
Network and Dial-up connectionson XP machine.

However, I found out that if I delete all extra protocols on XP machine, it
opens the other machine folders fast, but the W2K machine could not see this
one as I mentioned above
 
Hi Chuck,

Unfortunatel, I cannot remove anything on any of two my computers because
after that my W2K computer couldn't see th other one (except one case - I can
remove IPX binding for Client for Microsoft Networks in Advanced settings for
Network and Dial-up connectionson XP machine.

However, I found out that if I delete all extra protocols on XP machine, it
opens the other machine folders fast, but the W2K machine could not see this
one as I mentioned above
Click to expand...

Elvart,

Please don't confuse workarounds with solutions. If you're running IPX/SPX
because one of your computers won't connect without IPX/SPX, you ought to fix
that problem, not add to it. If you're going to run extra protocols like
IPX/SPX, you should expect latency. On any properly setup LAN, NetBIOS Over
TCP/IP is the only transport needed.
<http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html>
http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html
 
The question is how to set up a properly run LAN without extra protocols?
Click to expand...

There is but one network configuration that requires IPX/SPX. All others will
run very well using NBT and TCP/IP.
<http://nitecruzr.blogspot.com/2005/05/one-unique-case-where-ipxspx-may-help.html>
http://nitecruzr.blogspot.com/2005/05/one-unique-case-where-ipxspx-may-help.html
<http://nitecruzr.blogspot.com/2005/07/windows-networking.html>
http://nitecruzr.blogspot.com/2005/07/windows-networking.html

Start by describing each computer, and how each connects to the others. An
"ipconfig /all" from each may help too. Read this article, and linked articles,
and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
 
Hi Chuck,

This is a description of my home LAN:
I have two computers that are connecetd to each other through NAT router-hub
One computer runs Windows XP Home SP2 (network name-magellan) and this is
its ipconfig.txt

Windows IP Configuration



Host Name . . . . . . . . . . . . : magellan

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : Yes

DNS Suffix Search List. . . . . . : nyc.rr.com



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : nyc.rr.com

Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet NIC

Physical Address. . . . . . . . . : 00-04-61-42-19-47

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.127

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 24.29.103.10

Lease Obtained. . . . . . . . . . : Tuesday, September 27, 2005
2:35:21 PM

Lease Expires . . . . . . . . . . : Tuesday, October 04, 2005
2:35:21 PM


and browstat.txt


Status for domain FAMILY on transport \Device\NwlnkNb
Browsing is active on domain.
Master browser name is: PRINTER-CONNECT
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
\\\\PRINTER-CONNEC. Version:05.00 Flags: 51203 NT POTENTIAL MASTER
2 backup servers retrieved from master PRINTER-CONNECT
\\MAGELLAN
\\PRINTER-CONNECT
There are 2 servers in domain FAMILY on transport \Device\NwlnkNb
There are 1 domains in domain FAMILY on transport \Device\NwlnkNb


Status for domain FAMILY on transport
\Device\NetBT_Tcpip_{4EA21F27-00BA-4ACF-B8DD-09FC17947A36}
Browsing is active on domain.
Master browser name is: PRINTER-CONNECT
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
\\\\PRINTER-CONNEC. Version:05.00 Flags: 51203 NT POTENTIAL MASTER
2 backup servers retrieved from master PRINTER-CONNECT
\\PRINTER-CONNECT
\\MAGELLAN
There are 2 servers in domain FAMILY on transport
\Device\NetBT_Tcpip_{4EA21F27-00BA-4ACF-B8DD-09FC17947A36}
There are 1 domains in domain FAMILY on transport
\Device\NetBT_Tcpip_{4EA21F27-00BA-4ACF-B8DD-09FC17947A36}


Status for domain FAMILY on transport \Device\NwlnkIpx
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Second computer runs W2K Pro SP4 (network name-printer connect) and this is
its ipconfig.txt

Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : printer-connect
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : nyc.rr.com

Ethernet adapter {E4B7F278-8A25-4FB7-8760-01A8E4EE034D}:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NOC Extranet Access Adapter

Physical Address. . . . . . . . . : 44-45-53-54-42-00

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 0.0.0.0

Subnet Mask . . . . . . . . . . . : 0.0.0.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . :

Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : nyc.rr.com
Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
Adapter(LNE100TX v4)
Physical Address. . . . . . . . . : 00-20-78-11-04-EA

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.191

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 24.29.103.10
Lease Obtained. . . . . . . . . . : Tuesday, September 27, 2005 1:42:28 PM

Lease Expires . . . . . . . . . . : Tuesday, October 04, 2005 1:42:28 PM

and browstat.txt

Status for domain FAMILY on transport
\Device\Nbf_NdisWanNbfOut{AD9056BA-BE81-42A5-AEFE-DAEB377E2E3D}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain FAMILY on transport
\Device\Nbf_NdisWanNbfIn{A6390551-E658-4F6B-A424-8D7264B069C6}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain FAMILY on transport
\Device\Nbf_NdisWanNbfIn{9AEBFCA2-56ED-47EE-9F04-9B1F6A86B3B6}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain FAMILY on transport
\Device\Nbf_NdisWanNbfIn{6A99B0FC-C49C-4F1C-830A-59E5A0289736}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain FAMILY on transport
\Device\Nbf_NdisWanNbfOut{D7DC142C-94A6-4AC8-94ED-454ACF395F84}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain FAMILY on transport
\Device\Nbf_NdisWanNbfOut{47C2E0FD-52F1-49F0-B5B7-D557D4690E2C}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain FAMILY on transport
\Device\Nbf_{E4B7F278-8A25-4FB7-8760-01A8E4EE034D}
Browsing is active on domain.
Master browser name is: PRINTER-CONNECT
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
\\\\PRINTER-CONNEC. Version:05.00 Flags: 51203 NT POTENTIAL MASTER
1 backup servers retrieved from master PRINTER-CONNECT
\\PRINTER-CONNECT
There are 1 servers in domain FAMILY on transport
\Device\Nbf_{E4B7F278-8A25-4FB7-8760-01A8E4EE034D}
There are 1 domains in domain FAMILY on transport
\Device\Nbf_{E4B7F278-8A25-4FB7-8760-01A8E4EE034D}


Status for domain FAMILY on transport \Device\NwlnkNb
Browsing is active on domain.
Master name cannot be determined from GetAdapterStatus. Using
\\PRINTER-CONNECT
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
\\\\PRINTER-CONNEC. Version:05.00 Flags: 51203 NT POTENTIAL MASTER
1 backup servers retrieved from master PRINTER-CONNECT
\\PRINTER-CONNECT
There are 2 servers in domain FAMILY on transport \Device\NwlnkNb
There are 1 domains in domain FAMILY on transport \Device\NwlnkNb


Status for domain FAMILY on transport
\Device\NetBT_Tcpip_{98AECC4A-D412-4C77-BACF-1021D68E4DCB}
Browsing is active on domain.
Master browser name is: PRINTER-CONNECT
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
\\\\PRINTER-CONNEC. Version:05.00 Flags: 51203 NT POTENTIAL MASTER
1 backup servers retrieved from master PRINTER-CONNECT
\\PRINTER-CONNECT
There are 2 servers in domain FAMILY on transport
\Device\NetBT_Tcpip_{98AECC4A-D412-4C77-BACF-1021D68E4DCB}
There are 1 domains in domain FAMILY on transport
\Device\NetBT_Tcpip_{98AECC4A-D412-4C77-BACF-1021D68E4DCB}

Both computers could net view itself and the other one and could ping itself
by IP address and name. Both of them cannot ping the other one neither by
name nor by IP address.

W2K computer also is used by wife to connect remotely to her work network
when she works from home.
 
Hi Chuck,

This is a description of my home LAN:
I have two computers that are connecetd to each other through NAT router-hub
One computer runs Windows XP Home SP2 (network name-magellan) and this is
its ipconfig.txt
Click to expand...

Both computers could net view itself and the other one and could ping itself
by IP address and name. Both of them cannot ping the other one neither by
name nor by IP address.

W2K computer also is used by wife to connect remotely to her work network
when she works from home.
Click to expand...

Elvart,

You have a lot of interesting (how useful is the question?) transports there.

Magellan
NetBEUI
\Device\NwlnkNb
There are 2 servers in domain FAMILY on transport \Device\NwlnkNb
There are 1 domains in domain FAMILY on transport \Device\NwlnkNb
NetBIOS Over TCP/IP
\Device\NetBT_Tcpip_{4EA21F27-00BA-4ACF-B8DD-09FC17947A36}
Browsing is active on domain.
There are 2 servers in domain FAMILY on transport
\Device\NetBT_Tcpip_{4EA21F27-00BA-4ACF-B8DD-09FC17947A36}
There are 1 domains in domain FAMILY on transport
\Device\NetBT_Tcpip_{4EA21F27-00BA-4ACF-B8DD-09FC17947A36}
IPX/SPX
\Device\NwlnkIpx
Browsing is NOT active on domain.

Printer-connect
NetBEUI
\Device\Nbf_NdisWanNbfOut{AD9056BA-BE81-42A5-AEFE-DAEB377E2E3D}
Browsing is NOT active on domain.
Device\Nbf_{E4B7F278-8A25-4FB7-8760-01A8E4EE034D}
Browsing is active on domain.
There are 1 servers in domain FAMILY on transport
\Device\Nbf_{E4B7F278-8A25-4FB7-8760-01A8E4EE034D}
\Device\NwlnkNb
Browsing is active on domain.
NetBIOS Over TCP/IP
\Device\NetBT_Tcpip_{98AECC4A-D412-4C77-BACF-1021D68E4DCB}
Browsing is active on domain.
There are 2 servers in domain FAMILY on transport
\Device\NetBT_Tcpip_{98AECC4A-D412-4C77-BACF-1021D68E4DCB}

OK, I think I see what you're doing here. You have Printer-connect, with a
dialup or VPN client. That could create a need similar to the scenario I
describe as justifying use of IPX / SPX. But you're not using IPX / SPX for
file sharing, you're using NetBEUI. Those are two separate transports, and you
don't need both IPX/SPX and NetBEUI.

Try removing just IPX/SPX from Magellan. You can do that without removing
NetBEUI. If file sharing is bound to both IPX/SPX, NetBEUI, and NetBIOS Over
TCP/IP, that would certainly be a recipe for latency.

Your first post says "I have three computers on home network". Here you show
just two. Is the third identical to Magellan? Why do both Magellan and
Printer-connect see just 2 servers? Why does Printer-connect see only 1 server
thru NetBEUI?

I think you have a few questions to answer.
 
Hi Chuck, third computer moved to college with my other son. So, I have only
two now.

About NetBEUI. I checked Properties for LAN connection on both machines -
NetBEUI was not checked on bothe. Also, in Advanced Settings for Network and
Dial up connections NetBEUI was unchecked for both Client for Microsoft
network and File and Printer Sharing on both computers.

As soon as I unchecked IPX/SPX on Magellan Printer-connect stopped seeing
Magellan - "\\Magellan is not accessible. The network path was not found".
Also, I noticed that when user on Magella is not the same as on
Printer-connect, Printer-Connect is openning Microsoft Windows Network and
Family very slow.

BTW, you were right, Printer-connect has VPN.
 
Hi Chuck,

I sent you a reply with an info to your questions on 27th, but did not
receive any response.

Any reason for this?
 
Hi Chuck, third computer moved to college with my other son. So, I have only
two now.

About NetBEUI. I checked Properties for LAN connection on both machines -
NetBEUI was not checked on bothe. Also, in Advanced Settings for Network and
Dial up connections NetBEUI was unchecked for both Client for Microsoft
network and File and Printer Sharing on both computers.

As soon as I unchecked IPX/SPX on Magellan Printer-connect stopped seeing
Magellan - "\\Magellan is not accessible. The network path was not found".
Also, I noticed that when user on Magella is not the same as on
Printer-connect, Printer-Connect is openning Microsoft Windows Network and
Family very slow.

BTW, you were right, Printer-connect has VPN.
Click to expand...

Elvart,

Look at browstat for Magellan:
Status for domain FAMILY on transport \Device\NwlnkIpx
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

And browstat on Printer-Connect:
There are 1 servers in domain FAMILY on transport
\Device\Nbf_{E4B7F278-8A25-4FB7-8760-01A8E4EE034D}

Yet you say:
As soon as I unchecked IPX/SPX on Magellan Printer-connect stopped seeing
Magellan - "\\Magellan is not accessible. The network path was not found".

You have a protocol mismatch. Your best solution would be to un install both
IPX/SPX and NetBEUI from both computers (don't just disable them either), and
fix the IP problem. But you have to find out what protocols your wife's
computer requires at work, and on the VPN. If her computer requires either for
her work, you'll just be digging a bigger hole for yourself.

Let's try and solve the "error = 53" first. An "error = 53" can have many
causes.
<http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>

If we can get file sharing working over TCP/IP / NBT, you should be better
prepared to un install IPX/SPX and NetBEUI. So let's concentrate on the "error
= 53".

BTW, when you top post (putting your answers at the top), and you have a
signature delimited by a line "-- ", email programs that work according to
standards will truncate the message after the "-- " line, when formatting
replies.

You should either bottom post (as I am doing), or eliminate your signature. The
way you are currently doing, it's kind of hard to reply properly. And bottom
posting makes it hella easier to follow the conversation.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
 
Chuck said:
Elvart,

Look at browstat for Magellan:
Status for domain FAMILY on transport \Device\NwlnkIpx
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

And browstat on Printer-Connect:
There are 1 servers in domain FAMILY on transport
\Device\Nbf_{E4B7F278-8A25-4FB7-8760-01A8E4EE034D}

Yet you say:
As soon as I unchecked IPX/SPX on Magellan Printer-connect stopped seeing
Magellan - "\\Magellan is not accessible. The network path was not found".

You have a protocol mismatch. Your best solution would be to un install both
IPX/SPX and NetBEUI from both computers (don't just disable them either), and
fix the IP problem. But you have to find out what protocols your wife's
computer requires at work, and on the VPN. If her computer requires either for
her work, you'll just be digging a bigger hole for yourself.

Let's try and solve the "error = 53" first. An "error = 53" can have many
causes.
<http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>

If we can get file sharing working over TCP/IP / NBT, you should be better
prepared to un install IPX/SPX and NetBEUI. So let's concentrate on the "error
= 53".

BTW, when you top post (putting your answers at the top), and you have a
signature delimited by a line "-- ", email programs that work according to
standards will truncate the message after the "-- " line, when formatting
replies.

You should either bottom post (as I am doing), or eliminate your signature. The
way you are currently doing, it's kind of hard to reply properly. And bottom
posting makes it hella easier to follow the conversation.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
Click to expand...
Hi Chuck,

It took me quite some time to do everything you've written about "error 53"/

I checked LSP/Winsock and used WinsockFix on both machines - everything
seems fine.
Firewall - I have Sygate Security Agent 4.0 on both machines, On
printer-connect i Have to have it bc of wife's work. What I noticed that with
firewall Printer-connect could no ping magellan either by name or IP and vice
versa.
Registry settings restrictanonymous on printer-connect and magellan seem OK,
but Magellan has restrictanonymoussam value (1).
Node type on printer-connect is Broadcast and no Magellan - Unknown and this
I was not able to change using your advice about changing registry.

And about protocols - my wife is still trying to find out which exactly ones
she needs to work from home.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Cannot Access Computers on Home Network 5
Networking failure 3
Access to Workgroup computers 6
Home Networking setup problems 1
Can Not Access One Computer On Home Network 2
network sharing problem with xp pro 2
Can't access computers on network 6
Networking failure again 4

Back
Top