XP Network Browse Problems

[SA]

I'll try to be succinct about an issue that recently
flaired with and XP SP2 box.

Sympoms:

Win2000 Server, and workstations combined with one Xp pro
client. Peer-to-Peer Network. The Network was working
just fine for aeons, (even after updating to SP2).

a.) If the Win2000 machines boot first, they can all see
each other across the network; including accessing shares
etc. When the Xp machine boots, it can't "see" the other
boxes in the network neighborhood, and when it trys to
access either the Workgroup, or "Computers Close To Me" ,
it receives the message "[Workgroup] is not accessible,
you might not have permission...The list of servers for
this workgroup is unavailable."

From any of the Win2K boxes the WinXp box shows in the
network neighborhood, but when trying to access it, it of
course "\\machine is not accessble."

I see Browser errors in the Event Viewer on the Xp box,
i.e. 8021, the "browser was unable to retrieve a list of
servers" and 8032 "The browser service has failed to
retrieve the backup list too many times."

When I run the utility Browstat with a status switch the
error is:

"Browsing is not active on the domain, Master name can not
be determined from GetAdapterStatus"

b.) If the WinXp box boots first, the exact reverse is
true, i.e. it can see the other boxes in its net
neighborhood, but can't access them and the Win2K machines
get the Workgroup is unavailable error.

Apparent Problem:

From these two scenarios, what appears to happen is that
if the Win2K machines (any of them, Server or Workstation)
boot first and are therefore the "master browser" then
everything is fine between all the 2K machines, however
the Xp machine doesn't communicate with the master browser
effectively.

Conversely if the WinXp machine boots first and it is the
initial "master browser" then it hoses the entire network
because it doesn't communicate its browse list.

Fix attempts:

Things that have been reviewed or tried:

a.) The browser, server, workstation and other services
are up and running; restarts don't impact things
b.) The Xp firewall is set to allow the file and print
sharing on the local subnet. I've disabled the Xp2
firewall and there's no change in behavior.
c.) I've used a scanner across the local net and the XP
machine does have port 137 and 139 open on the local subnet
d.) Can ping all the machines back and forth so its not a
cable or router problem
e.) The XP' boxes NetBios setting is set to use the defaut
setting under the WINS tab on the TCP/IP settings for the
adapter and changing it to "Enable NetBios over TCP/IP"
changes nothing, the problem still occurs.
f.) There's no VPN or set up.
g.) Uninstall XP SP2, and no change
h.) Uninstalled and reinstalled client for MS networks and
the file and print sharing services on the Xp box; no
change.

There's got to be some reg setting that's gotten hosed,
what I don't know.

Help!
Steve Arbaugh

 

[Michael Pardee]

You are using a domain? Which box is the domain server?

Do the boxes still ping OK? (I expect so.)

Finally, it ran fine even after SP2... any clue what
changes were made (obviously *something* changed, whether
you requested it or not).

Mike

-----Original Message-----
I'll try to be succinct about an issue that recently
flaired with and XP SP2 box.

Sympoms:

Win2000 Server, and workstations combined with one Xp pro
client. Peer-to-Peer Network. The Network was working
just fine for aeons, (even after updating to SP2).

a.) If the Win2000 machines boot first, they can all see
each other across the network; including accessing shares
etc. When the Xp machine boots, it can't "see" the other
boxes in the network neighborhood, and when it trys to
access either the Workgroup, or "Computers Close To Me" ,
it receives the message "[Workgroup] is not accessible,
you might not have permission...The list of servers for
this workgroup is unavailable."

From any of the Win2K boxes the WinXp box shows in the
network neighborhood, but when trying to access it, it of
course "\\machine is not accessble."

I see Browser errors in the Event Viewer on the Xp box,
i.e. 8021, the "browser was unable to retrieve a list of
servers" and 8032 "The browser service has failed to
retrieve the backup list too many times."

When I run the utility Browstat with a status switch the
error is:

"Browsing is not active on the domain, Master name can not
be determined from GetAdapterStatus"

b.) If the WinXp box boots first, the exact reverse is
true, i.e. it can see the other boxes in its net
neighborhood, but can't access them and the Win2K machines
get the Workgroup is unavailable error.

Apparent Problem:

