Unable to browse network

[eicken]

I am using Netbeui for a small network in my home. The problem is my
laptop will see both my desktop and laptop when you click on network
neighborhood. If you click on network neighborhood on my desktop it does
not see the laptop. I am also using a modem share program throught the
network and it works fine. All cables are fine and cards config properly
also the hub is config.properly.
Any help will greatly be appreciated. Installed and reinstalled all
network settings.

[Jin Vitas]

Make sure you have file and print sharing enabled on both computers.. also try to connect to the computer by mapping to \\name\c$

[eicken]

Here is the latest. Removed all network settings and NIC. Rebooted. Shut system down and replaced NIC rebooted reset all network settings. Still the same problem.
Any suggestions??

[Boy]

Make sure your netbeui is set to default protocol on your desktop, and not the ip for your modem.

start there, see what that does.

-k-

[Myke]

Try this.

Double click the network icon in control panel on your desktop computer.
Highlight file and printer sharing for microsoft networks then click the proprties button.
Highlight Browse Master then choose enable in the Value drop down list.
Click ok, exit and restart your computer.
Hope that works. Good luck.


[This message has been edited by Myke (edited 03-27-99).]

[This message has been edited by Myke (edited 03-27-99).]

[eicken]

Its working
I searched the net and found a solution
I went into the registry
HKEY_LOCAL__MACHINE\software\microsoft\windows\cur rent version\network\real mode net
Deleted Autologon=0
Rebooted
I waited a few moments and the computer appeared in network neighborhood

Everyone thank you for your help


[This message has been edited by eicken (edited 03-30-99).]

[Boy]

hey I wouldn't have thought of that...

Thanks for updating and letting us know what fixed it. that is great information.

-k-

[ridefree]

Sounds like you didn't have "logon and restore network connections" enabled under the properties for your network client.
Probably would have had the same effect if you had changed to Autologon=1...?