File & Printer Sharing Problem

L

Linda Callard

We have two Windows XP Pro SP2 computers (laptop & desktop) that were
networked successfully. One of the computers (laptop) needed to be
formatted and all software reinstalled. Have not been able to re-establish
network satisfactorily. The desktop has full access to the laptop's shared
files and printer, but the laptop cannot access the desktop's shared files
and printers. While the laptop can see the desktop's shared folders and
printers, it cannot neither see the contents of the folders nor install the
printer drivers. Interestingly, the desktop computer cannot see its own
shared folders when trying to access through "My Network Places." This
seems to indicate a problem with the desktop, even though its configuration
was not knowingly changed.

We've turned off all firewalls, run the network setup wizard repeatedly, and
consulted the 23 page "Troubleshooting File and Printer Sharing in Microsoft
Windows XP" guide without success.

Help!
 
C

Chuck

We have two Windows XP Pro SP2 computers (laptop & desktop) that were
networked successfully. One of the computers (laptop) needed to be
formatted and all software reinstalled. Have not been able to re-establish
network satisfactorily. The desktop has full access to the laptop's shared
files and printer, but the laptop cannot access the desktop's shared files
and printers. While the laptop can see the desktop's shared folders and
printers, it cannot neither see the contents of the folders nor install the
printer drivers. Interestingly, the desktop computer cannot see its own
shared folders when trying to access through "My Network Places." This
seems to indicate a problem with the desktop, even though its configuration
was not knowingly changed.

We've turned off all firewalls, run the network setup wizard repeatedly, and
consulted the 23 page "Troubleshooting File and Printer Sharing in Microsoft
Windows XP" guide without success.

Help!
Click to expand...

Linda,

Make sure the browser service is running on the desktop computer. Control Panel
- Administrative Tools - Services. Verify that the Computer Browser, and the
TCP/IP NetBIOS Helper, services both show with Status = Started. Disable the
browser on the laptop computer.

On each computer, check to see if Simple File Sharing (Control Panel - Folder
Options - View - Advanced settings) is enabled or disabled. You need to have
SFS consistently set on each computer.

On XP Pro with SFS disabled, check the Local Security Policies (Control Panel -
Administrative Tools). Under Local Policies - Security Options, look at
"Network access: Sharing and security model", and ensure it's set to "Classic -
local users authenticate as themselves".

On XP Pro with SFS disabled, if you set the above Local Security Policy to
"Guest only", enable the Guest account, using Start - Run - "cmd" - type "net
user guest /active:yes" in the command window. If "Classic", setup and use a
common non-Guest account on all computers. Whichever account is used, give it
an identical, non-blank password on all computers.

On XP Pro with Simple File Sharing enabled, make sure that the Guest account is
enabled, on each computer. Enable Guest with Start - Run - "cmd" - type "net
user guest /active:yes" in the command window.

On XP Pro, if you're going to use Guest authentication, check your Local
Security Policy (Control Panel - Administrative Tools) - User Rights Assignment,
on the XP Pro computer, and look at "Deny access to this computer from the
network". Make sure Guest is not in the list.
 
C

Carey Holzman

You are welcome to email me if you would like to work on this one-on-one.

(e-mail address removed)
 
L

Lou Ramsey

Carey said:
You are welcome to email me if you would like to work on this one-on-one.

(e-mail address removed)
Click to expand...

Linda,

From other posts by Carey, it appears that his altruistic offer to
provide you with free, one-on-one advice is prompted by his inability to
accept criticism. Criticism is an unavoidable result of posting on
Usenet. Instead of posting his advice on Usenet, so all can see and
learn, he chooses to provide advice thru email.

Consider carefully the free advice which he provides. If the advice
includes instructions to install additional network components, consider
this.

The Windows platform (including Windows 9x and NT/2000/XP) has its
networking infrastructure based upon TCP/IP, with NetBIOS Over TCP/IP
(NBT) used as an interface between TCP/IP and the various networking
applications.

Any properly configured installation of Windows will run just fine with
these components.

Be selective when accepting advice, web pages or otherwise, that
contains instructions to install redundant and unnecessary components,
such as IPX/SPX or NetBEUI. Adding these extra components may serve as
a workaround, but will add needless complications that may cause
problems in the future.

Diagnose and fix the problem - don't just fix the symptoms.
 
C

Carey Holzman