From these two scenarios, what appears to happen is that
if the Win2K machines (any of them, Server or Workstation)
boot first and are therefore the "master browser" then
everything is fine between all the 2K machines, however
the Xp machine doesn't communicate with the master browser
effectively.

Conversely if the WinXp machine boots first and it is the
initial "master browser" then it hoses the entire network
because it doesn't communicate its browse list.

Fix attempts:

Things that have been reviewed or tried:

a.) The browser, server, workstation and other services
are up and running; restarts don't impact things
b.) The Xp firewall is set to allow the file and print
sharing on the local subnet. I've disabled the Xp2
firewall and there's no change in behavior.
c.) I've used a scanner across the local net and the XP
machine does have port 137 and 139 open on the local subnet
d.) Can ping all the machines back and forth so its not a
cable or router problem
e.) The XP' boxes NetBios setting is set to use the defaut
setting under the WINS tab on the TCP/IP settings for the
adapter and changing it to "Enable NetBios over TCP/IP"
changes nothing, the problem still occurs.
f.) There's no VPN or set up.
g.) Uninstall XP SP2, and no change
h.) Uninstalled and reinstalled client for MS networks and
the file and print sharing services on the Xp box; no
change.

There's got to be some reg setting that's gotten hosed,
what I don't know.

Help!
Steve Arbaugh

.

 

[Chuck]

I'll try to be succinct about an issue that recently
flaired with and XP SP2 box.

Sympoms:

Win2000 Server, and workstations combined with one Xp pro
client. Peer-to-Peer Network. The Network was working
just fine for aeons, (even after updating to SP2).

a.) If the Win2000 machines boot first, they can all see
each other across the network; including accessing shares
etc. When the Xp machine boots, it can't "see" the other
boxes in the network neighborhood, and when it trys to
access either the Workgroup, or "Computers Close To Me" ,
it receives the message "[Workgroup] is not accessible,
you might not have permission...The list of servers for
this workgroup is unavailable."

From any of the Win2K boxes the WinXp box shows in the
network neighborhood, but when trying to access it, it of
course "\\machine is not accessble."

I see Browser errors in the Event Viewer on the Xp box,
i.e. 8021, the "browser was unable to retrieve a list of
servers" and 8032 "The browser service has failed to
retrieve the backup list too many times."

When I run the utility Browstat with a status switch the
error is:

"Browsing is not active on the domain, Master name can not
be determined from GetAdapterStatus"

b.) If the WinXp box boots first, the exact reverse is
true, i.e. it can see the other boxes in its net
neighborhood, but can't access them and the Win2K machines
get the Workgroup is unavailable error.

Apparent Problem:

From these two scenarios, what appears to happen is that
if the Win2K machines (any of them, Server or Workstation)
boot first and are therefore the "master browser" then
everything is fine between all the 2K machines, however
the Xp machine doesn't communicate with the master browser
effectively.

Conversely if the WinXp machine boots first and it is the
initial "master browser" then it hoses the entire network
because it doesn't communicate its browse list.

Fix attempts:

Things that have been reviewed or tried:

a.) The browser, server, workstation and other services
are up and running; restarts don't impact things
b.) The Xp firewall is set to allow the file and print
sharing on the local subnet. I've disabled the Xp2
firewall and there's no change in behavior.
c.) I've used a scanner across the local net and the XP
machine does have port 137 and 139 open on the local subnet
d.) Can ping all the machines back and forth so its not a
cable or router problem
e.) The XP' boxes NetBios setting is set to use the defaut
setting under the WINS tab on the TCP/IP settings for the
adapter and changing it to "Enable NetBios over TCP/IP"
changes nothing, the problem still occurs.
f.) There's no VPN or set up.
g.) Uninstall XP SP2, and no change
h.) Uninstalled and reinstalled client for MS networks and
the file and print sharing services on the Xp box; no
change.

There's got to be some reg setting that's gotten hosed,
what I don't know.

Help!
Steve Arbaugh

Steve,

You checked the Browser service on each computer? How about the TCP/IP NetBIOS
Helper service?

Which computer did you run browstat on? How about running it four times - on
the Win2K and WinXP computers, both after booting the Win2K computer first, and
the WinXP computer first?

When you say "boot first", do you actually shut ALL computers down
simultaneously, then bring specified ones up first, giving time to conduct the
master browser election?

