Computer accessible but can't be seen on XP workgroup

Hi:

I have 4 computers on workgroup. All of them are running XP SP2. One
computer we are using as file server. All of us can access the data from the
file server (runing XP SP2), however, we can't see it through "See workgroup
computers". I have same password on all computers with Admin rights. I can
see other three computers but no the file server. Also, when on the server I
tried to click the "See workgroup computers" it says "WorkGroup is not
accessible. You might not have the permission to use this network resources.
Contact admin.... List of servers for this workgroup is not currently
available." Obtain IP / DNS checked automatically. Under advance tab, Net
Bios or TCP/IP enable. Enable LMHOSTS lookup enable.
DHCP enabled.

File and printer sharing for MS Networked checked.

They all on the same workgroup no domain etc. No Windows 2003 or 2000 server
installed.

Thanks

Hi
Hi
Check the Firewalls to make sure that they allow freeLAN traffic.
Windows XP File Sharing -
http://support.microsoft.com/default...b;en-us;304040
Printer Sharing XP -
http://www.microsoft.com/windowsxp/u...utt_july2.mspx
Windows Native Firewall setting for Sharing XP -
http://support.microsoft.com/kb/875357
Jack (MS, MVP-Networking)

"JD" <cgapa1@gmail.com> wrote in message
news:14B6FF97-5F21-425C-9534-9C66C11EE639@microsoft.com...
> Hi:
>
> I have 4 computers on workgroup. All of them are running XP SP2. One
> computer we are using as file server. All of us can access the data from
> the
> file server (runing XP SP2), however, we can't see it through "See
> workgroup
> computers". I have same password on all computers with Admin rights. I can
> see other three computers but no the file server. Also, when on the server
> I
> tried to click the "See workgroup computers" it says "WorkGroup is not
> accessible. You might not have the permission to use this network
> resources.
> Contact admin.... List of servers for this workgroup is not currently
> available." Obtain IP / DNS checked automatically. Under advance tab, Net
> Bios or TCP/IP enable. Enable LMHOSTS lookup enable.
> DHCP enabled.
>
> File and printer sharing for MS Networked checked.
>
> They all on the same workgroup no domain etc. No Windows 2003 or 2000
> server
> installed.
>
> Thanks

Thanks for your reply. I checked everything is fine. I also turned off the
firewall and antivirus program on the fileserver (running xp sp2 in
workgroup). . All the settings on the server is same as other PCs. I can see
other PCs but not the fileserver (running xp sp2 in workgroup). As I said, I
can ping it and also access it by the name but can't see in workgroup
computers. Since I can't see that is why I beleive when I access any file
first time it takes more time than normal. I guess workstation look for that
computer, but once I open up the file from the server rest does not take long
time, I mean read and write to that file.

One more strange thing is on the fileserver itself I can't open up the "See
WorkGroup Computers" option. It gives message that I don't have administrator
rights. Eventhoug I logedin as admin.

Thanks

"Jack (MVP-Networking)." wrote:

> Hi
> Hi
> Check the Firewalls to make sure that they allow freeLAN traffic.
> Windows XP File Sharing -
> http://support.microsoft.com/default...b;en-us;304040
> Printer Sharing XP -
> http://www.microsoft.com/windowsxp/u...utt_july2.mspx
> Windows Native Firewall setting for Sharing XP -
> http://support.microsoft.com/kb/875357
> Jack (MS, MVP-Networking)
>
> "JD" <cgapa1@gmail.com> wrote in message
> news:14B6FF97-5F21-425C-9534-9C66C11EE639@microsoft.com...
> > Hi:
> >
> > I have 4 computers on workgroup. All of them are running XP SP2. One
> > computer we are using as file server. All of us can access the data from
> > the
> > file server (runing XP SP2), however, we can't see it through "See
> > workgroup
> > computers". I have same password on all computers with Admin rights. I can
> > see other three computers but no the file server. Also, when on the server
> > I
> > tried to click the "See workgroup computers" it says "WorkGroup is not
> > accessible. You might not have the permission to use this network
> > resources.
> > Contact admin.... List of servers for this workgroup is not currently
> > available." Obtain IP / DNS checked automatically. Under advance tab, Net
> > Bios or TCP/IP enable. Enable LMHOSTS lookup enable.
> > DHCP enabled.
> >
> > File and printer sharing for MS Networked checked.
> >
> > They all on the same workgroup no domain etc. No Windows 2003 or 2000
> > server
> > installed.
> >
> > Thanks
>
>

