Windows Client TechCenter >
Windows 7 Forums
>
Windows 7 Networking
>
Intranet website will not resolve in Windows 7
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?
All Replies
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.- 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. - 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? - 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=disabled
Please run this command in a elevated CMD.
Thanks. - 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. 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.- 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. - Hi Lhmathys,
I noticed you mentioned you still got IPv6 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. - 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? Hi Lhmathys,
let's capture network package to troubleshoot this issue.
1) Download NetMon3.3 from the following website and install it on the laptop
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=983b941d-06cb-4658-b7f6-3088333d062f
2) 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.
