Hi Paul,
The op did state his email was working.
But it is odd that a System restore (if pre-IE9 update) continued to
yield an IE problem especially with mail functional and the requisite
networking handshaking to the email account server and back.
--
....winston
msft mvp mail
"Paul" wrote in message
"Nil" wrote in message
Not without more information. "Not working" is an almost completely
meaningless description.
What exactly happens when you try to use it. Be as detailed as
possible. Every error message is important.
The program just sits there with the error message: MNS.com or any other
web address - not responding.
Dose not have internet access. I can't describe it any better.
The email is working fine.
Cheers _ Hunibal _
So in fact, it could be *all* networking which is broken, not just
Internet Explorer 9.
You posted this with Windows Live Mail, but you may have posted your
message from something other than the affected computer. So we can't
take your successful posting to USENET, as proof that steps 1 thru 3
below aren't necessary.
In the following, things in double-quotes are commands, and you
don't need to type in the outer double-quotes.
1) In the start thing, type "devmgmt.msc" as a command, to start
Device Manager. Verify there is an entry for a hardware
device functioning as your NIC or Wifi. And that there are
no yellow marks or errors. This is a check the hardware is detected,
and a valid driver is loaded. If Windows Update loaded a new driver,
it could have broken something.
2) In network control panels, look for the icon that corresponds to
your current network setup. Maybe the computer thinks "the cable
has fallen out". On some Windows OSes, there'd be an icon on the
bar at the bottom, to indicate a cable disconnected. Figure out
where the network icon is hiding, and check the status.
3) If Windows Update installed a driver, you may be able to either
uninstall it, or roll back the driver in Device Manager (to the
older, working one). There should be a roll back button, when you
do Properties on the NIC or Wifi entry.
4) If you have some idea that, in fact, the hardware and driver end
are fine, next go to start and type in "cmd.exe" to open a Command
Prompt
window. I usually right-click on cmd.exe before starting it, and
select Run as Administrator. If probably isn't necessary for the
following commands, but you may have other things you want to
do in the Command window.
4a) Try "ipconfig" as a command. It should show the current IP address
being used by the interface. And if you have more than one interface,
it may show in the list. If any of the values don't make sense,
such as an IP address in the 169.254.x.x range, then you're not
connecting to the DHCP server on your home router or your ISP's
end. For example, my home LAN is in the 192.168 range (private,
non-routable), and to me, a 169.254 number would stick out like
a sore thumb.
I can also log into my router, via using a web browser. The router
is at a fixed address. We'll pretend that address is 192.168.100.1.
I'd use some web browser, do "
http://192.168.100.1" and try and
reach the router, then check the health page to see what addresses
are being used by the router itself. Maybe your ISP is down.
4b) Try "nslookup
www.sun.com". That will query the DNS server. When
your computer gets a dynamic address via DHCP, the DHCP server will
also tell your computer to "forward any queries to this particular
DNS server". Using the nslookup command, will query the DNS servers,
one at a time, and ask for a translation of an address. Now, you're
not getting this far, because IE says you're not getting a response
at all. So I doubt this will work for you. But it's another of the
diagnostic steps.
nslookup
www.sun.com
...
Address: 137.254.16.113
4c) Not all computers on the Internet, respond to a "ping" or "traceroute"
request. On servers, the admin can turn off the ICMP subset of
protocol.
That kills ping and fragmentation detection type functions. However, if
you know a particular computer supports ping, you can attempt to
"bounce"
packets off a foreign node. Since I just checked, and the Sun
Microsystems
main web server supports ping, we can bounce stuff off it.
ping
www.sun.com
ping 137.254.16.113
The two commands are equivalent, and the difference between them, is
the
first format will do a DNS query first, and get the numeric
translation,
before the actual ping is issued. The second form avoids having to get
the
DNS working (if you know the number already). Many times, when working
with
crippled networks in the past, I've survived on a text file with famous
IP addresses recorded in it. So if your networks have a habit of broken
DNS, a text file with your own recorded DNS values, can help you to do
a
few things.
Anyway, those are some basic ideas, without the necessary level of detail
to do all of them. Even if you don't do them all, it might give you a few
ideas to check out.
Some OSes have a "network diagnostic" hiding in them. When you're in
trouble,
you go to the "help" and try searching for "network diagnostic" and see what
whizzy code they provide for the job. Most companies don't do a very good
job of writing these, but it's still worth a test. What the test will do,
is some of the steps above, then the code will try to interpret the results
and tell you what's busted. Again, the interpretation is the hard part,
and code like that, isn't exactly "Siri" quality
If the diagnostic
reported something you couldn't understand, I would not be surprised by
such a design. Writing good diagnostics is hard.
Paul