=?Utf-8?B?SkQ=?= <cgapa1@gmail.com> wrote in
news:14B6FF97-5F21-425C-9534-9C66C11EE639@microsoft.com:

> Hi:
>
> I have 4 computers on workgroup. All of them are running XP SP2.
> One computer we are using as file server. All of us can access the
> data from the file server (runing XP SP2), however, we can't see
> it through "See workgroup computers". I have same password on all
> computers with Admin rights. I can see other three computers but
> no the file server. Also, when on the server I tried to click the
> "See workgroup computers" it says "WorkGroup is not accessible.
> You might not have the permission to use this network resources.
> Contact admin.... List of servers for this workgroup is not
> currently available." Obtain IP / DNS checked automatically.
> Under advance tab, Net Bios or TCP/IP enable. Enable LMHOSTS
> lookup enable. DHCP enabled.
>
> File and printer sharing for MS Networked checked.
>
> They all on the same workgroup no domain etc. No Windows 2003 or
> 2000 server installed.
>
> Thanks

** List of servers for this workgroup is not currently available. **

The above error usually indicates a Master Browser problem. The most
common cause of this is having even one computer on the subnet with a
firewall not set up to recognize Windows Networking. Browstat.exe is a
tool to help troubleshoot this problem but this program is not standard
Windows-issue. Pick a computer, bring up a command prompt, and type
the following command for each computer on your network (including the
same computer):

nbtstat -a computername

Note that the computer name should not be prefaced with the '\\'
characters and the -a is a lower-case 'a'. The result should be that
exactly one of your machines should reply with a line containing:
..__MSBROWSE__.
If this is not the case, there is a master browser problem.

-- John

I am having this same issue. I cannot see one of the computers, either by XP
View Workgroup Computers, or Vista Network. So, I typed 'nbtstat -a
clifpress' and got this response from the computer which could not be seen (I
am running the command from my Vista laptop which is connected via wireless):

C:\Users\Dad>nbtstat -a clifpress

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

Host not found.

Bluetooth Network Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

Host not found.

Wireless Network Connection:
Node IpAddress: [192.168.15.103] Scope Id: []

NetBIOS Remote Machine Name Table

Name Type Status
---------------------------------------------
CLIFPRESS <00> UNIQUE Registered
HOME <00> GROUP Registered
CLIFPRESS <20> UNIQUE Registered
HOME <1E> GROUP Registered
HOME <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered

MAC Address = 00-04-5A-85-85-50

Because the line '..__MSBROWSE__' is in the response, that means this
computer is ok?

Then I did the same for another computer on the network and got:

C:\Users\Dad>nbtstat -a bob

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

Host not found.

Bluetooth Network Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

Host not found.

Then I went back to Vista Network and now I can see CLIFPRESS! Also, when I
type the command for BOB again, now I get:

C:\Users\Dad>nbtstat -a bob

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

Host not found.

Bluetooth Network Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

Host not found.

Wireless Network Connection:
Node IpAddress: [192.168.15.103] Scope Id: []

NetBIOS Remote Machine Name Table

Name Type Status
---------------------------------------------
BOB <00> UNIQUE Registered
HOME <00> GROUP Registered
BOB <20> UNIQUE Registered
HOME <1E> GROUP Registered

What does all this mean???




"John Wunderlich" wrote:

> =?Utf-8?B?SkQ=?= <cgapa1@gmail.com> wrote in
> news:14B6FF97-5F21-425C-9534-9C66C11EE639@microsoft.com:
>
> > Hi:
> >
> > I have 4 computers on workgroup. All of them are running XP SP2.
> > One computer we are using as file server. All of us can access the
> > data from the file server (runing XP SP2), however, we can't see
> > it through "See workgroup computers". I have same password on all
> > computers with Admin rights. I can see other three computers but
> > no the file server. Also, when on the server I tried to click the
> > "See workgroup computers" it says "WorkGroup is not accessible.
> > You might not have the permission to use this network resources.
> > Contact admin.... List of servers for this workgroup is not
> > currently available." Obtain IP / DNS checked automatically.
> > Under advance tab, Net Bios or TCP/IP enable. Enable LMHOSTS
> > lookup enable. DHCP enabled.
> >
> > File and printer sharing for MS Networked checked.
> >
> > They all on the same workgroup no domain etc. No Windows 2003 or
> > 2000 server installed.
> >
> > Thanks
>
> ** List of servers for this workgroup is not currently available. **
>
> The above error usually indicates a Master Browser problem. The most
> common cause of this is having even one computer on the subnet with a
> firewall not set up to recognize Windows Networking. Browstat.exe is a
> tool to help troubleshoot this problem but this program is not standard
> Windows-issue. Pick a computer, bring up a command prompt, and type
> the following command for each computer on your network (including the
> same computer):
>
> nbtstat -a computername
>
> Note that the computer name should not be prefaced with the '\\'
> characters and the -a is a lower-case 'a'. The result should be that
> exactly one of your machines should reply with a line containing:
> ..__MSBROWSE__.
> If this is not the case, there is a master browser problem.
>
> -- John
>
>

