Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 203
  • Last Modified:

problems w/ migrated xp's in new 2003 domain.

we just migrated from a 2000 domain to a 2003sbs domain. the 2 servers were put on the same network with different domain names. ie brame.local and bramearchitects.lan. at the time i was setting up the server i did not know that the netbios name for the domains were the same (brame). we had an awful time getting the computers to join the domain, but we did get all of them joined finally. this is an environment with 2000 and xp machines. after removing the old dc, all of the 2000 machines are happy, but the xp's take about 3-5 min to log in. i know this is a dns issue. i have hard coded in the tcp/ip properties of the workstations the dns for the new dc. i have dhcp running from server handing out the ip for dns to server also. in dns on new server i have created a forward lookup zone called brame, which is in addition to the one created automatically during ad setup. the reverse lookup zone has also been created. i think my problem lies in the dns zone that was created automatically. all workstations look to dc which forwards to isp dns. can i kill the auto created zone (it is the mcdcs zone) and just use the forward lookup zone that i created without major reprocussions?? also this environment was using microsoft mail which is now exchange 2k3 (patched up) for internal and pop3 for external. the 2k machines can send/receive internally no problem. the xp's cannot. they can open their mailboxes fine, but if they try to send a message from global address list it gets sent to pop3 smtp which kicks it back.  out bound mail is disabled on the exchange.  any help would be appreciated......thanks
0
vrsII
Asked:
vrsII
  • 2
1 Solution
 
vrsIIAuthor Commented:
i have already put an a record with pointer record in both dns forward lookup zones for the server. i have done the ipconfig /flushdns and the / registerdns on the xp machines also.
0
 
jamesreddyCommented:
You've stumbled upon one of the many wonders of XP...logon issues.  Ok...there are MANY things you can check.  This thread outlines most of the main ones:

http://www.experts-exchange.com/Networking/WinNT_Networking/Q_20738101.html

If none of that works...come back and let us know.

James
0
 
vrsIIAuthor Commented:
here is te fix:  i did an nslookup on the xp machine and it was looking to wrong dns even though i hard coded the ip in tcp/ip properties. it turns out my pointer record was wrong. i deleted all of the a record and pointer records that i had created. also i had set up the server in my shop with a different ip than what we were using on site ( 192.168.1.21 vs. 192.168.1.2)and apparently when you change the ip of the server it DOES NOT get updated everywhere in dns. where the problem was was in the name server tab of the properties of the dns server. it was showing the server name with an " unknown" ip address. apparently it couldn't figure out what it's own ip was. as soon as i edited the ip address of the nameserver with the correct ip everything started working fine. xp's were logging in like they should and the nslookup was reporting the orrect dns name of the server. sooooooo... in short, if xp's are logging in slow, do a nslookup and if it is not what it should be, check the name servers tab in the properties of the  dns server in the dns mmc snap in. thanks for the help.....rick
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now