Discussion Locked

Login across the Internet

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
My server has an internet-know IP address(not 10.x.x.x or 192.168.x.x). How can I login to NT from my house or a branch office across the internet without special software? We would rather not use a VPN or PPTP. I also know that you can map a drive across the internet but I need to know how. It is a path context or some other format? We want to be able to do this as simple as possible, i.e. using "net use" commands or built in funtions.

13 replies

by steve cody

Be aware that by doing this, you are creating a big security risk by allowing this type of login.
Make sure on your home computer that you use a user account and password that is valid on your server.
Go into the LMHOSTS file or LMHOSTS.SAM on your home system. Create an entry for your server:
x.x.x.x SERVERNAME #PRE #DOM:domainname

Then, at a DOS prompt, type NBTSTAT -R.
Test out pinging your servers name. PING servername. If that works, then you can then try to connect to the server. In Windows, do a START, RUN, and enter \\servername. Click OK, and see if your server's shares become available. That's it. Map a share or printer, or whatever.
- Steve

by inspectorclave

You will need to add the LMHOSTS entry as stated in #1. However, you will also need to make sure that the appropriate ports are open on your proxy server to allow the traffic in and out. There are too many ports to list in this response, but I would say that it would be MUCH easier and MUCH safer to setup a VPN. All you need for a VPN is the PPTP protocol installed on your server, and the VPN client on the workstations. I would be interested in finding out why you do not want to use VPN's.They really are nice and you won't have the HUGE security gap that you otherwise would.

(you can also use RAS (Remote Access Server) but that is only available through dial-up access... not the Internet.

by aaron v

I just have to say that I would not recommend this approach. I agree with a previous question, "Why not VPN?" If this is due to issues you have seen regarding weaknesses in PPTP, you might consider a firewall appliance VPN solution (I believe WatchGuard has automatic VPN with some products).

If you are dead-set against VPN's, then I would recommend creating a high-encryption private web site with access to your files. Then those who connect will need a 128bit browser and valid username and password.

by Former member

1. You cannot map a drive witout being authenticated.
2. Your IP address has to be made part of the NT network you're trying to attach to. This is part of what VPNs do. WHen you VPN, you get a IP address of the local subnet.
3. Your IP address will be routed via EGP's but will not be recognized as part of your NT LAN/WAN IGP. I think somewhere along the line you're gonna have to install some sort of PPP protocol in order to use the connection-oriented NT protocols.
4. You could install an FTP service on your NT server and FTP into your server from your client. Be sure to include login permissions!

by _degan_

You should use VPN.

Otherwise, you will need the LMHOST entry as specified, and TCP port 139 open between your locations. Then you can use the standard NET USE commands to access your remote resource, as can anyone else who hacks a valid ID and password.

by nrodriguez

I am not so sure how you can login normally over the internet except with special software. you can install iis 4.0 and make you drive to you servers viewable through html or ftp. this will require logins. but i have never seen anyone log in regularyly without vpn or pptp

below is how you map drives.

you can map drive to different ways. the first is with net use. wks100.acme.com.... is the host name of the machine

Net use * \\WKS100\public
or you can type
Net use * \\WKS100.acme.com\public

or you could use a command from the nt resource kit called inet

inet use x: \\ftp.microsoft.com\public

this is according to the microsoft windows nt 4.0 and dns white paper.

dnswp.doc or download from ms dnswp.exe

This discussion is closed to new replies.