98 and NT4 clients can't find domain

[tangostar]

W2K domain Mixed Mode.
Clients have DS Client installed
gateway is Cisco 1812
DHCP WINS DNS is on DC

certain 98 and NT4 clients cannot connect to the domain but if I login locally they can ping all computers on the network and access the internet.

any ideas what the problem might be?

 

[tfg13]

Have you tried removing and re-adding the NT4 clients to the domain? Have you removed the "offending" 98 machines out of the AD computers folder, and allowed them to be readded?

 

[ITPangaeaArchitect]

there will not necessarily be a computer acct for downlevel clients (with exception of BDCs)...there is no secure channel established, and that is what the comp. acct. is for....\\personally i do create them though for inventory mgmt sake...

wheres WINS installed? Are your downlevel clients pointing to the correct WINS servers? Is your LMHOSTS file default?

-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there

 

[tangostar]

WINS is on the DC.
There are account for the NT4 and some of the 98.
tried rejoining the NT4 to the domain, but the domain could not be located.
All settings like DNS and WIN are obtained through DHCP.
haven't changed the LMHOSTS file.

 

[Seaspray0]

Check WINS: start, run, \\DCName and enter. Can you find the DC by it's netbios name? What type of records in WINS do you have for your DC?

Check DNS: ping DCName.YourDomain.YourRoot and see if you can resolve and ping the domain controller. Does your DNS server have the .srv records for your domain controller?

When you tried joining the domain, were you typing in the NetBios name of your domain (i.e. MyDomain) or the Fully Qualified Domain Name (FQDN i.e. MyDomain.Local)?

A+/MCP/MCSE/MCDBA

 

[tangostar]

if not logged into domain i cannot browse to servers, so \\Server doesn't work.

Pinging ServerName works fine.
I've tried adding with netbios nad FQDN

what type of SRV records should I have? I have none.

 

[tangostar]

sorry that isn't true.

under the domain name
under _msdcs
under a number of places

I have an _ldap and _kerberos SRVs pointing to the PDC and BDC

 

[ITPangaeaArchitect]

what version of the dsclient do you have? the version released with win2000 is bugged all to hell

there is a newer version but I beleive it is still obtainable only by calling in....

check your version of dsclient and report back the created/modified dates and version number,,,ill see if you are at current version or bugged....


-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there

 

[tangostar]

ya i got that call in version.

 

[ITPangaeaArchitect]

ok cool just wanted to be sure
now, please tell me your not using the extremely ugly and constant problem causing NT4Emulator value on your PDCe

-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there

 

[tangostar]

The who the what?

It's a clean, not upgraded version of 2000 in mixed mode.

 

[Seaspray0]

When I asked what type of records you have in WINS I was refering to Domain [1C] records. You're not going to find the DC without them for NT boxes that don't use DNS.

Reference Windows Help "Locating domain controllers using NetBIOS over TCP/IP (NetBT)"


For environments with domains running Windows NT Server 4.0 and earlier versions, the process of locating domain controllers involves the resolution of the <domain> [1C] name. This name is registered for use by the domain controllers within each domain and can contain up to 25 IP addresses.

The first IP address is always for the primary domain controller (PDC). The additional (up to 24) IP addresses are for backup domain controllers (BDCs). Because this name is treated as a domain group by WINS, each member of the group (a domain controller) must renew its name individually in WINS, or its IP address entry in the list is released and can be eventually overwritten.

Each time a domain controller starts, it registers its <domain>[1Ch] name. This record can then be updated dynamically in the WINS database and replicated to other WINS servers located throughout the network.



A+/MCP/MCSE/MCDBA