S
Steve Moss
Yes, I understand this is a frequently asked question and yes, I have
read the related threads here (and on various other places on the
'net), unfortunately without a resolution.
Here's my situation:
- A small (three machines) workgroup on a single class C subnet, all
PCs running Windows XP Pro with SP2, with one acting as an internet
gateway.
- Gateway machine has two NICs: one to a cable modem, the other to the
LAN. Firewall protects boundary, but does not filter or block traffic
on the internal LAN NIC.
- Each machine has a fixed IP and can ping all others, both by IP
address and computer name.
- Explicit UNC paths to known shared resources works OK on all machines
- On each machine, "net view \\computername" command works OK for all
computernames, but "net view" command (i.e., to browse workgroup) fails
with error 6118.
- Attempts to browse workgroup in Network Neighbourhood fail on all
machines.
Now, this is a browsing issue, as the "browstat status" command
indicates that browsing is NOT active on the domain (sic).
On each machine, the MaintainServerList registry value is set to "Auto"
and the IsDomainMaster value to "FALSE".
The Computer Browser service is set to 'automatic' on all machines, but
whenever one of them is started manually, it eventually times out and
closes. The Event Viewer shows an error with event id 7023, stating:
"The Computer Browser service terminated with the following error:
This operation returned because the timeout period expired."
This is causing problems for some applications, which need to browse
the workgroup. Does anyone have any idea of how to solve this?
Some more info ... I have VMWare on one of the nachines, and if I start
a Win2K guest OS in VMWare then the guest OS - AND ALL WinXP MACHINES
ON THE NETWORK - can successfully browse the workgroup(!), and the
Computer Browser service on the Win2K virtual machine successfully
elects as the master browser (as illustrated by a "browstat status"
command on any of the machines). So for some reason, the Computer
Browser service on all of the WinXP machines fails to elect itself as
master.
I have also tried setting the MaintainServerList registry value to
"Yes" and the IsDomainMaster value to "TRUE" on each of the WinXP
machines in turn, again without success.
read the related threads here (and on various other places on the
'net), unfortunately without a resolution.
Here's my situation:
- A small (three machines) workgroup on a single class C subnet, all
PCs running Windows XP Pro with SP2, with one acting as an internet
gateway.
- Gateway machine has two NICs: one to a cable modem, the other to the
LAN. Firewall protects boundary, but does not filter or block traffic
on the internal LAN NIC.
- Each machine has a fixed IP and can ping all others, both by IP
address and computer name.
- Explicit UNC paths to known shared resources works OK on all machines
- On each machine, "net view \\computername" command works OK for all
computernames, but "net view" command (i.e., to browse workgroup) fails
with error 6118.
- Attempts to browse workgroup in Network Neighbourhood fail on all
machines.
Now, this is a browsing issue, as the "browstat status" command
indicates that browsing is NOT active on the domain (sic).
On each machine, the MaintainServerList registry value is set to "Auto"
and the IsDomainMaster value to "FALSE".
The Computer Browser service is set to 'automatic' on all machines, but
whenever one of them is started manually, it eventually times out and
closes. The Event Viewer shows an error with event id 7023, stating:
"The Computer Browser service terminated with the following error:
This operation returned because the timeout period expired."
This is causing problems for some applications, which need to browse
the workgroup. Does anyone have any idea of how to solve this?
Some more info ... I have VMWare on one of the nachines, and if I start
a Win2K guest OS in VMWare then the guest OS - AND ALL WinXP MACHINES
ON THE NETWORK - can successfully browse the workgroup(!), and the
Computer Browser service on the Win2K virtual machine successfully
elects as the master browser (as illustrated by a "browstat status"
command on any of the machines). So for some reason, the Computer
Browser service on all of the WinXP machines fails to elect itself as
master.
I have also tried setting the MaintainServerList registry value to
"Yes" and the IsDomainMaster value to "TRUE" on each of the WinXP
machines in turn, again without success.