Intranet website will not resolve in Windows 7
I've stumbled upon something that has me very confused. I am running a web server on my home intranet and everything was working fine until I installed Windows 7 on it and my laptop. When I try to access my intranet website with http://<computername> in IE 8 or Firefox from Windows 7, the internal address will never resolve and I get the "web page is not available" error. Both the web server and my laptop have been upgraded to Windows 7, and both exhibit this behavior. I still have a computer running XP in my intranet, and it has no trouble accessing the web server in both IE 8 and Firefox. Has something changed in Windows 7 that will not resolve internal IP's for web pages?
November 2nd, 2009 6:02pm

Hi Lhmathys, Before moving on, could you please let me know if you can ping this intranet website?In additon, can you post the result of IPCONFIG /ALLon the forum?Thank you for your cooperation.
Free Windows Admin Tool Kit Click here and download it now
November 3rd, 2009 8:58am

Yes, I can ping any of the windows 7 machines in my LAN (I just can't resolve my internal web server by hostname in IE or Firefox - and yes, I've tried it with the firewall turned off on both sides.) Here's my ipconfig: Windows IP Configuration Host Name . . . . . . . . . . . . : XXXX Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) Physical Address. . . . . . . . . : 00-22-69-BF-70-20 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Dell Wireless 1505 Draft 802.11n WLAN Min i-Card Physical Address. . . . . . . . . : 00-23-4D-70-33-7D DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::5970:41fd:a708:5d52%12(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.2.104(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Tuesday, November 03, 2009 6:03:09 AM Lease Expires . . . . . . . . . . : Wednesday, November 04, 2009 6:03:08 AM Default Gateway . . . . . . . . . : 192.168.2.1 DHCP Server . . . . . . . . . . . : 192.168.2.1 DHCPv6 IAID . . . . . . . . . . . : 218112845 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-78-0B-F1-00-21-9B-F6-43-05 DNS Servers . . . . . . . . . . . : 192.168.2.1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Marvell Yukon 88E8040 PCI-E Fast Ethernet Controller Physical Address. . . . . . . . . : 00-21-9B-F6-43-05 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Tunnel adapter isatap.{17B51752-63F4-4ECA-BC72-AA63753F1E7A}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:34ef:143a:9f1d:153a(Pref erred) Link-local IPv6 Address . . . . . : fe80::34ef:143a:9f1d:153a%15(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled Why does my Windows XP machine still work fine in both IE 8 and Firefox? It can resolve the Windows 7 IIS just fine, but none of the Windows 7 machines resolve the internal host name. Very, very strange.
November 3rd, 2009 1:01pm

Here's some further information: When I ping a Windows 7 machine on my LAN, I get an address that appears to be hex, like: XXXX::XXXX:XXXX:XXXX:XXXX%XX When I ping a Windows XP machine on my LAN, I get a standard IP, like: XXX.XXX.XXX.XXX Is Windows 7 using IPv6 on my LAN or something?
Free Windows Admin Tool Kit Click here and download it now
November 3rd, 2009 1:33pm

Hi Lhmathys, It seems Windows 7 try to use IPv6 communicate with Windows 7 computers on the LAN. Could you please try to use the following command to disable IPv6 to troubleshoot this issue?netsh interface ipv6 set global randomizeidentifiers=disabledPlease run this command in a elevated CMD.Thanks.
November 4th, 2009 3:03am

Thanks Robinson, but that didn't work. Does this have anything to do with the new "HomeGroup" option? I'm still confused why the browser cannot resolve the address even if the OS is trying IPv6.
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2009 4:17am

Thank you for your update. Given the current situation, please help me confirm the following points. 1. Does the ping work as expected?2. Can you access that computer by \\computer name?3. Can you acesss that computer by \\IP address?Thank you for your cooperation.
November 4th, 2009 7:42am

1. Yes, I can ping both computername and the IP, but as I said before, I get the IPv6 address when using \\computername. 2. Yes 3. Yes Still won't resolve internal web server name to IP in a browser.
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2009 12:56pm

Hi Lhmathys, I noticed you mentioned you still gotIPv6 address when ping the web server using \\computername. Did you only disable IPv6 on laptop? Could you please disable IPv6 on the web server to troubleshoot this issue if possible?If the issue still persist after disabling IPv6 on both computers, we will capture network package to analyse this problem. Thank you for your cooperation. Hope it helps.
November 5th, 2009 9:56am

Yes. . . I ran the command in an elevated command prompt on both the web server and the client computer and I still get the IPv6 addresses. If I ping the web server from my laptop, I get IPv6. If I ping my laptop from the web server, I get IPv6. Both computers are running Windows 7. If I try the same HTTP request to my web server from a Windows XP machine, my intranet web site works fine. I'm starting to feel like we're going in circles. Can we please try something other than netsh and ping?
Free Windows Admin Tool Kit Click here and download it now
November 5th, 2009 12:35pm

