the key will be
being able to identify the domain controllers by name, name resolution. if
the pc can't find the domain controller, PDC or BDC in nt4, your pc will not be
able to logon and you see the message you got. if the controller is on a
remote network and you are using tcpip your pc needs to know the address of
the domain controller before making the logon request. not much needs to
be done on the routers excepts making sure the netbios related ports are not
blocked, 135-139 or something like that.
this can be done
in a couple of ways, a local file called lmhosts, which is a static listing
of ip addresses and computernames kind of like a hosts file in a unix
environment. the second is to setup wins resolution, which is a service
that dynamically builds a database of computernames and their tcpip
addresses. this requires a server be running the wins service and a
setting in the client pc TCPIP properties. a third way is to put a Backup
Domain Controller on the remote subnet
will have lots of
information
daveh
|
- Logon to NT Server? Ngo Van Dzung
- Logon to NT Server? Ngo Van Dzung
- Re: Logon to NT Server? Adam Hickey
- RE: Logon to NT Server? Dave Hennen
- RE: Logon to NT Server? Odell, Jeff
- Re: Logon to NT Server? Douglas James Howe
- RE: Logon to NT Server? Michael W. Oliver
- RE: Logon to NT Server? Sereno, Patrick