Cut and paste Lou... You're quite the hero saving these people from being
helped.

I have no idea what I did to you to warrant such an outburst, but personal
attacks are best left in email. This is not the place for it.

Thanks for your cooperation.

Carey
 
M

Malke

Carey said:
Cut and paste Lou... You're quite the hero saving these people from
being helped.

I have no idea what I did to you to warrant such an outburst, but
personal attacks are best left in email. This is not the place for it.

Thanks for your cooperation.
Click to expand...
Setting aside any personal remarks that may or may not have been made,
you've been asked over and over again to keep the answers in the
newsgroup so they benefit everyone, not just one poster. Yet you
persist in trying to take posts to private email. Why?

And yes, I cut and pasted this from another post, just as you cut and
paste your offer of email support. The fact that I've done so doesn't
invalidate the data.

Malke
 
L

Linda Callard

Chuck said:
Linda,

Make sure the browser service is running on the desktop computer. Control
Panel
- Administrative Tools - Services. Verify that the Computer Browser, and
the
TCP/IP NetBIOS Helper, services both show with Status = Started. Disable
the
browser on the laptop computer.

On each computer, check to see if Simple File Sharing (Control Panel -
Folder
Options - View - Advanced settings) is enabled or disabled. You need to
have
SFS consistently set on each computer.

On XP Pro with SFS disabled, check the Local Security Policies (Control
Panel -
Administrative Tools). Under Local Policies - Security Options, look at
"Network access: Sharing and security model", and ensure it's set to
"Classic -
local users authenticate as themselves".

On XP Pro with SFS disabled, if you set the above Local Security Policy to
"Guest only", enable the Guest account, using Start - Run - "cmd" - type
"net
user guest /active:yes" in the command window. If "Classic", setup and
use a
common non-Guest account on all computers. Whichever account is used,
give it
an identical, non-blank password on all computers.

On XP Pro with Simple File Sharing enabled, make sure that the Guest
account is
enabled, on each computer. Enable Guest with Start - Run - "cmd" - type
"net
user guest /active:yes" in the command window.

On XP Pro, if you're going to use Guest authentication, check your Local
Security Policy (Control Panel - Administrative Tools) - User Rights
Assignment,
on the XP Pro computer, and look at "Deny access to this computer from the
network". Make sure Guest is not in the list.
Click to expand...

Thanks, Chuck. We followed your recommendations (with SFS enabled, as that
was our previous setup), but to no avail. Given that the desktop cannot
access its own shared files through "My Network Places," irrespective
of whether the laptop is connected to the LAN, we believe that some setting
on the desktop has been changed or become corrupted when we tried to
re-establish the LAN after rebuilding the laptop's HD. The desktop shared
folder does not appear under our "Local Network" heading, but under
"unspecified." Is this a clue?

If you had any other suggestions, we'd like to hear them. Does anyone know
if there is an online network analyzer that would automatically check our
configuration?
 
C

Chuck

Thanks, Chuck. We followed your recommendations (with SFS enabled, as that
was our previous setup), but to no avail. Given that the desktop cannot
access its own shared files through "My Network Places," irrespective
of whether the laptop is connected to the LAN, we believe that some setting
on the desktop has been changed or become corrupted when we tried to
re-establish the LAN after rebuilding the laptop's HD. The desktop shared
folder does not appear under our "Local Network" heading, but under
"unspecified." Is this a clue?
Click to expand...

Linda,

I have some standard tests which should point us in the right direction.

Please start by providing ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, make sure that Format - Word Wrap is
NOT checked!, copy and paste entire contents into your next post. Identify
operating system (by name, version, and SP level) with each ipconfig listing.
 
L

Linda Callard

Chuck said:
Linda,

I have some standard tests which should point us in the right direction.

Please start by providing ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the
command
window - Open c:\ipconfig.txt in Notepad, make sure that Format - Word
Wrap is
NOT checked!, copy and paste entire contents into your next post.
Identify
operating system (by name, version, and SP level) with each ipconfig
listing.
Click to expand...


Chuck, both computers are running WinXP Pro SP2. CCS-PC5 is the laptop and
CCS-PC6
is the desktop. Here are the ipconfig data you requested - hope it means
something to you!


------------------------------------------------
CCS-PC5 laptop -
Windows IP Configuration

Host Name . . . . . . . . . . . . : CCS-PC5
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : CCS-NET

Ethernet adapter CCS-Net:

Connection-specific DNS Suffix . : CCS-NET
Description . . . . . . . . . . . : Intel(R) PRO/100+ MiniPCI
Physical Address. . . . . . . . . : 00-10-A4-0C-04-DA
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.185
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::210:a4ff:fe0c:4da%4
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : 20 November 2004 17:26:52
Lease Expires . . . . . . . . . . : 20 November 2004 18:26:52

PPP adapter PEI - Charlottetown:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 142.176.115.88
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 142.176.115.88
DNS Servers . . . . . . . . . . . : 142.176.17.8
142.176.17.9
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-FA-9D-71-4F-8C-A7
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter 6to4 Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6to4 Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 8E-B0-73-58
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 2002:8eb0:7358::8eb0:7358
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
2002:836b:213c::836b:213c
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : 8E-B0-73-58
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:142.176.115.88%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . : CCS-NET
Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : C0-A8-00-B9
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.185%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

------------------------------------------------

CCS-PC6 desktop -
Windows IP Configuration

Host Name . . . . . . . . . . . . : CCS-PC6
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : CCS-NET

Ethernet adapter CCS-NET:

Connection-specific DNS Suffix . : CCS-NET
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection #2
Physical Address. . . . . . . . . : 00-E0-18-5C-50-58
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.134
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::2e0:18ff:fe5c:5058%4
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : 19 November 2004 14:26:16
Lease Expires . . . . . . . . . . : 19 November 2004 15:26:16

PPP adapter PEI - Charlottetown:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 142.176.125.144
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 142.176.125.144
DNS Servers . . . . . . . . . . . : 142.176.17.8
142.176.17.9
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter 6to4 Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6to4 Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 8E-B0-7D-90
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 2002:8eb0:7d90::8eb0:7d90
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
2002:836b:213c::836b:213c
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : 8E-B0-7D-90
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:142.176.125.144%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . : CCS-NET
Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : C0-A8-00-86
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.134%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled
------------------------------------------------
 
C

Chuck

Linda,

This sounds like a browser (no, not Internet Explorer) problem. Let's start
there.

The Microsoft Browstat program will show us what browsers you have in your
domain / workgroup, at any time.
http://support.microsoft.com/?id=188305

You can download Browstat from either:
<http://www.dynawell.com/reskit/microsoft/win2000/browstat.zip>
<http://rescomp.stanford.edu/staff/manual/rcc/tools/browstat.zip>

Browstat is very small (40K), and needs no install. Just unzip the downloaded
file, copy browstat.exe to any folder in the Path, and run it from a command
window, by "browstat status". Make sure all computers give the same result.

For more information about the browser subsystem (very intricate), see:
http://support.microsoft.com/?id=188001
http://support.microsoft.com/?id=188305
<http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx>

Provide browstat information for each computer.
Start - Run - "cmd". Type "browstat status >c:\browstat.txt" into the command
window - Open c:\browstat.txt in Notepad, make sure that Format - Word Wrap is
NOT checked!, copy and paste into your next post. Identify each computer by
name and operating system.
 
L

Linda Callard

Chuck said:
Linda,

This sounds like a browser (no, not Internet Explorer) problem. Let's
start
there.

The Microsoft Browstat program will show us what browsers you have in your
domain / workgroup, at any time.
http://support.microsoft.com/?id=188305

You can download Browstat from either:
<http://www.dynawell.com/reskit/microsoft/win2000/browstat.zip>
<http://rescomp.stanford.edu/staff/manual/rcc/tools/browstat.zip>

Browstat is very small (40K), and needs no install. Just unzip the
downloaded
file, copy browstat.exe to any folder in the Path, and run it from a
command
window, by "browstat status". Make sure all computers give the same
result.

For more information about the browser subsystem (very intricate), see:
http://support.microsoft.com/?id=188001
http://support.microsoft.com/?id=188305
<http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx>

Provide browstat information for each computer.
Start - Run - "cmd". Type "browstat status >c:\browstat.txt" into the
command
window - Open c:\browstat.txt in Notepad, make sure that Format - Word
Wrap is
NOT checked!, copy and paste into your next post. Identify each computer
by
name and operating system.
Click to expand...


---------------------------------------------
CCS-PC5 Laptop:

