IT Employment

Ask something
Discussion Locked

NT Server and Peer to Peer

0 helpful
4 replies

by wagman 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have several laptops setup on an NT server and everything works well, TCP/IP and file and Print Sharing. Now I would like to take two or three of them to a clients site and setup a small peer to peer so they can share files and printers while doing audit work. Now I set it up and everything work just right without changing anything, but when they got back to the clients only one of the three got the login screen and was able to see the network neighborhood. The other 2 got the basic windows login screen instead of the network login screen. Everything is identical except nics and it had worked when I first attempted. Anyone have any ideas? Thanks in advance.

4 replies

by buckrogers

What OS is running on the laptops? If it is 9x you can right click Network Neighborhood select properties, then below you should see Primary Netowork Login make sure it is set for Client for Microsoft Network, and not Windows login.

by wagman

I made sure this was correct. They were all three 95 machine. The funny thing is that I had them setup this am the same way as we did the very first time and it appear to work. I don't understand why there would be a problem with the order. Seems like it should see the mini-network and login no matter who started first.

by ni70

Did you check the Client for Microsoft Networks properties and uncheck logon to nt domain? You may also want to try adding the NetBUI protocol.

by edwarvel

For a small peer to peer network use the NetBEUI protocol rather than TCP/IP. Windows 95 can be quirky on a TCP/IP type of network unless there is an NT machine that is serving as the base for the network. If anyone on the network is going to be using the internet (especially w/ broadband) make sure you check out www.grc.com for detailed instructions on how to secure a peer to peer network from internet attack (another good reason to use NetBEUI instead of TCP/IP).

This discussion is closed to new replies.