[NTLUG:Discuss] @Home connection problems. Can't even ping.

[Kelly Scroggins]

At one time, @home support had me cycle both the modem
and the puter. 

Try powering the puter off, then power cycle the modem.
After the modem is back up, power up the puter.

Just a shot in the dark.  

I was once instructed by @home support to do that.
But that's the only time I've ever done it that way.
But I usually have to reset the modem at the least when
I change NICs.

Might be worth a try.  It'll take 5 minutes, maybe 10.

kelly


Quoting Jay Urish <j at dalwan.net>:
   At 09:46 PM 5/24/00 , you wrote:
   
   Kip has a static Ip.. I even tried DHCP with my winblows laptop. It 
   wouldn't get an address..
   
   The funny thing is, I put all of the static info into the laptop and it 
   wouldn't work there either..
   
   >         In my experience with @home (both in Toronto, and in Nashville,
   >never used a cablemodem in Texas), they require DHCP for the clients,
   >simply copying the auto-assigned Windows IP/GW/Etc won't work (Cablerouter
   >thingy remembers MAC addr of NIC who DHCP'd the IP).  Try running "dhcpcd
   >eth1" on the Linux boxen (assuming you want eth1 to be the interface
   >connected to cablemodem), and see what you get.  Best of luck!
   >
   >--
   >A.L.Lambert
   >
   >--------------------------------------------------------------------------
   >If what they've been doing hasn't solved the problem, tell them to do
   >something else.
   >         -- Gerald Weinberg, "The Secrets of Consulting"
   >--------------------------------------------------------------------------
   >
   >
   >_______________________________________________
   >http://ntlug.org/mailman/listinfo/discuss
   
   
   Jay Urish
   Network Engineer - Dallas Wide Area Networking L.L.C
   www.dalwan.net
   
   
   _______________________________________________
   http://ntlug.org/mailman/listinfo/discuss