Status for domain CCS-NET on transport \Device\NwlnkNb
Browsing is active on domain.
Master name cannot be determined from GetAdapterStatus. Using \\CCS-PC5
Master browser is running build 2600
1 backup servers retrieved from master CCS-PC5
\\CCS-PC5
There are 1 servers in domain CCS-NET on transport \Device\NwlnkNb
There are 1 domains in domain CCS-NET on transport \Device\NwlnkNb

Status for domain CCS-NET on transport
\Device\NetBT_Tcpip_{CB6603F1-5ADC-4E37-8F44-C660B3F3ADE9}
Browsing is active on domain.
Master browser name is: CCS-PC6
Could not open key in registry, error = 5 Unable to determine build
of browser master: 5
\\\\CCS-PC6 . Version:05.01 Flags: 51603 NT POTENTIAL MASTER
1 backup servers retrieved from master CCS-PC6
\\CCS-PC6
There are 1 servers in domain CCS-NET on transport
\Device\NetBT_Tcpip_{CB6603F1-5ADC-4E37-8F44-C660B3F3ADE9}
There are 1 domains in domain CCS-NET on transport
\Device\NetBT_Tcpip_{CB6603F1-5ADC-4E37-8F44-C660B3F3ADE9}

Status for domain CCS-NET on transport \Device\NwlnkIpx
Browsing is active on domain.
Master name cannot be determined from GetAdapterStatus. Using \\CCS-PC5
Master browser is running build 2600
1 backup servers retrieved from master CCS-PC5
\\CCS-PC5
Unable to retrieve server list from CCS-PC5: 1231

---------------------------------------------
CCS-PC6 Desktop:

Status for domain CCS-NET on transport \Device\NwlnkNb
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain CCS-NET on transport
\Device\NetBT_Tcpip_{D0369A81-275B-4968-BE6D-DACAB6F5DC83}
Browsing is active on domain.
Master browser name is: CCS-PC6
Master browser is running build 2600
1 backup servers retrieved from master CCS-PC6
\\CCS-PC6
There are 0 servers in domain CCS-NET on transport
\Device\NetBT_Tcpip_{D0369A81-275B-4968-BE6D-DACAB6F5DC83}
There are 1 domains in domain CCS-NET on transport
\Device\NetBT_Tcpip_{D0369A81-275B-4968-BE6D-DACAB6F5DC83}

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

Linda Callard

Linda Callard said:
---------------------------------------------
CCS-PC5 Laptop:

Status for domain CCS-NET on transport \Device\NwlnkNb
Browsing is active on domain.
Master name cannot be determined from GetAdapterStatus. Using
\\CCS-PC5
Master browser is running build 2600
1 backup servers retrieved from master CCS-PC5
\\CCS-PC5
There are 1 servers in domain CCS-NET on transport \Device\NwlnkNb
There are 1 domains in domain CCS-NET on transport \Device\NwlnkNb

Status for domain CCS-NET on transport
\Device\NetBT_Tcpip_{CB6603F1-5ADC-4E37-8F44-C660B3F3ADE9}
Browsing is active on domain.
Master browser name is: CCS-PC6
Could not open key in registry, error = 5 Unable to determine build
of browser master: 5
\\\\CCS-PC6 . Version:05.01 Flags: 51603 NT POTENTIAL MASTER
1 backup servers retrieved from master CCS-PC6
\\CCS-PC6
There are 1 servers in domain CCS-NET on transport
\Device\NetBT_Tcpip_{CB6603F1-5ADC-4E37-8F44-C660B3F3ADE9}
There are 1 domains in domain CCS-NET on transport
\Device\NetBT_Tcpip_{CB6603F1-5ADC-4E37-8F44-C660B3F3ADE9}

Status for domain CCS-NET on transport \Device\NwlnkIpx
Browsing is active on domain.
Master name cannot be determined from GetAdapterStatus. Using
\\CCS-PC5
Master browser is running build 2600
1 backup servers retrieved from master CCS-PC5
\\CCS-PC5
Unable to retrieve server list from CCS-PC5: 1231

---------------------------------------------
CCS-PC6 Desktop:

