Network Problems

G

Guest

2 PCs on Windows Network.
Each with a NIC and ethernet cable to connect to router.

Problem is that often when I open windows explorer on either
machine it takes ages to show the Hard Disk contents.

On both machines the "Automatically search for network folders"
is ticked off.

On the router Unpnp is enabled under secure settings.

TCP/IP settings on both machines set to automatically detect settings
and assign IP address. Only the DNS server IP addresses entered manually.

Any advice greatly appreciated.

Thanks
 
C

Chuck

2 PCs on Windows Network.
Each with a NIC and ethernet cable to connect to router.

Problem is that often when I open windows explorer on either
machine it takes ages to show the Hard Disk contents.

On both machines the "Automatically search for network folders"
is ticked off.

On the router Unpnp is enabled under secure settings.

TCP/IP settings on both machines set to automatically detect settings
and assign IP address. Only the DNS server IP addresses entered manually.

Any advice greatly appreciated.

Thanks

Joaquin,

How many folders, and files, are in the root of the drive that opens with
Windows Explorer?

If you can provide "browstat status" and "ipconfig /all" from each computer, we
can probably diagnose the problem. Read this article, and linked articles, and
follow instructions precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp
 
G

Guest

HelloChuck

Much obliged for your reply. Please find below results for each PC after
carrying out instructions.

PC1

browstat.txt contents:

Status for domain FLIGHTSIM on transport
\Device\NetBT_Tcpip_{E964AACB-99AC-49B0-8C70-0003E96A859F}
Browsing is active on domain.
Master browser name is: FSMASTER
Master browser is running build 2600
1 backup servers retrieved from master FSMASTER
\\FSMASTER
There are 2 servers in domain FLIGHTSIM on transport
\Device\NetBT_Tcpip_{E964AACB-99AC-49B0-8C70-0003E96A859F}
There are 1 domains in domain FLIGHTSIM on transport
\Device\NetBT_Tcpip_{E964AACB-99AC-49B0-8C70-0003E96A859F}

ipconfig.txt contents:

Windows IP Configuration



Host Name . . . . . . . . . . . . : fsmaster

Primary Dns Suffix . . . . . . . :

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

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

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



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : ASUSTeK/Broadcom 440x 10/100
Integrated Controller

Physical Address. . . . . . . . . : 00-E0-18-A2-38-B3

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.254.1

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

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

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

158.152.1.43

PC2

Browstat.txt contents:

Status for domain FLIGHTSIM on transport
\Device\NetBT_Tcpip_{E9AEEA73-28AD-4B1E-B7D3-22C7035FD111}
Browsing is active on domain.
Master browser name is: FSMASTER
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
\\\\FSMASTER . Version:05.01 Flags: 51003 NT POTENTIAL MASTER
1 backup servers retrieved from master FSMASTER
\\FSMASTER
There are 2 servers in domain FLIGHTSIM on transport
\Device\NetBT_Tcpip_{E9AEEA73-28AD-4B1E-B7D3-22C7035FD111}
There are 1 domains in domain FLIGHTSIM on transport
\Device\NetBT_Tcpip_{E9AEEA73-28AD-4B1E-B7D3-22C7035FD111}

ipconfig.txt contents:

Windows IP Configuration



Host Name . . . . . . . . . . . . : fsslave

Primary Dns Suffix . . . . . . . :

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

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

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



Ethernet adapter Local Area Connection 2:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
Adapter(LNE100TX v4) #2

Physical Address. . . . . . . . . : 00-12-17-4D-E5-5E

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.254.2

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

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

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

158.152.1.43


Looks as if there may be something wrong with PC2. Thanks for your help.

Regards

Joaquin
 
C

Chuck

HelloChuck

Much obliged for your reply. Please find below results for each PC after
carrying out instructions.

Looks as if there may be something wrong with PC2. Thanks for your help.

Regards

Joaquin

Joaquin,

