win 7 64-bit can't resolve or connect exchange 2003
Using a fresh install of the Win7-64 RC at work and everything works great except Outlook 2007. At first, I thought it was just an Office issue so I tried re-installing and that didn't work, then I tried pinging the exchange server and it keeps timing out. Our exchange server is still exchange 2003 running on server 2003 R2. We have a dozen or so servers all running the same set up, sans exchange, and I can ping and connect to all of them, except the exchange server (also vnc/rdc doesn't work). I also have no problem connecting and getting my mailbox on my secondary machine. I also tried pinging directly to the ip-address of the server, to make sure it wasn't a DNS issue, and that didn't work either. Any help would be appreciated thanks. I'm thinking that it's a win7 64bit -> server 2003 32bit issue, but that makes zero sense in terms of networking and the fact that there are other servers with the same OS setup I have no problem pinging.
July 9th, 2009 5:53pm

There is no known issue with Windows 7 64-bit RC and Exchange Server 2003. I have this setup running here without issues.Can you locate the Exchange Server in DNS using nslookup?Is the server on a different subnet? Can you reach that subnet from the Windows 7 client?Did you block outgoing traffic in Windows firewall?Ray
Free Windows Admin Tool Kit Click here and download it now
July 10th, 2009 1:31pm

There is no known issue with Windows 7 64-bit RC and Exchange Server 2003. I have this setup running here without issues.Can you locate the Exchange Server in DNS using nslookup?Is the server on a different subnet? Can you reach that subnet from the Windows 7 client?Did you block outgoing traffic in Windows firewall?Ray
July 10th, 2009 1:31pm

Ray, I can reach the subnet from Win7. (all our internal servers are on the 10.0.10.x range, including exchange). I can ping any server. I have Windows Firewall disabled when I'm on our domain, because I'm behind a beefy Cisco PIX. And no, Nslookup can not find the exchange server, nor can ping. But I can't ping the 10.0.10.x address directly either. Or VNC into it. It's very odd, that it's just this one server...
Free Windows Admin Tool Kit Click here and download it now
July 10th, 2009 5:04pm

patmcd - Did you ever get an answer on this? I have been experiencing the same issue with Vista-64 Enterprise SP2. I can't find anything wrong on the network, had to add a route to win Vista-64 machine to find the server (which I know is wrong) but I needed connectivity in a hurry. Just wondering if you ran across a resolution for this issue. Thanks
August 25th, 2009 10:11pm

I have the same issue with Outlook 2003 on Win 7 64-bit. I connect to the domain and get to the shared drives fine.When I setup my Outlook, I can give it my server name, and it will resolve the user, but then it fails to connect. Is there a Patch to Exchange 2003?
Free Windows Admin Tool Kit Click here and download it now
October 26th, 2009 8:03pm

I'm having a similar issue. I recently installed Windows 7 on 2 production machines at home. I did clean installs on both - 32 bit on a HP laptop & 64 bit on a self built box with a new mobo & AMD Phenom II X3. Both machines had the RC installed & running well. I installed Office 2003 on both. I was able to configure the laptop to log in to our Exchange Server at work (which recently was upgraded to 2007 - what fun...) via Cached Exchange Mode. However, I could not get the 64 bit machine to log in. Today (Thanksgiving) I installed the 64 bit public beta of Office 2010 Professional Plus. I had to uninstall Office 2003 first. Outlook 2010 can't resolve the Exchange Server either. Our IT folks don't have much Win 7 experince but I will ask them about this Monday. I thought I would add to this thread.
November 27th, 2009 1:52am

did u find a solution??? i have the same problem:(
Free Windows Admin Tool Kit Click here and download it now
January 17th, 2010 11:05am

Try taking out the “\\” in the server name. That is what prevented mine from connecting. Just put in the server name, or “SERVERNAME.DOMAIN.EXT”. No quotes.
March 11th, 2011 3:08pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics