After booting my wired-LAN-connected notebook it lasts (sometimes) a rather long time (up to 15 minutes) until
my notebook gets visible in the LAN network resp. the exiting other computers are visible in the notebooks network
neighborhood.

Is there way to speed up the browser contacting ?

I assume that there must be a way to force the notebook immediately after network changes to investigate
other computers.

Is there a parameter / Registry tweak for this ?

Wolfgang

I suspect this is a master browser issue - in a workgroup setting, since
there are no domain controllers to keep a list of available workstations on
the network one computer will become the master browser and maintain a list
of workstations.  When a computer is started up or shut down an election
will be forced to select a new master browser:

http://support.microsoft.com/kb/188001
http://support.microsoft.com/kb/q102878/
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/cnet/cnfi_brs_oynw.asp

There's no way to speed the process up other than to designate one computer
as the master browser and disable browse master on the others but then you
run the risk of browsing not working at all if the master browser is off.

Show quoteHide quote

The computer browser service relies on broadcasts which increases the
possibility of collisions and dropped packets.  This frequently causes
latency and delays in compiling a browse list:

http://support.microsoft.com/kb/188001/en-us

One of the things you can do is reduce the possibility of delay-causing
elections by turning off the Computer Browser service on all but one of your
computers.  This may not be practical unless you have a computer which is
always on.  Another solution is to switch to static IP addresses and lmhosts
files.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

rather long time (up to 15 minutes) until
computers are visible in the notebooks network
network changes to investigate
Show quoteHide quote

w.herc***@hotmail.com (Wolfgang Hercker) wrote in
Show quoteHide quoteThe delay you speak of is normal for Windows Networking.

If you want to speed up the registration on your local subnet, you
can issue the command:
   browstat forceannounce <network> <domain>
from a command window.  This will force all computers on the subnet
to announce themselves to the master browser on the subnet.

If you have a WINS server and are talking about registering across
subnets, then you have to wait until your subnet's browse master
announces the local list to the WINS server.  This is done on a
rather slow schedule to keep the WINS server from being swamped with
announcements on a large network.

Browstat.exe is available at:
<http://www.microsoft.com/downloads/details.aspx?FamilyId=49AE8576-9BB9-4126-9761-BA8011FABF38&displaylang=en>

More information here:
"Troubleshooting the Microsoft Computer Browser Service"
<http://support.microsoft.com/kb/188305/>

HTH,
  John

Home Networking
Windows XP "Domain not found"
remote procedure call failed and did not execute
Security - tcpview established connections paranoia
DHCP client refuses to start
DSL and USB Connection
Disconnect TCP connections shown in Netstat
Remote Desktop Web Connection Failure
No TCP, yet UDP and ICMP still work
Remember password for a network share