kingsc

So I cheated and added a host record to _mcdcs for "de67edef-eceb-4b03-a449-15b7f915044b" The check now passes, but I get the following warning: Testing server: Default-First-Site-Name\SRV-1 Starting test: Connectivity *** Warning: could not confirm the identity of this server in the directory versus the names returned by DNS servers. If there are problems accessing this directory server then you may need to check that this server is correctly registered with DNS ......................... SRV-1 passed test Connectivity

Wierd, I don't see the attachment there, anyone see it? I included the image here in case it didn't attach properly.

Awesome response and very informative, thank you! This is the history with our DNS server: The DNS server is also our AD server. I told the guy who was setting it up to not start the AD installation process until the next day because he wasn't going to have time to finish it. Well he did it anyway, and in a rush, after the AD was done installing, the DNS part came up and he cancelled it. So after some work, we had dns problems of course, so he removed the role and re-added it. We tried creating a primary lookup zone for table1.com afterward, but it was already there I guess since that's what the error at the end of the procedure told us. I won't be able to look at it again until Monday(I think) unfortunately, but I'll update as soon as I do and hopefully be able to provide some screenshots! Ok I have no idea what I'm doing here but while I'm trying to work this out, I thought I'd attach a pic of what the DNS structure looks like. ALso, we did verify we can get out to the internet from computers that list only our DNS server for their DNS server.

Awesome response and very informative, thank you! This is the history with our DNS server: The DNS server is also our AD server. I told the guy who was setting it up to not start the AD installation process until the next day because he wasn't going to have time to finish it. Well he did it anyway, and in a rush, after the AD was done installing, the DNS part came up and he cancelled it. So after some work, we had dns problems of course, so he removed the role and re-added it. We tried creating a primary lookup zone for table1.com afterward, but it was already there I guess since that's what the error at the end of the procedure told us. I won't be able to look at it again until Monday(I think) unfortunately, but I'll update as soon as I do and hopefully be able to provide some screenshots!

Ah, hi there cluberti, I don't think I've talked with you since back when I was trying to put together my universal image. What you're saying makes sense to me, and I did check the _mcds tree, but I don't know what I'm doing unfortunately. I have two trees, the _msdcs one and a table1.com one. I'll post screenshots later, but in the table1.com tree, IIRC, there is an A record for both SRV-1 and SRV-2(The computer I'm running DCDiag from, that I'll be installing exchange on). Also, IIRC, the _msdcs tree is empty, which maybe explains why I'm getting that error? But if that's the case, why is it trying to utilize that tree when both SRV-1 and 2 are in the table1.com domain? I'll utilize the hyperlink you gave me and see what I can find. Thanks.

Hi all, new to this topic and trying to setup Exchange 2003 on a Windows Server 2003. The DNS server is a seperate server running Windows Server 2008. This is what I get back when running DCDIAG using the "/s:SRV-1" flag: Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\SRV-1 Starting test: Connectivity The host de67edef-eceb-4b03-a449-15b7f915044b._msdcs.table1.com could not be resolved to an IP address. Check the DNS server, DHCP, server name, etc Although the Guid DNS name (de67edef-eceb-4b03-a449-15b7f915044b._msdcs.table1.com) couldn't be resolved, the server name (srv-1.table1.com) resolved to the IP address (192.168.10.130) and was pingable. Check that the IP address is registered correctly with the DNS server. ......................... SRV-1 failed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\SRV-1 Skipping all tests, because server SRV-1 is not responding to directory service requests Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : table1 Starting test: CrossRefValidation ......................... table1 passed test CrossRefValidation Starting test: CheckSDRefDom ......................... table1 passed test CheckSDRefDom Running enterprise tests on : table1.com Starting test: Intersite ......................... table1.com passed test Intersite Starting test: FsmoCheck ......................... table1.com passed test FsmoCheck I need this check to pass before I can continue installing Exchange. Like I said I'm new to this so I'm sure it's something simple related to the DNS server. Can anyone help?

Ok so I tried disabling outlook addins to no effect, recreating the profile a second time, ran SFC, and re-installed office. All to no effect..... and she's the only user this is happening to.....

The problem with those are that they sit in the background eating up resources while they aren't being used, and requires the indexing service to be enabled which is not. Also, that won't alleviate the now somewhat new issue that its' even freezing sporadically when navigating folders. Now, I know that means she has too much stuff. I'm well aware. Problem is she works in accounts payable and she needs ALL of them. On top of that, there is another user in her department that has all the same mailboxes that she does, plus a couple more and no problem....... frustrating. EDIT - Updating everyone and myself.... What I've done: * Rebuilt profile * Checked for google desktop and windows desktop search * Made sure indexing was disabled in services.msc. * Office Diagnostics * Run Contig on OSTs/PSTs What I haven't done: * Re-installed Office * Re-imaged machine * Disable OutlookAddin * Run sfc /scanonce * Anything else I haven't though of.

WRONG. SHe's STILL having the issue!!!

We've had this deployed for months, no problems.

Nevermind.. think I may have fixed it. I have a batch file that runs as a runonce when a new profile is created, I just added two registry keys via REG ADD to modify the EnableAutoDial and GlobalUserOffline values to return them to their normal starting values. Thanks anyways.

Quick problem I'm trying to tackle in an image. I set up a PPTP VPN connection in an image so that we wouldn't have to configure it anymore for users. If I create a local test user, everything works correctly. However, after attaching the computer to the domain, and signing in with any user, when I open IE the Dial a connection window pops up. This is easily fixed afterwards but annoying and the point of the image is to not have to deal with it. I'm doing some testing on my own but has anyone in a business environment experienced a similar issue that can provide some advice?

Figured it out. We actually had 3 users with the problem, and 1 of them was on XP. Pinned it down to a directory service issue on the exchange server. The Sys Admin said everything looked good but restarting the server services resolved it. Thank god!

So I may have a clue...... There's definitely a communication problem here. When clicking the "To:" button, the "cannot contact exchange server" message pops up. If I take the account off cached mode Outlook doesn't connect at all.

Looks like installing WDS and the user archiving old items fixed the issue.