I'm guessing you mean you can get to other sites from that connection, just not
www.sowal.com. If you can't get to any sites, you should check your TCP/IP connection properties, specifically how it assigns an IP address (static and specified, or dynamic) and how it finds a DNS server.
If you can get to other sites, just not
www.sowal.com, you could try a couple of things:
1) Make sure you're typing the address correctly:
http://www.sowal.com
(doesn't hurt to triple check -- make sure you type it rather than letting IE auto-complete it for you from a cached entry which could be bad)
2) If you're sure of that, try substituting the IP address of the site for the domain name. That is, instead of:
http://www.sowal.com
type:
http://64.182.20.40
or
http://64.182.20.40/bb
If that works, your connectivity and routing are good, but there's something screwing up name-to-ip resolution. (If that doesn't work there may be something screwing up your network routing and you should look at your DSL modem/router settings. Contact your ISP technical support.)
Assuming the IP address method above does work, open a command shell window and type:
nslookup
www.sowal.com
You should get a response that includes something like this:
....
Non-authoritative answer:
Name:
www.sowal.com
Address: 64.182.20.40
which shows your name server is configured properly.
If not, contact your ISP technical support.
If you do see the above, name resolution is fine, it's probably something interfering with Internet Explorer's use of the name resolution facility, which probably means some IE corruption. You could address this by re-installing IE or installing a different browser like FireFox.
But before trying either of those options, see if you can reach the web site from a different user account on the same computer. If you have more than one user account on the system, log in as a different user and try to bring up the web site. If that works, it's probably corruption in a user-specific IE configuration file used to resolve site names, like index.dat. If so, locate the offending account's IE index.dat file and delete it (do it from a command shell if you know how to do that). Actually, even if you don't have multiple accounts, locate the file and delete it anyway. It won't hurt and IE will just re-build it when you re-launch it.
It would be named something like:
C:\Documents and Settings\username\Local Settings\Temporary Internet Files\Content.IE5\index.dat