Is Internet Explorer 8 (IE8) IPv6 capable?
Hi I have a Windows 7 Ultimate machine with latest patches running IE8. I have a web service that supports both Ipv4 and Ipv6 addresses running on the same VLAN with addresses: IPv4: 192.168.10.56 IPv6: 2801:0:40:a::10 My PC has the following IP addresses: IPv4: 192.168.10.200 IPv6: 2801:0:40:a::a From my PC, I can ping both IPv4 and IPv6 addresses However, I can only access the web service via the IPv4 address i.e. http://192.168.10.56 I cannot access the web service via http://2801:0:40:a::10. I get the error message: "Windows cannot find http://2801:0:40:a::10. Please check spelling and try again" Can someone assist? Thanks. Regards Andre Thompson
November 4th, 2010 12:02pm

yes, you have to bracket the literal address: http://[2801:0:40:a::10] but I can't reach it over any browser.. In fact, I can't ping it either. You might want to troubleshoot that..
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2010 1:21pm

try with brackets: http://[2801:0:40:a::10] On Thu, 4 Nov 2010 15:58:24 +0000, AndreThompson wrote: > > >Hi > >I have a Windows 7 Ultimate machine with latest patches running IE8. > >I have a web service that supports both Ipv4 and Ipv6 addresses running on the same VLAN with addresses: > >IPv4: 192.168.10.56 > >IPv6: 2801:0:40:a::10 > >My PC has the following IP addresses: > >IPv4: 192.168.10.200 > >IPv6: 2801:0:40:a::a > >From my PC, I can ping both IPv4 and IPv6 addresses > >However, I can only access the web service via the IPv4 address i.e. http://192.168.10.56 > >I cannot access the web service via http://2801:0:40:a::10. I get the error message: > >"Windows cannot find http://2801:0:40:a::10. Please check spelling and try again" > >Can someone assist? > > > >Thanks. >Regards Andre Thompson Barb Bowman http://www.digitalmediaphile.com
November 4th, 2010 1:24pm

PING succesfull means the first 3 layer of OSI model are OK. This means only that. http://en.wikipedia.org/wiki/OSI_model Cable, NIC and hardware are fonctionnal between the 2 machines. PC is able to form a valid data packet that travel media layer PC NIC is able to send trough network and obtain distant NIC a forward. Do not think that because your PING works that network is OK. Your packet barely entered the distant NIC and get back home to flip a memory bit to 1 on NIC saying packet X is back and that it. OS and service have nothing to do with PING. W7 send command PING via driver and wait for NIC to answer. Your trouble is apparently related to layer 4-5-6 or 7 If someone in direct local lan is able to establish communication in IPV6 then i think the service or OS do not know what to do with the IPV6 packet from your session. I mean somewhere in OS policies or setup of service your access is deny to the service server when you wear IPv6 suit. Maybe service support V6 but misconfigured..
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2010 5:17pm

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

Other recent topics Other recent topics