1.
"ipconfig /all". Thank you for the "ipconfig" output. Just to let you know, did not receive the "route print" output. In its place, you posted the ipconfig output a second time. It shows:
a. Node Type of "Peer-Peer". While I've never seen this before, apparently it sets the "how" and "order" of name resolution checks, therefore should not affect any troubleshooting efforts using the numeric IPv4 addresses.
b. DHCP and autoconfiguration are enabled, so your basic TCP/IP parameters are configured and set automatically with values from a DHCP server. The basic parameters look reasonable to me (IPv4 Address, Subnet Mask, Default Gateway, DNS server). Your IPv4 address is on the same network as the default gateway. (My earlier claim that they were not was based on a "typo" in one of your earlier posts.)
c. Primary WINS Server. I don't understand why it's set to "127.0.0.1", but again since it stands for
Windows Internet Name Service; it should not affect any troubleshooting efforts using numeric IPv4 addresses.
d.
IPv6. As I haven't worked with Vista or IPv6 some of the output is puzzling to me. Particularly why there are so many entries for IPv6. Might bear further analysis. For troubleshooting purposes, I'd just "uncheck" the Microsoft TCP/IP version 6 protocol from the wired network adaptors defined connection (and reboot).
2.
Internet Service Provider.
a. Does someone else's computer successfully connect and browse Internet using your wildblue connection?
b. Does laptop successfully connect and browse Internet using someone else's broadband internet service (connection)? If yes, then your TCP/IP stack and winsock should be OK.
3.
Internet Options/Network Connections.
a. Does the laptop have any "dial-up" connections defined? If yes, you might want to delete them.
b. Also ensure options to "dial" a connection are unchecked within "Connections" tab of Internet Options window.
4.
Unable to get online. Describe what you mean by this. Post the "exact" error, informational message, or symptoms that occur when you try.
5.
Browsers. Clear the browser caches and disable any proxy settings.
a. Internet Explorer (IE8). Try disabling the "proxy", if set. In Internet Explorer click Tools/Internet Options/Connections and click LAN Settings...uncheck any box that has a check mark in it...(no check marks for auto-detect, auto config script, or for the proxy). The proxy server is designed to provide better web browsing response, but is not required.
b. Firefox. Download, install, and try the latest Mozilla Firefox browser. It won't have a "proxy" server set. In Firefox, to veriy, click Tools/Options/Advanced/Network/How to connect and check the "No Proxy" box...
c. From both browsers, try to access HP FTP Server website using "FTP" protocol: "ftp://ftp.hp.com/" and "ftp://15.217.49.73/".
6.
Firewalls. Check your firewall settings (for what exactly, I'm not sure).
7.
Ping. You should always be able to "ping" your own IPv4 address, especially if you can successfully ping the default gateway address. Please ping these two values again and post the "exact" error message you receive if not successful (and an average response time if successful). For example:
a. Request timed out.
b. PING: transmit failed, error code 1231.
c. Destination Host Unreachable.
8.
WildBlue Forum. Suggest you open a parallel thread on the wildblue forum. While they accept no responsibility for your computer configuration, it appears you might get some assistance from their "Moderators" who apparently are wildblue employees if you are civil. See
http://wildblueworld.com/forum/. Look at either the "Tech Chat: WildBlue and beyond!" or "Questions, Problems and Troubleshooting" categories.
9.
Ubuntu Live CD. A Live CD contains a bootable operating system that will load and run from the CD (does not need to be installed to the hard drive). The Ubuntu Live CD is about 700 MBytes of data. Probably more than you want to download. But you may request a "free" CD. They say it could take several weeks for delivery, however. I mention the Ubuntu Live CD because it's pretty good about automatically configuring its network connection for an internet connection upon boot. You might be able to use it to further convince yourself the problem is your laptop software/configuration and not the wildblue hardware. See
http://www.ubuntu.com/getubuntu.
