Discussion Locked

95 pc not shown in NT Net Neighborhood

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a 95 workstation that I cannot get to show up in the network neighborhood. I have tried turning on file and printer sharing, NetBEUI, Wins resolution using DNS, and the workstation will not show up in the network neighborhood. What can I be missing?? Is there some secret software that has to be installed on 95 boxes to make them visible? The first response that gets results gets the points.

Thanks

Dennis

17 replies

by turambar386

One reason would be if the computer name ends in a dollar sign. This makes them invisible to browsing.

by maxwell edison

The "step-by-step" procedures are:

Right click on Network Neighborhood - Properties - Add - Service - Add - Microsoft - File and Printer Sharing for Microsoft Networks - OK - OK

You may be prompted to insert the Win95 CD. You'll be instructed to reboot the computer.

You should see that computer name on the Network Neighborhood. You'll have to go back to that computer and define a device to be shared, a drive, folder or printer, but you should at least see the computer on N.N.

If not, go back to Network properties and add the protocol TCP/IP.

Good luck,

Max

by curlergirl

For Win95 to be part of NT network and show in NN, you need:
1. Appropriate protocol installed - i.e, TCP/IP or NetBEUI depending on what you're using - and configured. If using TCP/IP, it must be properly configured to be on the same subnet as the rest of the network.
2. Protocol bound properly to network card.
3. Client for MS Networks installed and configured to log on to the NT domain.
4. Network Properties/Identification tab - the workgroup name must be the same as the domain name.
5. File and printer sharing enabled - do not have to share anything but it needs to be installed.
6. As someone else said - don't use a computer name with a $ in it.
7. If using TCP/IP, name resolution must be configured either by using WINS server or LMHOSTS file.

That said, can you browse the network and use network resources from the PC? Can you ping the PC by name and IP (if using TCP/IP)? If all of the above is OK, we need add'l. info to troubleshoot. Hope this helps!

by sed55

I neglected to tell you that:
1) My machine name does not contain a $
2) The workgroup name is the same as the domain name
3) Using TCP/IP also as the primary protocol
4) Using DHCP with WINS using DNS.

Sorry for these omissions.

by admin-stuart

Sometime the secret's in the hardware, not software. If you've taken pains to configure the proper network software components, and you're sure their is a common protocol on the network, whether TCP-IP or NetBeui, I would try a different NIC, maybea good standard tried and tested one like a 3Com 3C-90x. Take the NIC that's in the machine now and stick it in another PC, try to duplicate the problem elsewhere to narrow it down.

by pahosler

You didn't mention if you have tried to ping either box. Can you see the NT server from your 95 box net neighborhood? Try Start>run>winipcfg to make sure you are getting assigned a proper IP from your DHCP server. But all in all, logically if youcan ping it, and you have something set-up to share then you should be able to see it.

Regards,
Paul

by shanghai sam

It was pinging from my workstation, by IP, and by name. Had the C drive shared. Still not on the N.N.

by stillatit

Picking off some other simple problems, the machine name is under 15 characters, and all alphanumeric, right? No spaces or other special characters?

If you are using WINS, every station on your LAN should be using WINS, and all pointing at the same server.

I assume you can ping your problem box from other machines, and the problem box can ping everyone else. If this is not the case, look for a cable problem, or a wrong IP address or wrong subnet mask.

Given all that, try these tests. Assume the box name is FRED in these examples, and that its IP address is 192.168.0.42:

First, test whether or not some other station can see your problem box. On another box, click Start, Run, and type in \\192.168.0.42 and click OK. Does the content of FRED show up, or do you get an error message? If the error message, the problem probably in the protocol stack. Remove and reinstall NETBEUI.

On another box, click Start, Run, and type in \\FRED and click OK. Does the content of FRED show up, or do you get an error message? If the error message, your name is not being recognized. Check the WINS database and see what is there. Check that the node type is set to hybrid, so that name resolution is actually using WINS.

Trying the tests on FRED, looking to connect to an other station will tell you if the protocol stacks on FRED are OK. If everything works, it is time to look for wierdness. Get a copy of tweakui from www.download.com (or wherever), and look at the setting that makes the box invisible to the network. There is a registry key for this, but I do not have it, and tweakui is easier.

Another longshot:
a) make very sure that your workgroup name is exactly the same as the domain name (no trailing spaces).
b) put anentry in your lmhosts file for the domain controller, using the #PRE and #DOM: tags.
This should force the station to find the domain.

Good luck.

by shanghai sam

MAchine name is VA12013
Using DHCP on the network.. WINS server is defined for all workstations
Boxes can ping each other by IP and name
Not using NetBEUI, but using TCP/IP only
WIll try the other suggestions you make.

by sed55

I didn't mean to close this question... I was not done trying the suggestions.

by sed55

The problem has been solved on this particular box. There was a device driver in the [386enh] section of 'system.ini' called 'smsroutr.vxd'. I guess it is a byproduct of SMS. I commented this line out (since we no longer have SMS running), and lo and behold the box shows up in Network Neighborhood, and in the Domain Server Manager. Thanks to all who offered solutions, as this turned out not to be your run of the mill problem.

Dennis

This discussion is closed to new replies.