Windows 7 64-bit cannot ping or connect to Exchange server
Hi Everyone, I've run into a bizarre problem. I'm rolling out my first Windows 7 x64 engineering workstations this week, and they cannot connect to my Exchange 2007 server. 32-bit Windows 7 works just fine. The server name and domain resolve correctly, but Outlook 2007, OWA and even ping do not work. Here are the details: Exchange Server 2007 (v8.1 Build 240.6) Windows Server 2003 R2 SP2 x64 as a Hyper-V guest Hyper-V host on Windows Server 2008 SP2 x64 Exchange Server has Hub, Store and Access roles ISA Server 2006 lives at the edge, in the DMZ of our hardware firewall Windows 7 x64 client, all current updates Office 2007 SP2 x86, all current updates The server's name is elvis, our AD domain is swfab.local Here's the problem: The x64 clients cannot connect to the Exchange server. Not with Outlook, not with OWA, not even PING or NSLOOKUP. When you ping the Exchange server from an x64 client ("ping elvis") the domain and server address will resolve correctly, but no ping replies occur. However that same x64 client can ping any other server and our two DCs. Outlook 2007 will read the user name and server name correctly during auto-setup, but will fail to connect to the Exchange server. OWA fails to connect from IE x64 and IE x86. The Exchange server has no Windows Firewall running. I've tried Windows Firewall on and off on the x64 clients. I initially thought it might be 32-bit Outlook, but then realized that I cannot even ping the server. So the problem is much more basic. Does anyone have any ideas? Thanks very much! John Sage Here's the relevant ipconfig and ping results: Ping Results ============= Ping the Exchange server: Pinging elvis.swfab.local [192.168.203.11] with 32 bytes of data: Reply from 192.168.203.105: Destination host unreachable. Reply from 192.168.203.105: Destination host unreachable. Reply from 192.168.203.105: Destination host unreachable. Reply from 192.168.203.105: Destination host unreachable. Ping the first DC: Pinging cal.swfab.local [192.168.203.2] with 32 bytes of data: Reply from 192.168.203.2: bytes=32 time<1ms TTL=128 Reply from 192.168.203.2: bytes=32 time<1ms TTL=128 Reply from 192.168.203.2: bytes=32 time<1ms TTL=128 Reply from 192.168.203.2: bytes=32 time<1ms TTL=128 Ping the second DC: Pinging gus.swfab.local [192.168.203.5] with 32 bytes of data: Reply from 192.168.203.5: bytes=32 time<1ms TTL=128 Reply from 192.168.203.5: bytes=32 time<1ms TTL=128 Reply from 192.168.203.5: bytes=32 time<1ms TTL=128 Reply from 192.168.203.5: bytes=32 time<1ms TTL=128 IPCONFIG /all Results ====================== Windows IP Configuration (Windows 7 x64 workstation) Host Name . . . . . . . . . . . . : 100101A Primary Dns Suffix . . . . . . . : swfab.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : swfab.local Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20) Physical Address. . . . . . . . . : 40-61-86-2A-AC-86 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::d892:c2d1:7da4:48bd%12(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.203.105(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Friday, January 15, 2010 5:47:51 AM Lease Expires . . . . . . . . . . : Monday, January 18, 2010 9:47:50 PM Default Gateway . . . . . . . . . : 192.168.203.254 DHCP Server . . . . . . . . . . . : 192.168.203.2 DHCPv6 IAID . . . . . . . . . . . : 255877510 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-D0-27-82-40-61-86-2A-AC-86 DNS Servers . . . . . . . . . . . : 192.168.203.2 192.168.203.5 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{2E658823-2965-4F1F-8A4E-C9D0B831CBC2}: Media State . . . . . . . . . . . : Media disconnected Tunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Windows IP Configuration (Windows Server 2003R2 x64, Exchange 2007) Host Name . . . . . . . . . . . . : elvis Primary Dns Suffix . . . . . . . : swfab.local Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : swfab.local Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter Physical Address. . . . . . . . . : 00-15-5D-CB-24-01 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.203.11 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.203.254 DNS Servers . . . . . . . . . . . : 192.168.203.2 192.168.203.5 Windows IP Configuration (Windows Server 2003R2 x86, DC DNS DHCP) Host Name . . . . . . . . . . . . : cal Primary Dns Suffix . . . . . . . : swfab.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : swfab.local Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter Physical Address. . . . . . . . . : 00-50-56-A4-1C-03 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.203.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.203.254 DNS Servers . . . . . . . . . . . : 192.168.203.2 192.168.203.5 Windows IP Configuration (Windows Server 2003R2 x86, DC DNS) Host Name . . . . . . . . . . . . : gus Primary Dns Suffix . . . . . . . : swfab.local Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : swfab.local Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter Physical Address. . . . . . . . . : 00-15-5D-CB-21-0D DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.203.5 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.203.254 DNS Servers . . . . . . . . . . . : 192.168.203.2 192.168.203.5
January 18th, 2010 4:10pm

Have you turned off the firewall and set the UAC to none? Also be sure to turn off all security software (temporarily) to see if this is the issue. I am running half a dozen win7 pro 64bit on a 2003 domain with no issue so sorry cant be much more help.
Free Windows Admin Tool Kit Click here and download it now
January 18th, 2010 4:46pm

Keith, Thanks for the quick suggestion. Yes, I've tried turning Windows Firewall off, no joy. UAC is not the issue, for two reasons: I don't need elevated privileges to ping, and I can ping every other server on the network. My thinking is that there's something about Exchange 2007 on 2003R2 x64 that doesn't like packets from Windows 7 x64. When that is figured out, I believe Outlook and OWA will begin working. So once I can ping successfully then I can move on to determining if there is a further problem. Have a great afternoon, John
January 18th, 2010 6:03pm

Hi John, Based on my research, I would like to suggest the following: 1. Please check if you can ping this Windows 7 64bit computer from your exchange server. 2. Ensure all the NICs on the client sides and server sides are up-to-date. 3. Check if there are any differences between the Windows 7 64bit and Windows 732bit clients. Thanks. Nicholas Li - MSFT
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2010 5:06am

1. Please check if you can ping this Windows 7 64bit computer from your exchange server. 2. Ensure all the NICs on the client sides and server sides are up-to-date. 3. Check if there are any differences between the Windows 7 64bit and Windows 732bit clients. Hi Nicholas, Thanks for your reply. I cannot ping the Windows 7 x64 client from the Exchange 2007 x64 server. However I can successfully ping the Windows 7 x64 client from any other Windows XP x86 client, Windows 7 x86 client, Windows Server 2008 x86 and x64, and Windows 2003 Server x86 and x64. And the Hyper-V host (Server 2008 x64) that the Exchange server lives on can ping the client. The network drivers are current on the client and on the Exchange server. The Windows 7 x86 clients connect to the Exchange server and can ping it without any issues. Both the x86 and x64 clients are domain members. The x64 client can ping any other device on the network that will answer a ping, it is seen in AD, and it can print and it can access file shares on other servers. Just the Exchange server is "invisible" to it (and vice-versa). Have a great evening, John
January 28th, 2010 7:48pm

JohnI am having a similar issue. On each host, can you verify whether or not ARP is correctly resolving the MAC address of the destination host?ARP -a will show you the ARP table. If ARP is working, the IP address will show up next to the MAC address of the NIC assigned that address. If not, it will show up all 00's
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2010 6:03pm

hi jhon.. i facing same problem. if u have find solution plz send me.
May 18th, 2010 8:05am

hi ukcats,,, i facing same problem ,,i try all things but no solution if u have find solution send me.
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2010 8:06am

Hi John Sage, Pls advise if you managed to find a fix for Windows 7 x64 client from accessing Exchange 2007 x64 server. If yes, Pls kindly guide us on this as we are having similar issue in our network. Regards SS_KANU
July 16th, 2010 8:18am

I too am waiting to see what the issue might be. We are having an issue with a Windows 2008 x86 GHOST Server and local clients. The network will be there then go on the fritz with the DESTINATION HOST UNREACHABLE when pinging along with no computers viewable in the Network. Is becoming quite frustrating.
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2010 5:14pm

For what it's worth, at this client, the issue was an oddly configured NAT entry on one of their firewall DMZs. It had nothing to do with Microsoft. Seriously, look closely at the ARP cache on the client and the server. Sometimes the HEX characters blur together :) We've got dozens of makes and models of Windows 7 machines talking to Windows Server 2008 - every issue has been one of network or client side software config...
July 19th, 2010 5:19pm

OK, I figured it out, at least on our system and I hope it works for everyone else. Control Panel...Network and Internet...Network and Sharing Center...Advanced sharing settings...Under Domain in File Sharing Connections change from 128bit to 40-56bit encryption. Once I did that, Exchange worked perfectly and was able to connect.
Free Windows Admin Tool Kit Click here and download it now
August 31st, 2010 9:44am

Also check your domain policies for access rights! Try these items below also! They adversely effect other applications but fixes most connectivity problems! But I don't recommend these setting changes if you are connected directly to the internet with no firewall in place.... Click on the Start button and type SECPOL.MSC in the search function. Browse to "Local Policies" -> "Security Options". Now Look for the Entry "Network Security: Lan Manager Authentication Level" and open it. Click on the dropdown menu and select "Send LM & NTLM - use NTLMv2 session security if negotiated". Aplly the Settings. In the advanced Sharing settings of Network and Sharing center, you need to have it set as Work/Home Profile. Now Try It! Please check these related Policy items also! Enter the "GPEDIT.MSC" in the start search function box. Open the "Computer Configuration" goto "Windows Settings" then to "Security Settings" followed by the "Local Policies" and then "Security Settings". In the right pane window, "Enable" the following Policies: Network Access: Allow Anonymous SID/Name translation Network Access: Let Everyone Permissions aplly to anonymous users Also, Please Disable the Following Policies: Network Access: Restrict anonymous access to Named Pipes and Shares Network Access: Do Not Allow Anonymous Enumeration of Sam Accounts Network Access: Do Not Allow Anonymous Enumeration of Sam Accounts and SharesBILL
December 30th, 2010 12:49pm

In my case it was a sneaky Cisco device recently configured by a vendor for the same IP as our Exchange 2003 server. A brand new 2008 R2 server picked up the Cisco router MAC instead of the Exchange server for the IP and so could not ping or communicate at all with the Exchange server. All other devices were older so their ARP tables correctly pointed to the Exchange server and they could communicate fine. A comparison of the ARP table on 2008 R2 server and the physical address of the Exchange server showed they did not match indicating a conflict.
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2012 4:20pm

Hi John, Can you share how the issue resolved. Binosh binosh1@hotmail.com
May 15th, 2012 6:07am

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

Other recent topics Other recent topics