<http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx>

Do you have authentication setup properly between all computers? Check again
please.

On the XP Pro computer, check to see if Simple File Sharing (Control Panel -
Folder Options - View - Advanced settings) is enabled or disabled. With XP Pro,
you need to have SFS properly set.

With XP Pro, if SFS is disabled, check the Local Security Policy (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".

With XP Pro, if you set the above Local Security Policy to "Guest only", enable
the Guest account, using Local User Manager (Start - Run - "lusrmgr.msc"). 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.

For XP Pro with Simple File Sharing enabled, make sure that the Guest account is
enabled, on each computer, using Local User Manager (Start - Run -
"lusrmgr.msc").

Can you list shares between each computer? Run both "net view \\Win2KComputer"
and "new view \\XPProComputer" from the XP computer, then from the same Win2K
computer.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[SA]

Mike:

No, no domain, this is peer to peer (i.e. a workgroup).
Yes the boxes ping OK
The only change was a windows update for .Net 1.1; after
that nothing really changed.

I had been on a public network and set the SP2 Firewall to
not allow exceptions and then switched back after going on
a private network.

Somehow it seems that part of the "firewall" may still be
applied.

SA

-----Original Message-----
You are using a domain? Which box is the domain server?

Do the boxes still ping OK? (I expect so.)

Finally, it ran fine even after SP2... any clue what
changes were made (obviously *something* changed, whether
you requested it or not).

Mike

-----Original Message-----
I'll try to be succinct about an issue that recently
flaired with and XP SP2 box.

Sympoms:

Win2000 Server, and workstations combined with one Xp pro
client. Peer-to-Peer Network. The Network was working
just fine for aeons, (even after updating to SP2).

a.) If the Win2000 machines boot first, they can all see
each other across the network; including accessing shares
etc. When the Xp machine boots, it can't "see" the other
boxes in the network neighborhood, and when it trys to
access either the Workgroup, or "Computers Close To Me" ,
it receives the message "[Workgroup] is not accessible,
you might not have permission...The list of servers for
this workgroup is unavailable."

From any of the Win2K boxes the WinXp box shows in the
network neighborhood, but when trying to access it, it of
course "\\machine is not accessble."

I see Browser errors in the Event Viewer on the Xp box,
i.e. 8021, the "browser was unable to retrieve a list of
servers" and 8032 "The browser service has failed to
retrieve the backup list too many times."

When I run the utility Browstat with a status switch the
error is:

"Browsing is not active on the domain, Master name can not
be determined from GetAdapterStatus"

b.) If the WinXp box boots first, the exact reverse is
true, i.e. it can see the other boxes in its net
neighborhood, but can't access them and the Win2K machines
get the Workgroup is unavailable error.

Apparent Problem:

From these two scenarios, what appears to happen is that
if the Win2K machines (any of them, Server or Workstation)
boot first and are therefore the "master browser" then
everything is fine between all the 2K machines, however
the Xp machine doesn't communicate with the master browser
effectively.

Conversely if the WinXp machine boots first and it is the
initial "master browser" then it hoses the entire network
because it doesn't communicate its browse list.

Fix attempts:

Things that have been reviewed or tried:

a.) The browser, server, workstation and other services
are up and running; restarts don't impact things
b.) The Xp firewall is set to allow the file and print
sharing on the local subnet. I've disabled the Xp2
firewall and there's no change in behavior.
c.) I've used a scanner across the local net and the XP
machine does have port 137 and 139 open on the local subnet
d.) Can ping all the machines back and forth so its not a
cable or router problem
e.) The XP' boxes NetBios setting is set to use the defaut
setting under the WINS tab on the TCP/IP settings for the
adapter and changing it to "Enable NetBios over TCP/IP"
changes nothing, the problem still occurs.
f.) There's no VPN or set up.
g.) Uninstall XP SP2, and no change
h.) Uninstalled and reinstalled client for MS networks and
the file and print sharing services on the Xp box; no
change.

There's got to be some reg setting that's gotten hosed,
what I don't know.

Help!
Steve Arbaugh

.

.

 

[SA]

Heck, I've even gone back and repaired the original XP
install and still hosed.

Nothing seems to work.

SA

-----Original Message-----
You are using a domain? Which box is the domain server?

Do the boxes still ping OK? (I expect so.)

Finally, it ran fine even after SP2... any clue what
changes were made (obviously *something* changed, whether
you requested it or not).

Mike

-----Original Message-----
I'll try to be succinct about an issue that recently
flaired with and XP SP2 box.

Sympoms:

Win2000 Server, and workstations combined with one Xp pro
client. Peer-to-Peer Network. The Network was working
just fine for aeons, (even after updating to SP2).

a.) If the Win2000 machines boot first, they can all see
each other across the network; including accessing shares
etc. When the Xp machine boots, it can't "see" the other
boxes in the network neighborhood, and when it trys to
access either the Workgroup, or "Computers Close To Me" ,
it receives the message "[Workgroup] is not accessible,
you might not have permission...The list of servers for
this workgroup is unavailable."

From any of the Win2K boxes the WinXp box shows in the
network neighborhood, but when trying to access it, it of
course "\\machine is not accessble."

I see Browser errors in the Event Viewer on the Xp box,
i.e. 8021, the "browser was unable to retrieve a list of
servers" and 8032 "The browser service has failed to
retrieve the backup list too many times."

When I run the utility Browstat with a status switch the
error is:

"Browsing is not active on the domain, Master name can not
be determined from GetAdapterStatus"

b.) If the WinXp box boots first, the exact reverse is
true, i.e. it can see the other boxes in its net
neighborhood, but can't access them and the Win2K machines
get the Workgroup is unavailable error.

Apparent Problem:

From these two scenarios, what appears to happen is that
if the Win2K machines (any of them, Server or Workstation)
boot first and are therefore the "master browser" then
everything is fine between all the 2K machines, however
the Xp machine doesn't communicate with the master browser
effectively.

Conversely if the WinXp machine boots first and it is the
initial "master browser" then it hoses the entire network
because it doesn't communicate its browse list.

Fix attempts:

Things that have been reviewed or tried:

a.) The browser, server, workstation and other services
are up and running; restarts don't impact things
b.) The Xp firewall is set to allow the file and print
sharing on the local subnet. I've disabled the Xp2
firewall and there's no change in behavior.
c.) I've used a scanner across the local net and the XP
machine does have port 137 and 139 open on the local subnet
d.) Can ping all the machines back and forth so its not a
cable or router problem
e.) The XP' boxes NetBios setting is set to use the defaut
setting under the WINS tab on the TCP/IP settings for the
adapter and changing it to "Enable NetBios over TCP/IP"
changes nothing, the problem still occurs.
f.) There's no VPN or set up.
g.) Uninstall XP SP2, and no change
h.) Uninstalled and reinstalled client for MS networks and
the file and print sharing services on the Xp box; no
change.

There's got to be some reg setting that's gotten hosed,
what I don't know.

Help!
Steve Arbaugh

.

.

 

[SA]

Chuck:

Thanks for all the check points. Here's the response:

1.) Browser service is running on all machines.
2.) Browstat: running it on all machines really doesn't
make a difference. On the non-Xp box, everthing is fine,
provided that any one of those machines is the first to
boot on the network, so that it becomes the browse master
before the XP box.
3.) Yes, that's what I mean. If any of the win2K boxes
boots first (from all being shut down,) they run fine, but
the XP box after it boots, can't pick up the browse list
from any of the Win2K boxes, so its hosed. If the XP box
is booted first, none of the Win2K boxes can pick up its
browse list and it defines itself as the master browser so
the whole net is hosed although the XP box then shows the
Win2K boxes in its list of computers, but you still can't
access the shares.
4.) Yes, authentication is set up correctly.
5.) SFS is disabled on the XP box
6.) Classic security model is set
7.) net view fails on XP box if it boots after the Win2k
boxes. Visa versa on the Win2K boxes if Xp box boots
first.

This is a PITA.

Steve Arbaugh

 

[Chuck]

Chuck:

Thanks for all the check points. Here's the response:

