> Cox configured the Cisco 2600 router so it doesnt have
> DHCP enabled

Did Cox tell you what address to use for your computer?  Or what range
of addresses to chose one from?

> The nameservers that I am using are Cox nameservers
> When I type in an adress for example googleit just says "Looking for 
> www.google.com"
>
> when I looked in /etc/resolv.conf it says
>
> search localhostnameserver 68.105.28.11nameserver 68.105.29.12

Is that what is really in /etc/resolv.conf or have you managed to lose
some newline characters that would put things on separate lines?  I
can't read over your shoulder from this far away.  I would expect
/etc/resolv.conf to look more like this, given your data.

search localhost
nameserver 68.105.28.11
nameserver 68.105.29.12

> by the way, Cox gave me these nameservers lastnight, I previously had two 
> differentnameserver adresses
>
> When I tried to connect using the IP addressof google it just says 
> transferring data from 74.125.95.103 and never does anything else
>

Is there some way you can fix your email replies so they don't all get
smashed together like the sample below?

>> Date: Mon, 1 Dec 2008 09:24:30 -0800> From: [EMAIL PROTECTED]> To: 
>> [email protected]> Subject: Re: Connecting with CentOS 5.2> > On 
>> Sun, Nov 30, 2008 at 8:31 PM, Michael Lynch <[EMAIL PROTECTED]> wrote:> >> > 
>> I have my server connected to a switch which is connected to a Cisco 2600 
>> router> > Cox is my ISP> Date: Sun, 30 Nov 2008 20:07:40 -0800> From: [EMAIL 
>> PROTECTED]> To: [email protected]> Subject: Re: Connecting with 
>> CentOS 5.2> >

Really dumb question:  I looked at some of the on-line documentation
for the Cisco 2600.  There are several RJ45 sockets on the back.  Not
all of them are network connectors.  Are you plugged in to the right
hole?  Can you see link lights at both ends of the cable?

Do you get a reply from the Cox nameserver if you issue the command:
ping 68.105.28.11
I get
[EMAIL PROTECTED] tmp]$ ping 68.105.28.11
PING 68.105.28.11 (68.105.28.11) 56(84) bytes of data.
64 bytes from 68.105.28.11: icmp_seq=1 ttl=54 time=70.8 ms
64 bytes from 68.105.28.11: icmp_seq=2 ttl=54 time=69.0 ms
 . . .

    carl
-- 
    carl lowenstein         marine physical lab     u.c. san diego
                                                 [EMAIL PROTECTED]

-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie

Reply via email to