Using Linux server to connect to @Home Cable service


I have setup a Linux server to allow my other two home computers use my @home service.  I can browse the web just fine and email seems to work as well.  However, I can not see the @home proxy server (which they call "www").  How do I get setup to see thier proxy server?  Please let me know what info you need as I am unsure where to begin.  Thanks

Who is Participating?
munsieConnect With a Mentor Commented:

the solution to your problem is to set the default domain search path to include your domain.  The easiest way to find out what your domain is to look at the install sheet they gave you.

Under Linux, just add the domain name to the /etc/resolv.conf file.  Just add a search line.

On my box, I have the following in my resolv.conf for @home:


and from that I can see the www machine

On a Win95 box, use the Network Neighborhood properties and change your DNS settings in the TCP settings.

On a Mac, Open the TCP control panel and add the domain name to the additional domain names box.

and, to clarify a bit... www isn't a proxy server (as far as i know), it's just the home page for @home users.  It's used as a portal of sorts and it gives you access to setting up additional email accounts, web space, and additional IP addresses.

good luck,
nasaAuthor Commented:
Adjusted points from 200 to 300
"However, I can not see the @home proxy server (which they call "www")."

What is the URL for this machine?
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

nasaAuthor Commented:
The actual IP address for this machine is  The URL is "http://www" -- that's it.

Have you tried using the following?

Can you ping it?

Here are partial results from here:


Tracing route to []
over a maximum of 30 hops:
  1     1 ms     1 ms     1 ms  server []
 10    81 ms    84 ms    87 ms  194.ATM7-0.BR2.DCA1.ALTER.NET []
 11   196 ms   206 ms   215 ms
 12   226 ms   191 ms   186 ms []
 13   226 ms   193 ms   206 ms
 14   202 ms   209 ms   221 ms []
 15   199 ms   209 ms   209 ms []
 16   223 ms   214 ms   202 ms []
 17   245 ms   246 ms   253 ms []
 18   223 ms   269 ms   236 ms []

You usually do not need to actually "connect" to a proxy server. It just needs to relay your packets to another network.
keep in touch with us in ABQ:
nasaAuthor Commented:
Sorrry it took so long to get back, but that did the trick.  Thanks a lot.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.