HELP ASAP - Connecting to server and Outlook which is on a different server

The problem is that if I make all workstation first DNS go to DHCP server then everyone can logon but then their outlook takes forever to open. Every workstation gets their IP address automatically.

The DHCP server which is also a DC where users authenticate to is a windows 2000 server and then two DNS they get on their workstation is the 192.168.100.40 and also 192.168.100.48

Now if the first DNS that all workstation get is 192.168.100.40 then the machines login without much delay. But then outlook does not work right away and take almost 20 minutes to connect to the exchange server which is on a separate DC which is a windows 2003 server and its IP address is 192.168.100.48

If I change the DNS order that each workstation gets to 192.168.100.48 then each machine takes 20 minutes to login but outlook works great.

We have been running these server without any issues for almost three years. But all of a sudden after we got new DNS numbers from ISP and adding them to the DNS server on the 192.168.100.40 has caused issues.

Can anyone help. Microsoft has no solution and they are still researching. They had me change the order but then no one can login and it takes forever.
gorhamoienAsked:
Who is Participating?
 
CetusMODCommented:
PAQed with points refunded (500)

CetusMOD
Community Support Moderator
0
 
Netman66Commented:
Which DNS server was installed?
0
 
Netman66Commented:
Oh, man....

Which DNS server was installed first! ?

Sorry..
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
gorhamoienAuthor Commented:
Well all server have the DNS server installed. It was installed three years ago. The first was the 192.168.100.40 and then last year was 192.168.100.48 one. This problem arized when ISP changed the DNS numbers and I added those DNS numbers in the DNS server forwarders.
0
 
Netman66Commented:
OK, is .40 Windows 2000?

I think this problem is due to the _msdcs zone, but want to confirm a few things.

Are both DCs set as GCs?

0
 
gorhamoienAuthor Commented:
.40 is windows 2000 sever
.48 is exchange server with windows 2003

Yes both are DC's and set as GC's and have DNS servers running

Each workstation gets their IP address from .40 server
Workstations can ping the exhcange server name mail and it resolves to the internal IP address. However if they were to ping the entire name which is exchange.domainname.com then it resolves to the public IP address. How can I make it ping to the internal IP address. In that way I can keep the .40 as the first DNS and .48 as secondary. In this way outlook will also open without any issue.
0
 
Netman66Commented:
Manually change the entry - but I'm not sure how long that will last.

You may be able to uncheck the "register in DNS" checkbox on the NIC then make sure all the entries are in DNS.  As long a Scavenging is not enabled they should stay put.

So, we've confirmed that 2000 was the first DNS server.  On the 2003 DNS server, where is the _msdcs zone?  It *should* be inside the domain zone.  If it isn't we have the problem.

0
 
gorhamoienAuthor Commented:
On each workstation??? What do you mean??? Yes msdc is inside the domain zone. It was always there and nothing has changed there.
0
 
Netman66Commented:
No, not on every workstation.  I am referring to the NIC on the server that has all the IP addresses assigned to it.

0
 
gorhamoienAuthor Commented:
Thank you all for responding. After lot of thinking I finally figured out and I am surprised that even Microsoft could not be of much help. Since I have two separate domain server each havings its own farm each DNS server should have identical information and should include the zones from each server such that no matter which DNS server it can resolve from either. Once I created both servers zones on both server it was working like a charm.

Nothing to do with forward DNS, DHCP releasing which IP addresses, NIC card on the server etc. Those were all fine. One can only replicate each other DNS if they belong to the same domain and trusted. With separate domains and no trust between domains it is better to add other server zones. I am really surprised that it has worked well over the last three years like that.
0
 
Netman66Commented:
So we were supposed to GUESS that these 2 servers were in different domains?

The quality of the answers you get is directly related to the information you provide us with.

At least it's fixed.
0
 
gorhamoienAuthor Commented:
I did mention both are domain controllers. One being a windows 2000 and one being a 2003 server. However, it was never asked if there was any trust between the two. Yes it was my mistake not mentioning it. However, I am surprised that Microsoft having control of both the server remotely could not see that. I am just glad it is fixed now. I also told them what the problem is and all I wanted them to figure out why when i ping the exchange.domain.com it does not ping to the internal IP verses looking at public IP.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.