NT 4.0 and moving domain controller issues

[tpulley]

Recently my company moved an NT 4.0 PDC from site A to site B. There were users that connected to it in site B & C. Now users can connect in site B but not in site B. I changed the WINS server to reflect the new IP. I also created hosts and lmhosts files on the local machines in site C. They can ping by name ping serverpdc and get a reply. They cannot however ping by UNC name ping \\serverpdc . Unknown hosts. When I try and map a drive to the a share on the server, I get no logon server found.

All sites are in different domains. There is another site (D) that is housing the WINS for site C. I added a static entry to that WINS server. I pointed my serverpdc to that as one of the WINS servers (P) and the one at site B for the other (S). Any Ideas????

Thanks In advance.

 

[robtan]

You might need to revise your question. There are soemthings I don't understand like "Now users can connect in site B but not in site B."?

You say you are moving a NT PDC from site A to site B, and that all sites are in different domains. Can you give more details of the overall NT infrastructure you have? ie, Single Master Domain etc. Sounds like multiple master domain, in which case, how did you have it mapped out? Each site has it's own domain?

 

[tpulley]

Let me revise...

Site A, NC has two domains currently. Domain A and Domain B both of these reside in the NC office. Domain A was in Ill. This was moved recently. Domain C in Mx connects to local resources as well as resources on Domain A. Domain D (NY) is the master of the MX domain (C) Domain B is master of Domain A. I want to get users in Mx to attach to the resource in Domain A. There are two wins servers in this world. One in NY and one in NC. I pointed users in Mx to the WINS server in NC (they were pointed to NY) to no avail. I created an LMhosts file that indicated the server (serverdoc) new IP address. Users can ping the serverdoc by name. They cannot however map a drive to it. Upon trying they get a Logon server is not available. I can ping it all day just cannot connect to the share that they need. Of course browsing doesn't work to it either. There is a VPN tunnel connecting all users in a meshed network.

Make better sense?

 

[robtan]

The Logon server message not found, seems to indicate a credentials problem of some kind. Are users in Domain C authenticating properly? Are they perhaps logging into cached profiles?

You might need to re-establish the Trust relationships that involves A and C.

I presume that trying to map a drive using IP doesn't work either?

Can users from other domains (B & D) access the same share in A? Can users from C access anything else in other domains?

 

[tpulley]

There was a left over LMhost file on the Domain Controller. It had a now bogus IP address. I correced this and wella.... Things started working as they should.

Thanks for the input.