Hi Lhmathys, let's capture network package to troubleshoot this issue. 1) Download NetMon3.3 from the following website and install it on the laptophttp://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=983b941d-06cb-4658-b7f6-3088333d062f2) Launch NetMon3.3.3) In the Microsoft Network Monitor 3.3 window, click Create a new capture tab 4) In the new tab, select all the Network Adapters in the Select Networks window.5) Then, switch to Network Monitor, press F5 to start NetMon.6) Try to access the web server.7) Go back to the NetMon window and press F7 to stop the NetMon.8) Press Ctrl+S to save the Netmon file named test.Please upload the file to Windows Live SkyDrive (http://www.skydrive.live.com/) and share the URL with us. Thank you for your cooperation.
November 11th, 2009 9:48am

I'm having this exact same issue. Windows 7 was installed on 2 different computers, neither of them can resolve our intranet address'. One site is a Sharepoint site and the other is just a basic page created in Frontpage (I say this just to rule out some sort of Sharepoint issue). I can ping these sites using the IP, and i can browse to the sites by typing in the server names. However when the Windows 7 boxes use the user friendly DNS entry I made, http://intranet or http://intranet2, they won't resolve to the site. The other 99% of computers on this network run XP and resolve the intranet sites just fine.
Free Windows Admin Tool Kit Click here and download it now
April 1st, 2010 8:42pm

In Windows 7, if you try to ping your own PC name on the network, it defaults to a IPv6 display. If you place a -4 between the ping and the computer name, the results will be in IPv4 format.
April 1st, 2010 10:29pm

robert, thanks for the reply. would you mind going into greater detail on how this could help resolve my problem? Are you saying i need to disable IPv6 on the NIC?
Free Windows Admin Tool Kit Click here and download it now
April 2nd, 2010 1:16pm

Without trying to hijack the thread from the OP, my reply was for the issue of pinging \\computername and getting back a hex code from the results. As for your issue, a quick solution is to place the IP and hostname in the host file. Also check to make sure your WINS/DNS are pointed correctly on that local machine.
April 5th, 2010 9:57pm

i could do that but i don't want to have to edit every future workstation i roll out. It wll also cause additional work if i ever move the sites to another server. I find it hard to believe there is not an official microsoft statement about this issue. I appreciate your help anyway. Jeff
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2010 1:49pm

Researching a very similar problem. Maybe one of these references will help in your case. Once our problem is resolved, I post the solution here. In our situation only Win7 on a different subnets located at remote sites connected via route based hardware VPN's are having the problem. Good luck with these links. http://msdn.microsoft.com/en-us/library/aa383144.aspx http://support.microsoft.com/kb/294382/ http://msdn.microsoft.com/en-us/library/cc982052.aspx http://blogs.msdn.com/david.wang/archive/2005/07/14/HOWTO_Diagnose_IIS_401_Access_Denied.aspx http://support.microsoft.com/Default.aspx?id=943280 http://support.microsoft.com/default.aspx?scid=kb;en-us;896861 http://support.microsoft.com/default.aspx?scid=kb;EN-US;941853 http://support.microsoft.com/kb/871179/ http://support.microsoft.com/kb/303650 http://www.paulliebrand.com/2008/04/02/sharepoint-consistently-prompting-for-user-credentials/ http://www.slickit.ca/2009/02/internet-explorer-enable-intranet.html http://support.microsoft.com/kb/943891 Corp site does not experience the problem except with Firefox...this one did fix that problem, but it did not work for the remote sites connected via hardware vpn:::::: http://support.mozilla.com/en-US/kb/Firefox+asks+for+user+name+and+password+on+internal+sites?bl=n&s=windows%20authentication
May 14th, 2010 6:09pm

Hi i stumbled upon your conversation during my attempts to find an answer for my problem and you might be able to help me: my works network is mainly based on WINXP one of our new computers with win 7 is unable to connect to one of our work stations which is a CNC machine. 1. I can ping! 2. cant access it by \\IP address this problem exist ONLY in the WIN7 station' every other station accesses the machine with no problem. thank you
Free Windows Admin Tool Kit Click here and download it now
January 10th, 2011 5:36am

This issue is affecting my entire network, as well. I have approx 50/50 split between Win XP and Win 7 on desktops (150+ total). Some local, some at remote sites connecting via permanent VPN tunnels. I just took over this company's IT recently and they are not on a domain, just a workgroup. DNS is running on the Exchange sever (I know, I know, but one problem at a time). By default, Exchange server is a domain, although it is the only server in it's domain. Server OS is Server 2008R2 Every XP can resolve against the internal DNS as well as external DNS. If internal DNS is the only entry in the desktop the XP boxes will follow the forwarders in the local DNS server without a problem (it usually isn't, but we tested that way as well to troubleshoot). Every Win7 box can resolve against any external DNS server I point them at, but NONE will resolve against the internal one. NONE will follow the forwarders from the internal DNS server, either. So, we get internet access just fine, but can't see our own internal boxes by DNS lookup. Every desktop, both XP and Win7, can ping the servers just fine by IP, and can connect to web services as long as they target the internal IP directly. ONLY XP boxes can ping by name or browse to a local server by name. This issue effects EVERY Windows 7 box, and NONE of the XP Boxes. I can't for the life of me figure out why. Why can they all see any external DNS server just fine but not one on their own subnet?
March 9th, 2011 10:41am

Is it possible Win7 won't try to query a DNS server on a private subnet (i.e. 10.x.x.x) UNLESS they belong to the same domain?
Free Windows Admin Tool Kit Click here and download it now
March 9th, 2011 10:46am

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

Other recent topics Other recent topics