Slow Network

Time after time I set up a network only to find that the computers don't
"see" each other in the workgroup - at least not right away. Just yesterday
it happened again where I had to wait for over 10 minutes for a network list
of computers to show up.

This is a huge time-waster and makes for very inefficient networking
configuration work.

I've surely read about the Master Browser and have tried some "tricks" that
don't seem to do much.

Has this been discussed, suggested as needing a fix, etc? I view this as a
major limitation because I have to deal with it all the time in small
networks.

Last time I asked, nobody answered. So, I've changed the question a bit.

Thanks,

Fred

On Tue, 4 Aug 2009 09:27:25 -0700, "Fred Marshall"
wrote:

Time after time I set up a network only to find that the computers don't
"see" each other in the workgroup - at least not right away. Just yesterday
it happened again where I had to wait for over 10 minutes for a network list
of computers to show up.

This is a huge time-waster and makes for very inefficient networking
configuration work.

I've surely read about the Master Browser and have tried some "tricks" that
don't seem to do much.

Has this been discussed, suggested as needing a fix, etc? I view this as a
major limitation because I have to deal with it all the time in small
networks.

Last time I asked, nobody answered. So, I've changed the question a bit.

Thanks,

Fred

Unfortunately, that's not unusual. It often takes up to 10-15 minutes
for network browsing (My Network Places) to start working.

IMHO, network browsing is badly designed and inherently unreliable.
You can spend a lot of time troubleshooting it, but I don't think it's
worth the effort.

The solution is not to use network browsing at all. To access
another computer immediately, type the other computer's name in the
Start Run box in this format:

\\computer

You can also create a desktop shortcut to another computer, specifying
the location of the item in the same format.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Desktop Experience)

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

On Tue, 4 Aug 2009 09:27:25 -0700, "Fred Marshall"
wrote:

Time after time I set up a network only to find that the computers don't
"see" each other in the workgroup - at least not right away. Just yesterday
it happened again where I had to wait for over 10 minutes for a network list
of computers to show up.

This is a huge time-waster and makes for very inefficient networking
configuration work.

I've surely read about the Master Browser and have tried some "tricks" that
don't seem to do much.

Has this been discussed, suggested as needing a fix, etc? I view this as a
major limitation because I have to deal with it all the time in small
networks.

Last time I asked, nobody answered. So, I've changed the question a bit.

Thanks,

Fred

Unfortunately, that's not unusual. It often takes up to 10-15 minutes
for network browsing (My Network Places) to start working.

IMHO, network browsing is badly designed and inherently unreliable.
You can spend a lot of time troubleshooting it, but I don't think it's
worth the effort.

The solution is not to use network browsing at all. To access
another computer immediately, type the other computer's name in the
Start Run box in this format:

\\computer

You can also create a desktop shortcut to another computer, specifying
the location of the item in the same format.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Desktop Experience)

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

"Fred Marshall" wrote in
:

Time after time I set up a network only to find that the computers
don't "see" each other in the workgroup - at least not right away.
Just yesterday it happened again where I had to wait for over 10
minutes for a network list of computers to show up.

This is a huge time-waster and makes for very inefficient
networking configuration work.

I've surely read about the Master Browser and have tried some
"tricks" that don't seem to do much.

Has this been discussed, suggested as needing a fix, etc? I view
this as a major limitation because I have to deal with it all the
time in small networks.

This time delay is built-in by Microsoft's design.

