Workgroup computers cannot be seen until restart

[kimiraikkonen]

Hi,
I have a client machine with XP Home SP2 and remote PC running on W2k
pro Sp4.

Although all of serices and protocols are running(NetBIOS enabled and
server service is running with dependicies),
Until i restart XP Home SP2 machine, i cannot see remote computer
which is on the same Workgroup named MSHOME.

I connect these 2 computers through my router and remote PC needs to
be rebooted also to see client (XP Home SP2) machine.

Anyway, if a machine connects the sama workgroup, one of the machines
needs to be rebooted to see themselves on the same network by clicking
''view workgroup computers''.

Why does Windows wants to a fresh restart to recognize all the
computers well?

Secondly, if the remote PC turns off after which is on the same
workgroup, the client PC still sees the remote PC even cannot reach
remote PC as normal (it's turned off). WHY is the turned off PC listed
in the ''view workgroup computers''?

I think sharing in Windows (especially workgroup) is a great success
of a user!

Thanks...

 

[Steve Winograd [MVP]]

Hi,
I have a client machine with XP Home SP2 and remote PC running on W2k
pro Sp4.

Although all of serices and protocols are running(NetBIOS enabled and
server service is running with dependicies),
Until i restart XP Home SP2 machine, i cannot see remote computer
which is on the same Workgroup named MSHOME.

I connect these 2 computers through my router and remote PC needs to
be rebooted also to see client (XP Home SP2) machine.

Anyway, if a machine connects the sama workgroup, one of the machines
needs to be rebooted to see themselves on the same network by clicking
''view workgroup computers''.

Why does Windows wants to a fresh restart to recognize all the
computers well?

Secondly, if the remote PC turns off after which is on the same
workgroup, the client PC still sees the remote PC even cannot reach
remote PC as normal (it's turned off). WHY is the turned off PC listed
in the ''view workgroup computers''?

I think sharing in Windows (especially workgroup) is a great success
of a user!

Thanks...

In my experience, workgroup browsing through My Network Places is
inherently unreliable -- so unreliable that I recommend not using it.
You can spend a lot of time trying to troubleshoot it, but I don't
think it's worth the effort.

Here are two ways to access another computer directly:

1. Type the other computer's name in the Start > Run box in this
format:

\\computer

2. Create a desktop shortcut to the other computer: right-click a
blank spot on the desktop, click New, click Shortcut, and specify the
location of the item as:

\\computer

Both methods will open a window containing the other computer's shared
disks and folders.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Chuck]

Hi,
I have a client machine with XP Home SP2 and remote PC running on W2k
pro Sp4.

Although all of serices and protocols are running(NetBIOS enabled and
server service is running with dependicies),
Until i restart XP Home SP2 machine, i cannot see remote computer
which is on the same Workgroup named MSHOME.

I connect these 2 computers through my router and remote PC needs to
be rebooted also to see client (XP Home SP2) machine.

Anyway, if a machine connects the sama workgroup, one of the machines
needs to be rebooted to see themselves on the same network by clicking
''view workgroup computers''.

Why does Windows wants to a fresh restart to recognize all the
computers well?

Secondly, if the remote PC turns off after which is on the same
workgroup, the client PC still sees the remote PC even cannot reach
remote PC as normal (it's turned off). WHY is the turned off PC listed
in the ''view workgroup computers''?

I think sharing in Windows (especially workgroup) is a great success
of a user!

Thanks...

You're talking about a total of 2 computers? Or more?

You have a browser problem here (I'm not mentioning Internet Explorer). The
browser is the process that keeps "View Workgroup Computers" up to date.
<http://nitecruzr.blogspot.com/2006/09/nt-browser-and-windows-networking.html>
http://nitecruzr.blogspot.com/2006/09/nt-browser-and-windows-networking.html

When you have a problem, look at "browstat status", "ipconfig /all", "net config
server", and "net config workstation", from each computer, and 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

 

[kimiraikkonen]

In my experience, workgroup browsing through My Network Places is
inherently unreliable -- so unreliable that I recommend not using it.
You can spend a lot of time trying to troubleshoot it, but I don't
think it's worth the effort.

Here are two ways to access another computer directly:

1. Type the other computer's name in the Start > Run box in this
format:

\\computer

2. Create a desktop shortcut to the other computer: right-click a
blank spot on the desktop, click New, click Shortcut, and specify the
location of the item as:

\\computer

Both methods will open a window containing the other computer's shared
disks and folders.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Programhttp://mvp.support.microsoft.com- Hide quoted text -

- Show quoted text -

I stronly agree with you, also you can create a shortcut to a remote
computer to connect with double click. Creating a .lnk (shotcut file \
\computer)