Windows Forum

Ask something
Discussion Locked

Win Xp Pro and NT 4.0 Domain

0 helpful
8 replies

by dread_aus 1 view

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

Okay here's what I've got: A client with the following setup

1 State Office with WinNt4.0 sp6a PDC, 1 NT 4.0 sp6a BDC (DNS, Wins), 1 Nt4.0 Proxy Server plus some other no relevant servers (eg Citrix) Cisco 3640 Router

ISDN lines to each Office

3 Branch Offices each with an NT 4.0 Server BDC and a number of workstations and Cisco 1720 Router. 2 Of the branches have older Win95/98 boxes and 1 Win2k Pro Box, the newer branch has all Win Xp Pro Boxes. Now the older Win98/95 Boxes logg perfectly fine into the local BDC and get their login script from there OK. However the Win2k and all the Win XP boxes bypass the local BDC and log directly into the PDC, therefore getting the incorrect login script. I have created a new login script on the PDC for that office to map their local drives etc as a workaround but what we are finding is that at the XP site the local area network is VERY slow. They hold all their data on the local server and even opening files on it can take quite a long time. Is there a solution for this ?? Any help would be appreciated

8 replies

by joseph moore

You could modify the LMHOSTS file on the Win2K and WinXP boxes, pointing the NT4 domain to the local BDC you want these machines to authenticate from.
You would put 2 records in the LMHOSTS file.
Say the local BDC you want the Win2K & WinXP machines to use is called REMOTEBDC and has an IP of 10.1.1.2
Also say that REMOTEBDC is a BDC of the NT4 domain called MYDOMAIN. Your 2 LMHOSTS file records would look like this:

10.1.1.2 REMOTEBDC #PRE #DOM:DOMAIN
10.1.1.2 "MYDOMAIN \0x1b"#PRE

Just put these 2 records in the LMHOSTS file on the machines, then open a Command Prompt and type in:

nbtstat -R

to purge and reload the NetBIOS name cache.
Then you can reboot the Win2K and/or WinXP boxes, and it should do what you want.

Please read Technet article "How to Write an LMHOSTS File for Domain Validation and Other Name Resolution Issues (Q180094)" for a clarification on the LMHOSTS file and its usage:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q180094
(please remove any spaces)

hope this helps

by dread_aus

Woops forgot to come back to this one, sorry, nope found the solution another way, thanks for the help though!

by dread_aus

Woops forgot to come back to this one, sorry, nope found the solution another way, thanks for the help though!

by gperrie

If you have WINS/DNS I would have thought you wouldn't need lmhost files.

Do the remote servers also have WINS/DNS or is all name resolution done on the central site? Maybe look at adding WINS to the remote BDCs and configuring them to replicate. What about DNS as well?

Gavin

by dread_aus

Done this already :) That was my first thought. One of the Servers at State Office is the Wins/DNS Server, so at the XP site I set it up to be a WINS/DNS Server as well and configured replication. This didn't help at all :(

by hjs

Try putting the IP address of you DNS server in the XP TCP/IP settings. I know this sounds goofy but it has worked for me.

by dread_aus

Woops forgot to come back to this one, sorry, nope found the solution another way, thanks for the help though!

This discussion is closed to new replies.