A lot depends on your network topology (which you don't mention).
If your network consists of a single local subnet, then you can use
the Browstat utility to force everyone on the subnet to announce to
the master browser and within a half minute or so, the master browser
should be up to date (browstat fa).

If your network is more than one subnet and has a PDC, then you
might hasten the process by killing the current master browser
(Browstat tic) and forcing an election of a new master browser
(browstat el). If one of the backup browsers (BBR) is elected, it
may come up with a stale list until it refreshes. You may have to
repeat the process until a browser is forced to query the PDC.

Browstat:
http://networking.nitecruzr.net/2005/05/browstat-utility-from-microsoft.html

HTH,
John

"Fred Marshall" wrote in
:

Time after time I set up a network only to find that the computers
don't "see" each other in the workgroup - at least not right away.
Just yesterday it happened again where I had to wait for over 10
minutes for a network list of computers to show up.

This is a huge time-waster and makes for very inefficient
networking configuration work.

I've surely read about the Master Browser and have tried some
"tricks" that don't seem to do much.

Has this been discussed, suggested as needing a fix, etc? I view
this as a major limitation because I have to deal with it all the
time in small networks.

This time delay is built-in by Microsoft's design.

A lot depends on your network topology (which you don't mention).
If your network consists of a single local subnet, then you can use
the Browstat utility to force everyone on the subnet to announce to
the master browser and within a half minute or so, the master browser
should be up to date (browstat fa).

If your network is more than one subnet and has a PDC, then you
might hasten the process by killing the current master browser
(Browstat tic) and forcing an election of a new master browser
(browstat el). If one of the backup browsers (BBR) is elected, it
may come up with a stale list until it refreshes. You may have to
repeat the process until a browser is forced to query the PDC.

Browstat:
http://networking.nitecruzr.net/2005/05/browstat-utility-from-microsoft.html

HTH,
John

The answer is straightforward, but probably not what you were expecting.
Sharing files from multiple computers is not a good way to work. It creates
far more problems than centralised storage. Allocate one computer as the data
store, and have the other computers map a driveletter to a share on this one
computer.

For 10 users you can implement this by way of a simple utility, or for
larger groups by purchasing a 'real' server, which could be a Windows server,
or Linux.

A server-based system requires you to get one connection working per
computer. A 'cat's cradle' workgoup of ten requires you to keep 90
connections working. In which case you most likely have a fulltime job on
your hands!

The other downside of 'cat's cradle' sharing is that you generally cannot
switch ANY computer off during working hours. Even if only one person is
working, all the computers must be on, otherwise problems with inaccessible
shares arise, which typically manifest as hesitation and delays in Explorer.

"Fred Marshall" wrote:

Time after time I set up a network only to find that the computers don't
"see" each other in the workgroup - at least not right away. Just yesterday
it happened again where I had to wait for over 10 minutes for a network list
of computers to show up.

This is a huge time-waster and makes for very inefficient networking
configuration work.

I've surely read about the Master Browser and have tried some "tricks" that
don't seem to do much.

Has this been discussed, suggested as needing a fix, etc? I view this as a
major limitation because I have to deal with it all the time in small
networks.

Last time I asked, nobody answered. So, I've changed the question a bit.

Thanks,

Fred

The answer is straightforward, but probably not what you were expecting.
Sharing files from multiple computers is not a good way to work. It creates
far more problems than centralised storage. Allocate one computer as the data
store, and have the other computers map a driveletter to a share on this one
computer.

For 10 users you can implement this by way of a simple utility, or for
larger groups by purchasing a 'real' server, which could be a Windows server,
or Linux.

A server-based system requires you to get one connection working per
computer. A 'cat's cradle' workgoup of ten requires you to keep 90
connections working. In which case you most likely have a fulltime job on
your hands!

The other downside of 'cat's cradle' sharing is that you generally cannot
switch ANY computer off during working hours. Even if only one person is
working, all the computers must be on, otherwise problems with inaccessible
shares arise, which typically manifest as hesitation and delays in Explorer.

"Fred Marshall" wrote:

Time after time I set up a network only to find that the computers don't
"see" each other in the workgroup - at least not right away. Just yesterday
it happened again where I had to wait for over 10 minutes for a network list
of computers to show up.

This is a huge time-waster and makes for very inefficient networking
configuration work.

I've surely read about the Master Browser and have tried some "tricks" that
don't seem to do much.

Has this been discussed, suggested as needing a fix, etc? I view this as a
major limitation because I have to deal with it all the time in small
networks.

Last time I asked, nobody answered. So, I've changed the question a bit.

Thanks,

Fred