PC2 (FSSlave) has trouble resolving the name of FSMaster to an address. The
problem is possibly in FSSlave, but I'll put even money on FSMaster. Let's do
some basic analysis.
# Both computers on same subnet 192.168.254/24, fixed settings, same DNS
servers, same Default Gateway.
# Both computers have Unknown node type, and no WINS server defined. This uses
Broadcast name resolution.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Unknown>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Unknown
# Both computers on same domain / workgroup FLIGHTSIM, and both acknowledge same
master browser FSMaster. Both computers see each other as servers ("There are 2
servers in domain FLIGHTSIM").
# Both computers run NetBIOS Over TCP (NBT), no other protocol or transport.

Please verify that NBT is explicitly Enabled on both computers.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components

Check FSMaster. One of the most common causes of this problem would be a
misconfigured or overlooked personal firewall, or other security component.
There are other possibilities too. Read this article with an open mind.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

Check your Hosts and LMHosts files - do you have entries in either for local
name resolution?
<http://nitecruzr.blogspot.com/2005/07/local-name-and-address-resolution-on.html>
http://nitecruzr.blogspot.com/2005/07/local-name-and-address-resolution-on.html

If no useful change or observation made yet, take the following code (everything
INSIDE the "#####" lines). Please DO NOT include ANY portion of the "#####"
lines. (Please verify computer names and ip addresses).

1. Open Notepad. Ensure that Format - Word Wrap is not checked. Highlight
then Copy the code (Ctrl-C), precisely as it is presented, and Paste (Ctrl-V)
into Notepad. Verify, and correct, names and addresses if necessary.
2. Save the Notepad file as "cdiag.cmd", as type "All Files", into the root
folder "C:\".
3. Run it by Start - Run - "c:\cdiag".
4. Wait patiently.
5. When Notepad opens up displaying c:\cdiag.txt, first check Format and
ensure that Word Wrap is NOT checked! Then, copy the entire contents (Ctrl-A
Ctrl-C) and paste (Ctrl-V) into your next post.

Do this from all computers, please, with all computers powered up and online.

##### Start CDiag Assembled Code

@echo off
set FullTarget1=fsmaster 192.168.254.1
set FullTarget2=fsslave 192.168.254.2
set FullTarget3=
set FullTarget4=
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set FullTargets=%FullTargets% 127.0.0.1
set PingTargets=www.yahoo.com 66.94.230.32 192.168.254.254
Set Version=V1.34
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Enumerate Shares >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net share >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Adhoc Browser View >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Full Targets %FullTargets% >>c:\cdiag.txt
for %%a in (%FullTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% net view %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view %%a >>c:\cdiag.txt
)
@echo. >>c:\cdiag.txt
@echo Ping Targets %PingTargets% >>c:\cdiag.txt
for %%a in (%PingTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
)
@echo. >>c:\cdiag.txt
@echo End diagnosis for %computername% >>c:\cdiag.txt
notepad c:\cdiag.txt
:EOF

##### End CDiag Assembled Code
 
G

Guest

Hello Chuck

I've read through all the links you kindly sent me and found a few things
missing. Namely:

Net BIOS over TCP/IP was not enabled on both.

TCP/IP Net BIOS Helper was disabled on both.

Node Type entry on registry not present on FSslave. I created the entry and
gave it the
value of 1 for Broadcast.

After making the changes I rebooted and everything seemed to work OK. I even
run CDiag.cmd on both and there were no visible errors or packet loss. I can
post
the result here if you think it necessary, but they contain quite a bit of
text.

I will see what happens over the next couple of days and if all appears well
then
will assume this issue is resolved.

What can I tell you.....your posts and links have been quite an education
for someone
like me with little Network experience. Sincere thanks for your trouble.

Regards

Joaquin
 
C

Chuck

Hello Chuck

I've read through all the links you kindly sent me and found a few things
missing. Namely:

Net BIOS over TCP/IP was not enabled on both.

TCP/IP Net BIOS Helper was disabled on both.

Node Type entry on registry not present on FSslave. I created the entry and
gave it the
value of 1 for Broadcast.

After making the changes I rebooted and everything seemed to work OK. I even
run CDiag.cmd on both and there were no visible errors or packet loss. I can
post
the result here if you think it necessary, but they contain quite a bit of
text.

I will see what happens over the next couple of days and if all appears well
then
will assume this issue is resolved.

What can I tell you.....your posts and links have been quite an education
for someone
like me with little Network experience. Sincere thanks for your trouble.

Regards

Joaquin

Joaquin,

If you made the changes, and everything is working, then there's no need to post
diagnostics. The articles did their job, and that's that. NBT was, I would
guess, the key.

Thanks for the feedback, and the update.
 

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

Top