Discussion Locked

NT Logon

0 helpful
19 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I've got a Win98 machine that will logon to the local NT network but will not logon to the remote NT network (through a router). I am able to ping the PDC on the remote domain but it refuses to authenticate. I brought the PC to the opposite side of therouter and it won't authenticate to the server on te other side. Any ideas?

19 replies

by bschorr

Do you get an error message? Are you saying that you can only logon to the server(s) on the same side of your router - i.e. whichever side of the router you're on, you can log in there?

If so, make sure that you have the UDP ports (137, 138 and especially 139) open on your router. They're needed for NetBIOS communication in Microsoft networking.

If you mean that you just can't log onto that remote domain regardless of which side of the router you're on...have you checked in Networking properties to make sure that you have the correct domain specified? Also do you have a valid and enabled account on the NT Server, are you using the correct password and remember that passwords are case-sensitive.

Aloha,

-Ben-
http://home.hawaii.rr.com/schorr

by mkelley

Possibly are you running TCP/IP with DHCP on the PDC? If so make sure your router passes DHCP discovery packets. Run winipcfg at the run line to see if your PC is getting an IP address from the DHCP server.

by jeff_gebhart

Are you running IP as a protocol? Is WINS enabled and configured?

When a windows machine attaches to a network without WINS, it can't see across a router.

To find out if this is the problem, copy the LMHOSTS.SAM file in the \WINDOWS directory toLMHOSTS. Add the PDC for the domain that you want to log into to this file, as well as the domain name itself.

In a routed environment, you need either LMHOSTS or WINS, with WINS being much easier to administer in the long run.

by sloaner

Sounds like you dont have a trust set up between the domains. If you set up the trust, it should work!

by bmichon

CHeck your trust to be sure it is configured properly and also check your groups to be sure that the account(s) have the correct permissions to access that domain.

by justinn

I ran into a similar problem to yours. Within the lmhosts file on the Win95/98 machine, type in an entry for the PDC. Make sure you add the #PRE #DOM Parameters to it. This will load the IP address of the PDC into the cache when it starts.

by dirk.deprest

are you working with two PDC's with a different domain, be sure that:
1) you're logging on to that domain
2) be sure the two domains are thrusted
3) on the remote PDC you've got the same
logon name as on the local PDC.

by digital

You tend to see this in dial-up's more than on the network.

The TCP/IP stack in WIN 98 while better than Win 95A is still a little fragile. Normally in this situation we do the follow with success:

1. Go to Start | Setting | Control Pannel
2.OPen the Network Option
3. Drop all networking in the control pannel. (TCP/IP, Netbeui, IPX, Client, etc).
4. Restart to load the generic files back on the system.
5. Repeat Set 1 & 2
6. Add the following: Client for MS Networks, TCP/IP,Netbeuiand restart.
7. You may need to ensure that the pointers in the properties for Client for MS networks and your access tab are set to the proper Domain Name in the provided box's.

Hope this helps.

Ken Foster
Digital Marketing Solutions.

This discussion is closed to new replies.