Status for domain CCS-NET on transport \Device\NwlnkNb
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain CCS-NET on transport
\Device\NetBT_Tcpip_{D0369A81-275B-4968-BE6D-DACAB6F5DC83}
Browsing is active on domain.
Master browser name is: CCS-PC6
Master browser is running build 2600
1 backup servers retrieved from master CCS-PC6
\\CCS-PC6
There are 0 servers in domain CCS-NET on transport
\Device\NetBT_Tcpip_{D0369A81-275B-4968-BE6D-DACAB6F5DC83}
There are 1 domains in domain CCS-NET on transport
\Device\NetBT_Tcpip_{D0369A81-275B-4968-BE6D-DACAB6F5DC83}

Status for domain CCS-NET on transport \Device\NwlnkIpx
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.
Click to expand...
Chuck, was that browstat data useful?
 
C

Chuck

Chuck, was that browstat data useful?
Click to expand...

Linda,

Yes, it was very interesting.

You need to straighten out your network configuration on both computers.

Please start by un installing unnecessary components, from the list of items
under Local Area Connection Properties. You only need the following items in
the list:
Client for Microsoft Networks
File and Printer Sharing For Microsoft Networks
QoS Packet Scheduler (optional)
Internet Protocol (TCP/IP)

Make sure you have both Client for Microsoft Networks, and File and Printer
Sharing for Microsoft Networks (Local Area Connection - Properties), on each
computer. And have shares setup on each computer.

Enable NetBIOS Over TCP/IP (Local Area Connection - Properties - TCP/IP -
Properties - Advanced - WINS) on each computer.

Make sure the browser service is running on each computer. Control Panel -
Administrative Tools - Services. Verify that the Computer Browser, and the
TCP/IP NetBIOS Helper, services both show with Status = Started.

Power both computers off. Then power one on, and then the other. Check
"browstat status" again.

If no improvement, provide ipconfig information for each computer, and we'll do
some more diagnoses to tell us what to look at next.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, make sure that Format - Word Wrap is
NOT checked!, copy and paste entire contents into your next post. Identify
operating system (by name, version, and SP level) with each ipconfig listing.
Click to expand...
 
C

Chuck

Chuck, was that browstat data useful?
Click to expand...

Linda,

Yes, it was very interesting.

You need to straighten out your network configuration on both computers.

Please start by un installing unnecessary components, from the list of items
under Local Area Connection Properties. You only need the following items in
the list:
Client for Microsoft Networks
File and Printer Sharing For Microsoft Networks
QoS Packet Scheduler (optional)
Internet Protocol (TCP/IP)

Make sure you have both Client for Microsoft Networks, and File and Printer
Sharing for Microsoft Networks (Local Area Connection - Properties), on each
computer. And have shares setup on each computer.

Enable NetBIOS Over TCP/IP (Local Area Connection - Properties - TCP/IP -
Properties - Advanced - WINS) on each computer.

Make sure the browser service is running on each computer. Control Panel -
Administrative Tools - Services. Verify that the Computer Browser, and the
TCP/IP NetBIOS Helper, services both show with Status = Started.

Power both computers off. Then power one on, and then the other. Check
"browstat status" again.

If no improvement, provide ipconfig information for each computer, and we'll do
some more diagnoses to tell us what to look at next.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, make sure that Format - Word Wrap is
NOT checked!, copy and paste entire contents into your next post. Identify
operating system (by name, version, and SP level) with each ipconfig listing.
Click to expand...
 
L

Linda Callard

Chuck said:
Linda,

Yes, it was very interesting.

You need to straighten out your network configuration on both computers.

Please start by un installing unnecessary components, from the list of
items
under Local Area Connection Properties. You only need the following items
in the list:
Client for Microsoft Networks
File and Printer Sharing For Microsoft Networks
QoS Packet Scheduler (optional)
Internet Protocol (TCP/IP)

Make sure you have both Client for Microsoft Networks, and File and
Printer
Sharing for Microsoft Networks (Local Area Connection - Properties), on
each computer. And have shares setup on each computer.

Enable NetBIOS Over TCP/IP (Local Area Connection - Properties - TCP/IP -
Properties - Advanced - WINS) on each computer.

Make sure the browser service is running on each computer. Control
Panel -
Administrative Tools - Services. Verify that the Computer Browser, and
the
TCP/IP NetBIOS Helper, services both show with Status = Started.

Power both computers off. Then power one on, and then the other. Check
"browstat status" again.

