Windows Forum

Ask something
Discussion Locked

Logon across router

0 helpful
13 replies

by paul.brannigan

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

I have a portable which can logon on to a domain when wired on site. It runs on Win2k with tcpip.
When it is either connected to the network via isdn to a router or on a remote network connected across isdn from its router to the main site router I can ping any other device by number, I can ping the domain server by name due to a host file and I can run Outlok to connect to Exchange server running on the domain server which is running NT sbs 4.5. However, I cannot make a drive connection or browse the network via network neighbourhood. I have tried lmhost file but without success. I may not be getting the scripting correct.

13 replies

by paul.brannigan

WINS but how can I tell if it is setup right? Does the remote computer need to have its address or name entered?

by isys

Check to see if your DNS server is the one you want. If you can ping your network devices by name then it could be NETBUI. But if you can't ping by name, it's DNS.

by paul.brannigan

How can I check the DNS settings? I am unfamiliar with it. TCPIP is the only protocol on the server. Do I have to separately implement netbios over TCPIP?

by green lantern

Make sure your router is enabling ports 137,138 and 139. These are required for your NetBIOS name resolution. The lmhosts sample file should be all you need to establish a proper NetBIOS connection. If you can ping but NOT do
"net view \\"
then you have a NetBIOS problem. Ping is just tcpip resolution.

ralph

by curlergirl

The remote computer must have the correct WINS and/or DNS settings to be able to resolve NetBIOS names. NetBIOS over TCP/IP is generally enabled by default, but if the workstation is XP or Win2K, you should double check this (in the Control Panel/Network/TCPIP properties). If you are using a router connection, make sure that the IP address of the WINS and/or DNS server(s) are also correct in the TCP/IP properties settings. Also make sure that you are using the correct gateway address at the remote location (this is probably OK if you can ping). If your workstation is set up to use a DHCP server for these settings, the problem may be that the local DHCP server at the remote site is not serving out the correct addresses for WINS and/or DNS at the main office. If this is the case, you may have to set them up statically on the laptop - this will override any DHCP server settings that you may encounter. However, if you have a WINS server at the remote location that is handling the remote office WINS resolution, and it is not replicating with the main office, you will run into trouble trying to resolve names locally (at the remote site) after you have changed the WINS settings to use the main office server. Hope this helps!

by curlergirl

The remote computer must have the correct WINS and/or DNS settings to be able to resolve NetBIOS names. NetBIOS over TCP/IP is generally enabled by default, but if the workstation is XP or Win2K, you should double check this (in the Control Panel/Network/TCPIP properties). If you are using a router connection, make sure that the IP address of the WINS and/or DNS server(s) are also correct in the TCP/IP properties settings. Also make sure that you are using the correct gateway address at the remote location (this is probably OK if you can ping). If your workstation is set up to use a DHCP server for these settings, the problem may be that the local DHCP server at the remote site is not serving out the correct addresses for WINS and/or DNS at the main office. If this is the case, you may have to set them up statically on the laptop - this will override any DHCP server settings that you may encounter. However, if you have a WINS server at the remote location that is handling the remote office WINS resolution, and it is not replicating with the main office, you will run into trouble trying to resolve names locally (at the remote site) after you have changed the WINS settings to use the main office server. Hope this helps!

by mike mullins

Most of the other answers hint at the problem. But the solution is this:

1. You need a lmhost file that resolves the domain name to the ip of the PDC/BDC that will authenticate your request.

2. You need the following ports open inbound to thatPDC/BDC on any routers/firewalls that are between you and your destination.

a. Browsing - UDP 137,138
b. Netlogon - UDP 138
c. Logon Sequence - UDP 137,138 TCP 139
d. File Sharing - TCP 139

That should cover your Logon, Netlogon, Browsing and File Sharing (retreival)

That covers it.

This discussion is closed to new replies.