--------------58B0413394FB4E525FC12BC3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit
Ewwwwww, didn't even work static!?!? Double and triple check the settings.... Can you ping an IP address? (no domain names, eliminate dns). Can you even ping the gateway when setup as static? What kind of cable modem are you using? (heard the old 3com's had a prob with the new network) Last ditch effort... I've been using the Dlink 704's cable modem sharing device to tie networks to the internet, and they make a handy NAT translated firewall. Anywho, I've had good luck using these Dlinks on various DHCP setups with different providers (even have one running on the wifes computer using a cable modem). I've tried similar Linksys devices (their okay), but I'm pretty partial to the Dlinks (short of going to a full blown router). In short, I let these devices handle the connectivity to the net, while keeping my network configured for local settings. I know this may be a little overkill to fix a DHCP problem on the computer, but you really should have something between you and the big, bad world out there anyway. Just a thought........ Nat "Banker, Craig" wrote: > Did that... pulled in my static settings...Another thing I noticed is > on the win side, the DHCP lease period is exactly 24 hours where it > had been longer on previous occasions.My IP or DNS servers have not > changed since the upgrade.I'm at a loss... > > -----Original Message----- > From: Nat Bayles [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 21, 2002 10:01 AM > To: [EMAIL PROTECTED] > Subject: Re: [brluglist] Unannounced Cox network > changes...?? > > One way to find out....... > > Make note of the settings provided by DHCP (dns, gateway, > and ip). > Now change your linux from being dchp to a static setup, > using the settings from cox. > (keep in mind, ip's very rarely change on cox to date) > This should get the linux side back up and running, at least > utill the ip address changes on your account. > > Nat > > --------------58B0413394FB4E525FC12BC3 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> <body bgcolor="#FFFFFF"> Ewwwwww, didn't even work static!?!? Double and triple check the settings.... <br>Can you ping an IP address? (no domain names, eliminate dns). <br>Can you even ping the gateway when setup as static? <br>What kind of cable modem are you using? (heard the old 3com's had a prob with the new network) <p>Last ditch effort... <br>I've been using the Dlink 704's cable modem sharing device to tie networks to the internet, and they make a handy NAT translated firewall. Anywho, I've had good luck using these Dlinks on various DHCP setups with different providers (even have one running on the wifes computer using a cable modem). I've tried similar Linksys devices (their okay), but I'm pretty partial to the Dlinks (short of going to a full blown router). <br>In short, I let these devices handle the connectivity to the net, while keeping my network configured for local settings. <p>I know this may be a little overkill to fix a DHCP problem on the computer, but you really should have something between you and the big, bad world out there anyway. <p>Just a thought........ <p>Nat <br> <br> <br> <br> <br> <p>"Banker, Craig" wrote: <blockquote TYPE=CITE> <span class=380431516-21032002><font face="Arial"><font color="#0000FF"><font size=-1>Did that... pulled in my static settings...</font></font></font></span><span class=380431516-21032002></span><span class=380431516-21032002><font face="Arial"><font color="#0000FF"><font size=-1>Another thing I noticed is on the win side, the DHCP lease period is exactly 24 hours where it had been longer on previous occasions.</font></font></font></span><span class=380431516-21032002></span><span class=380431516-21032002><font face="Arial"><font color="#0000FF"><font size=-1>My IP or DNS servers have not changed since the upgrade.</font></font></font></span><span class=380431516-21032002></span><span class=380431516-21032002><font face="Arial"><font color="#0000FF"><font size=-1>I'm at a loss...</font></font></font></span> <blockquote dir=ltr style="MARGIN-RIGHT: 0px"> <div class="OutlookMessageHeader" dir="ltr"><font face="Tahoma"><font size=-1>-----Original Message-----</font></font> <br><font face="Tahoma"><font size=-1><b>From:</b> Nat Bayles [<A HREF="mailto:[EMAIL PROTECTED]">mailto:[EMAIL PROTECTED]</A>]</font></font> <br><font face="Tahoma"><font size=-1><b>Sent:</b> Thursday, March 21, 2002 10:01 AM</font></font> <br><font face="Tahoma"><font size=-1><b>To:</b> [EMAIL PROTECTED]</font></font> <br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [brluglist] Unannounced Cox network changes...??</font></font> <br> </div> One way to find out....... <p>Make note of the settings provided by DHCP (dns, gateway, and ip). <br>Now change your linux from being dchp to a static setup, using the settings from cox. <br>(keep in mind, ip's very rarely change on cox to date) <br>This should get the linux side back up and running, at least utill the ip address changes on your account. <p>Nat <br> </blockquote> </blockquote> </body> </html> --------------58B0413394FB4E525FC12BC3-- ================================================ BRLUG - The Baton Rouge Linux User Group Visit http://www.brlug.net for more information. Send email to [EMAIL PROTECTED] to change your subscription information. ================================================
