I am having some difficulty with a laptop and was wondering if any of

[warmongr]

I am having some difficulty with a laptop and was wondering if any of you have seen <br>
this before I invest several hours of TS'ing. My user has a laptop that is <br>
currently set up as pippy. From Pippy I can telnet to any <br>
machine. I can surf the web. I can send and recieve email. But each time I go to <br>
Network Neighborhood the response is so slow that eventually his task list shows a <br>
'Not Responding' error. I believed it to be a resolution problem however all his <br>
network settings are correct. This is causing a problem when trying to access <br>
network resources such as printing and surfing the network Neighborhood. <br>
Is this a samba problem? I thought so at first and don't want to rule this out however it is the same whether he is accessing a samba server or not. <br>
<br>
Machine stats:<br>
<br>
<br>
Gateway Solo 9100<br>
Win98 SE<br>
IE 5.0<br>
<br>
All critical patches from Microsoft have been applied.<br>
<br>
Any ideas would be appreciated.<br>
<br>
Thanks,<br>
Natr

 

[sijones]

The first of all make sure the ip address is correct and no other computer on the network has the same one, if he is connected by the LAN to the internet then make sure you use one of the reserved addesses for LAN's ie 192.168.X.X I had the same problem with windows when connecting though a direct cable connection, I could do a find for the other computer but could not network neighbourhood search.<br>
<br>
The way i solved it was to assign ip addresses and it was ok. but by the sound of it, it seams like you have set win98 to ask a computer what other computers are available but the computer is not sending the list etc...<br>
Hard to explain really, if your running a dhcp service check the gateway settings, make sure you have a gateway set, if your not sure you should beable to set it to the internet server ip address. i have done that and it worked.<br>
<br>
hope this helps in some way. By the way samba if running in PDC mode can cause problems like this, best to get the lastest release from <A HREF="

http://www.samba.org"

TARGET="_new">

http://www.samba.org</A>

and try that!<br>
<p>Simon Jones<br><a href=mailto:sijones_uk@yahoo.com>sijones_uk@yahoo.com</a><br><a href=

http://www.theallandale.co.uk>The

Allandale Youth Works</a><br><b>God</b> am good!!! and good lookin

 

[AndyBo]

Sounds like a problem I've heard of before with Windows 9x in general and Network Neighbourhood. It's a problem that's acknowledged by M$, and there's a knowledge base entry somewhere...<br>
<br>
As I understand it, it's a problem with servers on the network arguing over which one is going to be &quot;browse master&quot;.<br>
<br>
For example, you've got four NT servers set up, all sharing directories. You have 12 Windows 9x clients sharing directories on these servers. Regardless of which NT server is PDC and which is BDC, every server and client wants to be the browse master. A kind of &quot;election&quot; takes place, and one of the servers or clients becomes the browse master.<br>
<br>
A minute or so later, (might be 30 seconds), the election takes place again (just in case the original master has been switched off or lost it's network connection). The problem your seeing can occur when Windows has the name of one server cached as browse master, and another server has since won the election.<br>
<br>
When running Samba it can also become a browse master, and become involved in the same election. IIRC, you can disable this feature in the Samba configuration file and ensure that Samba never become browse master.<br>
<br>
There's also a registry tweak you can apply to Windows 9x which lowers the time that the browse master name stays cached. This stops the Windows 9x client getting involved in the &quot;browse of death&quot; that you're seeing at the moment, and would be a permanent fix. Let me know if you can't find the M$ Knowledge Base entry, and I'll try and dig through my literature at home for the details on this.<br>
<br>
A workaround you can use in the meantime is to type in the name of the computer you're trying to find in the Windows &quot;Find Computer&quot; applet. Once you've found the computer, you can browse it's resources and do whatever you want to do.<br>
<br>
Hope this helps.<br>

 

[warmongr]

Sorry to leave everyone hanging on this one.&nbsp;&nbsp;I forgot I posted it.&nbsp;&nbsp;Here was the fix.<br><br>Uninstalled all of his network services and then used a regedit32 to clean the registry of any other network reference references.&nbsp;&nbsp;Rebooted (of course) and then reinstalled all network services.&nbsp;&nbsp;Made him a DHCP client and entered his MAC and IP in the dhcpd.conf file on the server (RH6.0)<br><br>I apologize for posting his thread here however at the time I believed it to be a SAMBA problem and was looking for fixes in that direction.<br><br>Thanks all for your input.<br>war...