1.) Browser service is running on all machines.
2.) Browstat: running it on all machines really doesn't
make a difference. On the non-Xp box, everthing is fine,
provided that any one of those machines is the first to
boot on the network, so that it becomes the browse master
before the XP box.
3.) Yes, that's what I mean. If any of the win2K boxes
boots first (from all being shut down,) they run fine, but
the XP box after it boots, can't pick up the browse list
from any of the Win2K boxes, so its hosed. If the XP box
is booted first, none of the Win2K boxes can pick up its
browse list and it defines itself as the master browser so
the whole net is hosed although the XP box then shows the
Win2K boxes in its list of computers, but you still can't
access the shares.
4.) Yes, authentication is set up correctly.
5.) SFS is disabled on the XP box
6.) Classic security model is set
7.) net view fails on XP box if it boots after the Win2k
boxes. Visa versa on the Win2K boxes if Xp box boots
first.

This is a PITA.

Steve Arbaugh

Steve,

Let's start from the beginning.

Provide ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.
Identify operating system (by name and version) with each ipconfig listing.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[SA]

Chuck:

Thanks for your multiple responses. Not to sound
trenchant, but ip configs will show nothing unusual. All
the machines are on the proper subnets.

Steve Arbaugh

 

[SA]

OK: Got it solved. Here was the resolution.

I'd noted that this was a peer-to-peer network on the XP
machine. This was based on the IP config node type
designation on that box. The Win2K boxes were all hybrid
node types.

Looking at KB 167640

I went on the XP box and changed the default node type to
hyrid as well by tweaking the registry (Note the article
doesn't indicate the it is targeted toward XP but it does
impact that OS). And setting the default NetBt node type
on the Xp box to hybrid as well, and Voila it works again.

Damn don't know how that ever changed.

Steve Arbaugh

-----Original Message-----
You are using a domain? Which box is the domain server?

Do the boxes still ping OK? (I expect so.)

Finally, it ran fine even after SP2... any clue what
changes were made (obviously *something* changed, whether
you requested it or not).

Mike

-----Original Message-----
I'll try to be succinct about an issue that recently
flaired with and XP SP2 box.

Sympoms:

Win2000 Server, and workstations combined with one Xp pro
client. Peer-to-Peer Network. The Network was working
just fine for aeons, (even after updating to SP2).

a.) If the Win2000 machines boot first, they can all see
each other across the network; including accessing shares
etc. When the Xp machine boots, it can't "see" the other
boxes in the network neighborhood, and when it trys to
access either the Workgroup, or "Computers Close To Me" ,
it receives the message "[Workgroup] is not accessible,
you might not have permission...The list of servers for
this workgroup is unavailable."

From any of the Win2K boxes the WinXp box shows in the
network neighborhood, but when trying to access it, it of
course "\\machine is not accessble."

I see Browser errors in the Event Viewer on the Xp box,
i.e. 8021, the "browser was unable to retrieve a list of
servers" and 8032 "The browser service has failed to
retrieve the backup list too many times."

When I run the utility Browstat with a status switch the
error is:

"Browsing is not active on the domain, Master name can not
be determined from GetAdapterStatus"

b.) If the WinXp box boots first, the exact reverse is
true, i.e. it can see the other boxes in its net
neighborhood, but can't access them and the Win2K machines
get the Workgroup is unavailable error.

Apparent Problem:

From these two scenarios, what appears to happen is that
if the Win2K machines (any of them, Server or Workstation)
boot first and are therefore the "master browser" then
everything is fine between all the 2K machines, however
the Xp machine doesn't communicate with the master browser
effectively.

Conversely if the WinXp machine boots first and it is the
initial "master browser" then it hoses the entire network
because it doesn't communicate its browse list.

Fix attempts:

Things that have been reviewed or tried:

a.) The browser, server, workstation and other services
are up and running; restarts don't impact things
b.) The Xp firewall is set to allow the file and print
sharing on the local subnet. I've disabled the Xp2
firewall and there's no change in behavior.
c.) I've used a scanner across the local net and the XP
machine does have port 137 and 139 open on the local subnet
d.) Can ping all the machines back and forth so its not a
cable or router problem
e.) The XP' boxes NetBios setting is set to use the defaut
setting under the WINS tab on the TCP/IP settings for the
adapter and changing it to "Enable NetBios over TCP/IP"
changes nothing, the problem still occurs.
f.) There's no VPN or set up.
g.) Uninstall XP SP2, and no change
h.) Uninstalled and reinstalled client for MS networks and
the file and print sharing services on the Xp box; no
change.

