Lnhosts resolving issue

[Guest]

Greetings. After two full days and one nights fiddling with different setups
and a lot of "save games" in the form of norton ghost partition images, I
finally have arrived at a very up to date and well behaving msXPpro
configuration on both my desktop and my laptop.

workgroup networking works, and computer browsing in "view workgroup
computers" work, with one exception;

Exception being: After restart have to renew my wlan nic on my laptop
manually to get the workgroup-computers to turn up..

I am using netgear WGT624 wlan adsl router, netgear wg511T pc-card. (my
desktop uses pci-card wg311T.) Using the netgear wlan connection tool I
choose apply to reconnect to the wlan. After this reconnect all of my
computers turn up in..

to get my workgroup working at all, I had to turn to lnhosts lookup. My
lnhosts on my computers look like this:

a.local.ip.here nameofhoststablepc #PRE

#include \\nameofhoststablepc\lnhosts\lnhostsfile

this works great, but it seems my lns lookup is performed _before_ my wlan
card has connected..

is there any way of postponing lnhosts lookup? oris there a way to force the
lnhosts lookup (include statement) to be performed on nic connect or
successfull wlan connect? or even to force it to be performed multiple times
(with no trigging event)

Hope someone finds this problem interesting, and even has a great answer!

thanks anyway, and have a nice day!

Regards, Øyvind Graham

 

[Doug Sherman [MVP]]

Not sure I followed all of this, but you can purge the name cache and reload
lmhosts with:

nbtstat -RR

Doug Sherman
MCSE, MCSA, MCP+I, MVP

 

[Guest]

Thanks for your answer, it made it possible for me to verify that the lmhosts
file indeed was not loaded from the server until I purged and reloaded it.
This leads me to this tentative conclution;

1. the loading of the linked lnhostsfile happens before my wlanconnection is
up.
and maybe the drivers of my netgear don't do a call to this purge-mechanism?

I decided to go back to basics, and find out why I had to use lnhosts in the
first place. This was because I couldnt get the names broadcasted to each
desktop othervise. I solved this by removing a network bridge made by my
cisco vpn client, removing its inbuilt stateful firewall on one of the hosts,
and removing netbeui protocol, and allowing netbeui over ip.

Having done this My workgroup worked like a charm.

It helps to write it...

 

[Doug Sherman [MVP]]

Go get 'em, Øyvind!

Doug Sherman
MCSE, MCSA, MCP+I, MVP