Windows 2003 Domain Can't See my NT 4.0 Domain Server

[mcsoadmin]

I'm hoping someone here has some insight on this issue. I am a network administrator over a 27 PC network, with a Windows 2003 Server (just installed in July) and an NT 4.0 Server which must remain due to software requirements. Prior to installed the 2003 Server, 23 had a NT 4.0 server there and both Servers could see and communicate with each other. After a lot of nerve racking and changing settings, to try to make both servers (2003 & NT 4.0) talk to each other, we were finally able to make NT 4.0 see 2003 Server, but the reverse is not true. Now, apparently, one of the changes made has made browsing network neighborhood impossible. Always get an error stating "Unable to Browse" and then the Workgroup name. I understand that there are apparently some issues with NT 4.0 and 2003, but have no idea where to begin to correct them. Have been unable to find information relating to this issue. By the way, NT 4.0 machine is running service pack 6. Please Help me as I need to browse network neighborhood again and be able to communicate with both systems. If I ping the IP address, I can communicate. If I use the net use command, I can map a drive letter that way, but unable to resolve name through DNS. I'm totally new to 2003 so, any assistance would be greatly appreciated. Thanks.

Network Admin at a Loss!!!!!

 

[DougP]

As one 2003 newbie to another
See if you can create a user on 2003 and then log onto it from an XP client. My XP client sees both domains.
this is not th ebest way but you wil see if you can log on to the new server at all

Also what roles did you setup on the new server?
Domain controller, DNS server ????


DougP, MCP

 

[EdwinSKH]

Does this article help?

http://support.microsoft.com/default.aspx?scid=kb;en-us;811497

You could try reapplying NT service pack 6a.

 

[mcsoadmin]

I am not the one that set up our Windows 2003 server. We purchased the PC from a local vendor who installed the operating system. The 2003 computer is a domain controller and the NT 4.0 computer was a BDC. It is now in it's own domain.

By the way, I didn't include that I can ping either server from the other. I can also connect directly to the computer by using the IP address but not the Computer Name.

Edwin.... thanks for the information you posted. I'll have to try and see if that might fix the problem and will let you know.

Network Admin at a loss!!

 

[gcdhnjgfhfgsxh]

Hi

If you havent installed the OS i would seriously consider reinstalling it. Vendors have a habbit of using short cuts to install operating systems, this cuts costs and time for them however from my experience can cause headachs for system admins. Microsoft have developed setup programs for operating systems for a reason - Thats how they should be installed and thats what they support. Vendors often use programs such as notron ghost to image the disks, rather than taking 1 or 2 hours to install an os properly that do it once and copy images which takes about 20 minutes. Also if you do the install yourself you get to see exactly what you are installing and any errors that may occur. This will in the long run prove better rather than relying on an outsider to do an install that u dont see

Regards



Dave

http://affy.dynu.net

 

[EdwinSKH]

If your NT Server and 2003 are in 2 different domains, then it may be just setting up trust relations between the 2 domains in the Active Directory Domains and Trusts. Also, make sure the 2003 is pointing to an internal DNS, with Dynamic updates allowed, preferably setup in the 2003 server itself.

http://support.microsoft.com/default.aspx?scid=kb;en-us;816301

 

[sigeo]

If it still matters, probably the qicker and less painful way to fix the problem is to demote your 2003 server to a stand alone server and be sure to check "mixed mode". Go into "Control Panel" then "Administrative Tools" then edit your security policies, both Domain and Domain Controler. Be sure passwords and sucrity match what what you have on your NT server. Reboot, go to into "Control Panel" then "System" then "Computer Name" and click "Change" type in Work Group or Domain name, whichever you are using, apply settings, if it says welcome to the Domain or Workgroup,it was sucessful. REBOOT. Set your users and shares on server 2003.