There's got to be some reg setting that's gotten hosed,
what I don't know.

Help!
Steve Arbaugh

.

.

 

[SA]

OK: Got it solved. Here was the resolution.

I'd noted that this was a peer-to-peer network on the XP
machine. This was based on the IP config node type
designation on that box. The Win2K boxes were all hybrid
node types.

Looking at KB 167640

I went on the XP box and changed the default node type to
hyrid as well by tweaking the registry (Note the article
doesn't indicate the it is targeted toward XP but it does
impact that OS). And setting the default NetBt node type
on the Xp box to hybrid as well, and Voila it works again.

Damn don't know how that ever changed.

Steve Arbaugh

 

[Quaoar]

Mike:

No, no domain, this is peer to peer (i.e. a workgroup).
Yes the boxes ping OK
The only change was a windows update for .Net 1.1; after
that nothing really changed.

I had been on a public network and set the SP2 Firewall to
not allow exceptions and then switched back after going on
a private network.

Somehow it seems that part of the "firewall" may still be
applied.

SA

-----Original Message-----
You are using a domain? Which box is the domain server?

Do the boxes still ping OK? (I expect so.)

Finally, it ran fine even after SP2... any clue what
changes were made (obviously *something* changed, whether
you requested it or not).

Mike

-----Original Message-----
I'll try to be succinct about an issue that recently
flaired with and XP SP2 box.

Sympoms:

Win2000 Server, and workstations combined with one Xp pro
client. Peer-to-Peer Network. The Network was working
just fine for aeons, (even after updating to SP2).

a.) If the Win2000 machines boot first, they can all see
each other across the network; including accessing shares
etc. When the Xp machine boots, it can't "see" the other
boxes in the network neighborhood, and when it trys to
access either the Workgroup, or "Computers Close To Me" ,
it receives the message "[Workgroup] is not accessible,
you might not have permission...The list of servers for
this workgroup is unavailable."

From any of the Win2K boxes the WinXp box shows in the
network neighborhood, but when trying to access it, it of
course "\\machine is not accessble."

I see Browser errors in the Event Viewer on the Xp box,
i.e. 8021, the "browser was unable to retrieve a list of
servers" and 8032 "The browser service has failed to
retrieve the backup list too many times."

When I run the utility Browstat with a status switch the
error is:

"Browsing is not active on the domain, Master name can not
be determined from GetAdapterStatus"

b.) If the WinXp box boots first, the exact reverse is
true, i.e. it can see the other boxes in its net
neighborhood, but can't access them and the Win2K machines
get the Workgroup is unavailable error.

Apparent Problem:

From these two scenarios, what appears to happen is that
if the Win2K machines (any of them, Server or Workstation)
boot first and are therefore the "master browser" then
everything is fine between all the 2K machines, however
the Xp machine doesn't communicate with the master browser
effectively.

Conversely if the WinXp machine boots first and it is the
initial "master browser" then it hoses the entire network
because it doesn't communicate its browse list.

Fix attempts:

Things that have been reviewed or tried:

a.) The browser, server, workstation and other services
are up and running; restarts don't impact things
b.) The Xp firewall is set to allow the file and print
sharing on the local subnet. I've disabled the Xp2
firewall and there's no change in behavior.
c.) I've used a scanner across the local net and the XP
machine does have port 137 and 139 open on the local subnet
d.) Can ping all the machines back and forth so its not a
cable or router problem
e.) The XP' boxes NetBios setting is set to use the defaut
setting under the WINS tab on the TCP/IP settings for the
adapter and changing it to "Enable NetBios over TCP/IP"
changes nothing, the problem still occurs.
f.) There's no VPN or set up.
g.) Uninstall XP SP2, and no change
h.) Uninstalled and reinstalled client for MS networks and
the file and print sharing services on the Xp box; no
change.

There's got to be some reg setting that's gotten hosed,
what I don't know.

Help!
Steve Arbaugh

.

.

The firewall locks down the connection on the SP2 TCP/IP filtering as it
goes away if the third-party firewall is not recognized automatically.
Select the connection properties, General tab, Advanced Props, Options
tab, TCP/IP filtering props, select Enabled, change Permit Only to
Permit All.
Q