Discussion Locked

Peer to Peer and Client/Server Networks

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

I have an NT Client/Server network at the office and a peer to peer netowrk at home. I want the peer to peer network to be part of the office's work group and domain so that I can make a VPN connection and log on from home.

The peer to peer network is operating quite slowly on one machine(taking a long time to access the network via network neighborhood)which has a host and lmhost file that corresponds to the client server network. THe machine withouy lmhost and host files accesses the network quickly. I am presuming that the host/lmhost files on the slow machine are the culprit, but not certain.

What is the proper configuration to use? Is there an entry in lmhost and host file for the peer to peer network that will speed up network recognition? I am running DHCP. Or do these files mess things up on the peer network? Without them, however, I can't get WINS resolution when connecting to the office client/server network.

Any suggestions?

Thank you.

7 replies

by henington

Here is my advice.

Create user account on your work domain. Log on to the internet as normal at home and create a VPN to your work. Enter the user and password you created on your work domain and you should be fine. You do not need your home computers to be part of your work domain in order for a VPN to work. The only thing you need is a login and password on your work domain with VPN set up and rights to access whatever you want to access at work. DHCP at work can also be set up to reserve a set of IP addresses to assign to VPN clients only. Email me if you need any more help.

heningtontt@pendleton.usmc.mil

Oh and your LMHost issue i believe is because the computer that has LMHost on it is connected to the VPN ?? That would be my guess is that the computer with the LMHost is connected to the internet or your VPN at work or something and that other connection is choking it because it doesnt know where to go. When you open Network Neighborhood it starts scannin for hosts and the other connection it has isnt reporting anything.

by bledsoe

Thanks very much for your response.

I have found that with NT authentication, unless the logon name, password and domain are filled in completely at boot up of the remote computer, you can have great difficulty logging on to the NT network. So having a different domain on my local peer to peer network from the network server could be a problem.

Logging into the server requires the lmhost file to have the server name and IP address. So if this is causing the problem on my peer to peer network, removing it will prevent connecting to the exchange server. Is there another entry I can make on the lmhost or host record which will allow the remote client to connect easily with the peer to peer network in my home?

by henington

You can have two completely different domains and still connect via VPN. Here is my setup and experience with VPN. I have a win2k adv server running dns and DHCP. my domain is henington.net. A buddy of mine has a domain ram-net.com. Went to network places and created a new connection. A vpn connection. He simply gave me a login to his domain and a password. I connect using the VPN created and it asks me for login and password. I enter the info and im in His domain now (effectivly). The only thing I can see is still shares he gives me permissions to view of course but this shows that the two networks do not need to be on same domain. A VPN allows connections of different domains through existing internet connections. We even went a step further to encrypt the connection for security. Now our network are 2k but im sure its very similar in NT. Little added security in 2k.

I really dont think the LMHost file is your problem. As far as seeing your exchange server once youVPN to your work network DHCP will assign you an IP for that VPN session and you should have no problem seeing the exchange server. Have you gotten the VPN to work successfully and still cant see the exchage server and still having choking on your one PC ?

by saihib

Your machines at home don't need to join your domain at work in order for you to connect via VPN. All you need are the proper rights on your VPN server and a properly configured VPN DUN connection at home.

This discussion is closed to new replies.