We added two windows 2008 server to windows 2000 domain as domain controllers with DNS servers. All LAN servers and client use the 2008 DNS without any issues. The 2008 DNS doesn't have any errors logged in the Event Viewer.
The only problem we are facing is the Exchange front-end server running OWA. The server is located in our DMZ and there is a Cisco firewall. This server used to use 2000 DC DNS servers which are 10.0.0.29 and 10.0.0.19. When we changed the DNS point to the 2008 DNS servers which are 10.0.0.17 and 10.0.0.18, it asked to reboot (this is only server asks to reboot and all other servers don't ask reboot when changing the DNS server). Since this is production server, we schedule to reboot it next morning. When I logon next day, the logon process took long time. After logon, I can ping the 2008 DNS server and run port query to check domain and trust port. They look good.
This morning, my technician rebooted it again. This time, we can't logon any more. It stays "Apply Computer Settings" for ever. Then we did warm reboot, and run safe mode with network. I can access the both 2000 and 2008 DC and DNS without any problems and other computer can remote access it. We also try to re-set the DNS back to the original 2000 DNS. That doesn't make any difference. The server is running, we access the OWA and receive the email. I can access the server's Computer Manager from other computer too. The Event Viewer doesn't show ant related errors. Also we can't access it using remote desktop. The server just stay "Apply Computer settings".
We don't have APC Agent service. Any suggestions?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Also, from the exchange-owa box, do a test of DNS resolution:
click start > go to run > enter "cmd.exe"
enter "nslookup.exe"
type "server 10.0.0.17" at the "nslookup" prompt
type "set type=a"
enter "DNS-NAME.OF-SOMETHING.INY
and post your results here.
"DNS-NAME.OF-SOMETHING.INY
sorry for double post, i realized after i posted that i didn't include any DNS troubleshooting info.
Hi dpiniella,
Thank you for all inputs.
1. "it sounds like domain auth is not working properly and you're only getting in on cached credentials". I thought that too. So I have tried to logon the local computer instead of domain. It is the same problem. Also The Apply Computer Settings shows before logon screen for a coup hours and then logon screen comes. When logon using the local administrator account, it stays apply computer settigns for ever.
2. I will open all ports for the test and will post back.
3. I can't nslookup right now because I can't logon local or remote. I may try that this weekend.
I fixed it. It is simple. Just reset network cable. More details can be found this search result.
Troubleshooting Applying Computer ...Troubleshooting Applying Computer Settings ... Posted: Thu Sep 11, 2008 2:50 pm Post subject: Troubleshooting Applying Computer Settings, Reply with quote ...
www.chicagotech.net/netfor
Business Accounts
Answer for Membership
by: dpiniellaPosted on 2008-09-12 at 05:49:22ID: 22459186
At a guess, it sounds like domain auth is not working properly and you're only getting in on cached credentials, not actually authenticating against the domain.
What are the firewall rules on the cisco to isolate your DMZ machines? Specifically look for the ports that 2008 needs to do Domain auth (they may have changed from 2000) and make sure that they are not blocked.
As a test, change the FW rules from the exchange-owa box to (and from) the DC and DNS to be open for any port/protocol and try logging on. If this works, you've got a port access problem and need to find out what ports EX-OWA is trying to use (a sniffer on the network or netstat on the box will help with this).