If no improvement, provide ipconfig information for each computer, and
we'll do
some more diagnoses to tell us what to look at next.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the
command
window - Open c:\ipconfig.txt in Notepad, make sure that Format - Word
Wrap is
NOT checked!, copy and paste entire contents into your next post. Identify
operating system (by name, version, and SP level) with each ipconfig
listing.
Click to expand...

Is "interesting" your euphemism for "all screwed up"? Did not want to
remove "Microsoft TCP/IP version 6" without your express direction. Please
advise. Did everything else. Same symptoms prevail. Here are updated data
for both computers (the netbios over tcpip has been enabled on both
computers - don't know why it reports as being disabled):

-------------------------------------

CCS-PC5 Laptop browstat

Status for domain CCS-NET on transport
\Device\NetBT_Tcpip_{CB6603F1-5ADC-4E37-8F44-C660B3F3ADE9}
Browsing is active on domain.
Master browser name is: CCS-PC5
Master browser is running build 2600
1 backup servers retrieved from master CCS-PC5
\\CCS-PC5
There are 2 servers in domain CCS-NET on transport
\Device\NetBT_Tcpip_{CB6603F1-5ADC-4E37-8F44-C660B3F3ADE9}
There are 1 domains in domain CCS-NET on transport
\Device\NetBT_Tcpip_{CB6603F1-5ADC-4E37-8F44-C660B3F3ADE9}

-------------------------------------

CCS-PC6 Desktop browstat

Status for domain CCS-NET on transport
\Device\NetBT_Tcpip_{D0369A81-275B-4968-BE6D-DACAB6F5DC83}
Browsing is active on domain.
Master browser name is: CCS-PC6
Master browser is running build 2600
1 backup servers retrieved from master CCS-PC6
\\CCS-PC6
There are 2 servers in domain CCS-NET on transport
\Device\NetBT_Tcpip_{D0369A81-275B-4968-BE6D-DACAB6F5DC83}
There are 1 domains in domain CCS-NET on transport
\Device\NetBT_Tcpip_{D0369A81-275B-4968-BE6D-DACAB6F5DC83}

-------------------------------------

CCS PC5 Laptop Windows IP Configuration

Host Name . . . . . . . . . . . . : CCS-PC5
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : CCS-NET

Ethernet adapter CCS-Net:

Connection-specific DNS Suffix . : CCS-NET
Description . . . . . . . . . . . : Intel(R) PRO/100+ MiniPCI
Physical Address. . . . . . . . . : 00-10-A4-0C-04-DA
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.185
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::210:a4ff:fe0c:4da%4
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : 22 November 2004 14:37:52
Lease Expires . . . . . . . . . . : 22 November 2004 15:37:52

PPP adapter PEI - Charlottetown:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 142.176.114.19
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 142.176.114.19
DNS Servers . . . . . . . . . . . : 142.176.17.8
142.176.17.9
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-FA-D0-71-4F-8D-EC
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter 6to4 Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6to4 Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 8E-B0-72-13
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 2002:8eb0:7213::8eb0:7213
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
2002:836b:213c::836b:213c
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : 8E-B0-72-13
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:142.176.114.19%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . : CCS-NET
Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : C0-A8-00-B9
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.185%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

-------------------------------------

CCS-PC6 Desktop Windows IP Configuration

Host Name . . . . . . . . . . . . : CCS-PC6
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : CCS-NET

Ethernet adapter CCS-NET:

Connection-specific DNS Suffix . : CCS-NET
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection #2
Physical Address. . . . . . . . . : 00-E0-18-5C-50-58
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.134
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::2e0:18ff:fe5c:5058%4
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : 22 November 2004 14:17:49
Lease Expires . . . . . . . . . . : 22 November 2004 15:17:49

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . : CCS-NET
Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : C0-A8-00-86
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.134%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

-------------------------------------
 
C

Chuck

Is "interesting" your euphemism for "all screwed up"? Did not want to
remove "Microsoft TCP/IP version 6" without your express direction. Please
advise. Did everything else. Same symptoms prevail. Here are updated data
for both computers (the netbios over tcpip has been enabled on both
computers - don't know why it reports as being disabled):
Click to expand...

<SNIP>

Linda,

Well, the IPConfig logs, and the browstat logs, look cleaner. And the IPConfig
logs don't report "NetBIOS over Tcpip. . . . . . . . : Disabled" for the IPV4
Ethernet connections. That's the good news.

The bad news, if you will look at the browstat logs, is that neither computer is
aware of the other, in terms of the master browser elections. Each computer
acknowledge the other's existence, in terms of being a server ("2 servers in
domain CCS-NET"). But both computers report themselves as the master browser,
which means minimally that the master browser election datagrams are being
blocked somewhere, and symmetrically.
<http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx>

What firewalls have you turned off? Many third party firewalls don't turn off
easily.

If it's not a firewall issue, and you have NBT enabled on both computers, the
next step is to remove Microsoft TCP/IP V6.

Also, turn off the browser on one computer. One master browser is fine for a
two computer domain - two browsers are necessary only for a domain with more
than two computers, and where the master browser is not guaranteed to be online
constantly. Restart both computers again, and rerun browstat whenever doing
this.
 
C

Chuck

Is "interesting" your euphemism for "all screwed up"? Did not want to
remove "Microsoft TCP/IP version 6" without your express direction. Please
advise. Did everything else. Same symptoms prevail. Here are updated data
for both computers (the netbios over tcpip has been enabled on both
computers - don't know why it reports as being disabled):
Click to expand...

<SNIP>

Linda,

Well, the IPConfig logs, and the browstat logs, look cleaner. And the IPConfig
logs don't report "NetBIOS over Tcpip. . . . . . . . : Disabled" for the IPV4
Ethernet connections. That's the good news.

The bad news, if you will look at the browstat logs, is that neither computer is
aware of the other, in terms of the master browser elections. Each computer
acknowledge the other's existence, in terms of being a server ("2 servers in
domain CCS-NET"). But both computers report themselves as the master browser,
which means minimally that the master browser election datagrams are being
blocked somewhere, and symmetrically.
<http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx>

What firewalls have you turned off? Many third party firewalls don't turn off
easily.

If it's not a firewall issue, and you have NBT enabled on both computers, the
next step is to remove Microsoft TCP/IP V6.

Also, turn off the browser on one computer. One master browser is fine for a
two computer domain - two browsers are necessary only for a domain with more
than two computers, and where the master browser is not guaranteed to be online
constantly. Restart both computers again, and rerun browstat whenever doing
this.
 
L

Linda Callard

Chuck said:
<SNIP>

Linda,

Well, the IPConfig logs, and the browstat logs, look cleaner. And the
IPConfig
logs don't report "NetBIOS over Tcpip. . . . . . . . : Disabled" for the
IPV4
Ethernet connections. That's the good news.

The bad news, if you will look at the browstat logs, is that neither
computer is
aware of the other, in terms of the master browser elections. Each
computer
acknowledge the other's existence, in terms of being a server ("2 servers
in
domain CCS-NET"). But both computers report themselves as the master
browser,
which means minimally that the master browser election datagrams are being
blocked somewhere, and symmetrically.
<http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx>

What firewalls have you turned off? Many third party firewalls don't turn
off
easily.

If it's not a firewall issue, and you have NBT enabled on both computers,
the
next step is to remove Microsoft TCP/IP V6.

Also, turn off the browser on one computer. One master browser is fine
for a
two computer domain - two browsers are necessary only for a domain with
more
than two computers, and where the master browser is not guaranteed to be
online
constantly. Restart both computers again, and rerun browstat whenever
doing
this.
Click to expand...

Thanks for all your help Chuck, but we have to take a break for a week or so
before we can return our attention to this exasperating challenge. We'll be
back online later.
 
C

Chuck

Thanks for all your help Chuck, but we have to take a break for a week or so
before we can return our attention to this exasperating challenge. We'll be
back online later.
Click to expand...

OK, Linda,

Thanks for the status update. Reply to this thread when you're back online.
 
L

Linda Callard

Chuck said:
OK, Linda,

Thanks for the status update. Reply to this thread when you're back
online.
Click to expand...

Problem solved. Unbeknownst to us, NSW/NAV was the culprit. Simple
registry edit solved everything. We're posting details in this newsgroup
under the title "Windows Networking Problem - One Possible Solution if NAV
Installed." Thanks, Chuck, for all your efforts.
 

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

network sharing problem 10
Sharing files in XP 2
XP home edition network problem 2
Printer Sharing on Mixed XP/Win 2000 Home Workgroup 2
XP can't see Vista Folder "Permission Error" 3
XP to XP Printer Sharing Problem 2
Networking problem: Please advise... 2
Home Network with Vista & XP 2

Top