=?Utf-8?B?RkNsaWZ0b24=?= <FClifton@discussions.microsoft.com> wrote
in news:809341BC-68F9-499A-B501-2F86CA3982A3@microsoft.com:

> I am having this same issue. I cannot see one of the computers,
> either by XP View Workgroup Computers, or Vista Network. So, I
> typed 'nbtstat -a clifpress' and got this response from the
> computer which could not be seen (I am running the command from my
> Vista laptop which is connected via wireless):
>
> C:\Users\Dad>nbtstat -a clifpress
[...]
> ..__MSBROWSE__.<01> GROUP Registered
[...]
> Because the line '..__MSBROWSE__' is in the response, that means
> this computer is ok?

It means that the computer thinks that it is the Master Browser

> Then I did the same for another computer on the network and got:
>
> C:\Users\Dad>nbtstat -a bob
>
[...]
> Then I went back to Vista Network and now I can see CLIFPRESS!
> Also, when I type the command for BOB again, now I get:
>
> C:\Users\Dad>nbtstat -a bob
>
> Local Area Connection:
> Node IpAddress: [0.0.0.0] Scope Id: []
>
> Host not found.
>
> Bluetooth Network Connection:
> Node IpAddress: [0.0.0.0] Scope Id: []
>
> Host not found.
>
> Wireless Network Connection:
> Node IpAddress: [192.168.15.103] Scope Id: []
>
> NetBIOS Remote Machine Name Table
>
> Name Type Status
> ---------------------------------------------
> BOB <00> UNIQUE Registered
> HOME <00> GROUP Registered
> BOB <20> UNIQUE Registered
> HOME <1E> GROUP Registered
>
> What does all this mean???

"View Network Computers" simply asks the computer who is the browse
master to send the list of computers that it thinks is on the network.
It can take a while for a computer to show up with the browse master.

"nbtstat -a <computer>" broadcasts a message directly to that computer
to send back its status.

One misconfigured firewall on just one computer on the subnet can cause
the Master Browser function to fail. First try disabling firewalls on
all machines and see if it helps out.

HTH,
John

Thanks for the help! I turned off all the computers but my laptop and the
server. I can now see the server. I think it might be my son's machine
causing the problem. It is an HP Desktop running Vista, using the Windows
firewall. Do you have some suggestions as to how the firewall should be
setup? Is there a wizard that can be run?

Frank

"John Wunderlich" wrote:

>
> One misconfigured firewall on just one computer on the subnet can cause
> the Master Browser function to fail. First try disabling firewalls on
> all machines and see if it helps out.
>
> HTH,
> John
>
>

=?Utf-8?B?RkNsaWZ0b24=?= <FClifton@discussions.microsoft.com> wrote
in news:0A010499-7EA8-446D-ABC6-10589B487DE1@microsoft.com:

>
> "John Wunderlich" wrote:
>
>>
>> One misconfigured firewall on just one computer on the subnet can
>> cause the Master Browser function to fail. First try disabling
>> firewalls on all machines and see if it helps out.
>>
>> HTH,
>> John

> Thanks for the help! I turned off all the computers but my laptop
> and the server. I can now see the server. I think it might be my
> son's machine causing the problem. It is an HP Desktop running
> Vista, using the Windows firewall. Do you have some suggestions
> as to how the firewall should be setup? Is there a wizard that
> can be run?

I'm not familiar with Vista (wrong newsgroup), but in XP / control
panel / Windows Firewall - you go to the Exceptions tab and make sure
"File and Printer Sharing" is checked as an exemption.

Another way to keep one firewalled computer from affecting others is to
stop its "Browser" service. (Actually only one computer needs to have
the Browser service running on a subnet).
Start->Run->Services.msc
Find & double-click "Computer Browser" then click the Stop button and
then change "Startup Type" to "Disabled".

HTH,
John