On Sat, 2007-01-27 at 00:20 +0000, Michael Fothergill wrote:
> Dear Debianists,
>
> I have now installed Etch AMD64 RC1 successfully on my new AMD64 box. The
> only problem I have is that the internet connection isn't working.
>
> My old box is an AMD Duron 1200 Mhz 32 bit machine which is running Etch
> i386. The internet connection works fine on it.
>
> I use NTL broadband cable.
>
> I have used the old box to help me get information about my internet
> connection.
>
> If you look in the network tools window you get information for eth0
>
> IP address.
>
> It is 86.22.11.90 and this is NTL.
>
> I checked with the whoami tool.
>
> I also looked in the network configuration box in the network admin icon. I
> found that the DNS server numbers for NTL are 194.168.4.100 and
> 194.168.8.100.
>
> I also ran ifconfig as follows:
>
> mikef@spc1-burn4-0-0-cust262:~$ /sbin/ifconfig
> eth0 Link encap:Ethernet HWaddr 00:02:44:33:AD:C3
> inet addr:86.22.11.90 Bcast:255.255.255.255 Mask:255.255.252.0
> UP BROADCAST RUNNING MULTICAST MTU:576 Metric:1
> RX packets:5190 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4341 errors:0 dropped:0 overruns:0 carrier:0
> collisions:2 txqueuelen:1000
> RX bytes:2418361 (2.3 MiB) TX bytes:602343 (588.2 KiB)
> Interrupt:5 Base address:0xc800
>
> eth1 Link encap:Ethernet HWaddr 00:0A:E6:0C:AE:D4
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:5 Base address:0xcc00
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:128 errors:0 dropped:0 overruns:0 frame:0
> TX packets:128 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:6560 (6.4 KiB) TX bytes:6560 (6.4 KiB)
>
> My question is: what is the best use of this information when I disconnect
> the old box and plug in the new one to help it hook up to NTL?
>
> I could just put the DNS numbers in the network admin window for example.
One of the very first things you must do when putting a new
machine/NIC(network interface card) on the cable modem... is to unplug
the cable modem. Well here is the series of actions I use.
1. shutdown old machine
2. turn off old machine
3. remove power from cable modem
4. unplug network cable from NIC
5. remove old machine
6. place new machine
7. plug network cable in new machine
8. restore power to cable modem
9. turn-on and start new machine
The sequences is pretty important. You see the cable modem has to see
you machines NIC or "hardware address" (HWaddr 00:02:44:33:AD:C3 on the
stuff you posted) and it remembers this ... it needs to forget and
remember the new stuff.
Once that happens, it should work fine. Most DOCSIS modems are this way
(DOCSIS == Cable Internet Infrastructure), although some cable internet
providers require activating the new HWaddr. I highly doubt that your
does this from things I've searched for.
--
greg@gregfolkert.net
Novell's Directory Services is a competitive product to Microsoft's
Active Directory in much the same way that the Saturn V is a competitive
product to those dinky little model rockets that kids light off down at
the playfield. -- Thane Walkup
Attachment:
signature.asc
Description: This is a digitally signed message part