I'm asking this here because the problem spans the use of Internet Explorer, Firefox, Chrome, Safari, etal. I've an intranet site that I can connect to with any of the above browsers on Windows XP boxes and with various browsers on Linux boxes, yet I have difficulty connecting using the above listed browsers on Windows 7. When I do a cold boot and attempt a connection to the site, the connection process works fine. However, if I refresh the browser or navigate away from the site and attempt to return, the connection fails. Internet Explorer (9 in this case) displays the standard "Internet Explorer cannot display the webpage" page. Clicking on the "More information" link displays a six-member list of possible causes, none of which are the issue (it's not a DNS issue; network connectivity is fine; there is no typo in the URL, and it's not an HTTPS issue). No other computer in our organization has a problem accessing the site in question - just this one (it's our only Windows 7 box - for now). Does anyone have an idea why this is happening and what I can do to fix the problem? Thanks in advance.

sounds like you need to check your DNS settings on the Win 7 box, is their third party firewalls installed that could be causing issues. From a box that you say is operational, do a nslookup to your site. Then do a nslookup on the Win 7 box, do they match? It could be something as simple as a wrong digit in your ipconfigs on that machine.:P Advice offered, If you need more help it is advised to seek the council and advice of paid professionals. The answer is always 42, or reboot.

Thanks for your response! There are no third-party firewalls installed on the Windows 7 box and, for the sake of testing, I've shut down the Windows firewall. I've examined the results of an "nslookup" on both the Windows 7 box and a Windows XP box and the results are the same. An interesting side-note: I have two DNS internal DNS servers - the "primary" is hosted on a Windows Server 2008 server and the "secondary" is on a Novel SuSE Linux Enterprise Server 10 box. If I reverse the "order of preferrence" everything works OK. So, perhaps the issue may lie with the DNS server on the Windows 2008 box. I'm scratching my head over this one. What might I check on the DNS server side? Thanks again.

Ah, you probaly have a DNS replication issue between the Windows and Linux DNS servers, you may have to Bing! for articles related to DNS zone updates between Windows and Linux. My 2 cents is that you look into picking one or the other, since AD integrated DNS offers you a lot of rich functionality, I would look into standing up a new Windows Box for your secondary DNS server and stopping the Linux DNS server.:P Advice offered, If you need more help it is advised to seek the council and advice of paid professionals. The answer is always 42, or reboot.

I thought we had this one beat, but it's rearing its ugly head again. I've got DNS running on a Windows Server 2008 box and a Windows Server 2003 box (Linux DNS has been shut down). Active Directory is running on the same 2008 box as DNS. I've an internal Web server set up with virtual hosts (it's located at 192.168.1.79). DNS entries for this server are as follows: Host Record: chameleon12 -> 192.168.1.79Alias Record: school -> chameleon12Alias Record: armer -> chameleon12 If I run an "nslookup" (on either a Windows 7 PC or a Windows XP PC) for any of the above names (chameleon12, school, armer), the response comes back with the correct results. However, if I "ping" them from a Windows 7 box I get a reply that reads "Ping request could not find host <hostname here>. Please check the name and try again." If I execute a "ping" from a Windows XP box it responds with the expected results ("Reply from 192.168.1.79: ...."). I've tried running the "ipconfig /flushdns" command on the Windows 7 box with mixed results - sometimes it seems to work, others not. I've also shutdown and restarted the DNS server - again with mixed results. I don't have any problems when accessing these internal sites when using Windows XP or a Linux box - the problem only manifests itself on Windows 7 PCs.