I just installed Suse 7.1 and I can't get my cable modem to work with it. It is recognizing the Ethernet card and dhcp is loading correctly at start up but for some unknown reason I am not able to communicate with my provider. I am in the US using the @home service. If anyone has any ideas they would be greatly appreciated. Diane
Hi Diane
I just installed Suse 7.1 and I can't get my cable modem to work with it. It is recognizing the >Ethernet card and dhcp is loading correctly at start up but for some unknown reason I am not able to communicate with my provider. I am in the US using the @home service. If anyone has any >ideas they would be greatly appreciated. Diane
Have you used a different PC on your cable modem in the past? with my cable service in the UK the Cable Modem (3COM) remembered the MAC address of the first PC I attached to it, thereafter it refused to talk to another ethernet card, without overiding that cards MAC address. I made a not of the MAC address of the first PC I attached and now I use a Linksys router which you can program the MAC addresss. You should be able to overide the MAC address in Linux, there should be far more experienced users on this list who can advise. David Bottrill
I have at home and It will often rememver the MAC address from a previous nic. Two things to try. A) Unplug the cable modem from the wall for a minute or two and this my reset it. B) Unplut the cable modem from the wall and then push a reset button (usually a small hole in the back labelled "reset". I used a paper clip - be careful not to dig around in there) and try it again. Remember that it can take about 10-30 minutes to latch to the server, especially with @home. Just plug it in and let it blink (or not) for awhile. I've had to do this a couple of times. Just have to be patient. On Sunday 13 May 2001 12:19, SpiderSpell wrote:
I just installed Suse 7.1 and I can't get my cable modem to work with it. It is recognizing the Ethernet card and dhcp is loading correctly at start up but for some unknown reason I am not able to communicate with my provider. I am in the US using the @home service. If anyone has any ideas they would be greatly appreciated.
Diane
---------------------------------------- Content-Type: text/html; charset="iso-8859-1"; name="Attachment: 1" Content-Transfer-Encoding: quoted-printable Content-Description: ----------------------------------------
I just installed Suse 7.1 and I can't get my cable modem to work with it. It is recognizing the Ethernet card and dhcp is loading correctly at start up but for some unknown reason I am not able to communicate with my provider. I am in the US using the @home service. If anyone has any ideas they would be greatly appreciated.
Diane There are several companies, using different equipment, that seem to be using the '@home' trademark, so YMMV... In the Detroit area, Comcast @home service uses a system based upon hostname, rather than MAC address. The account name they gave you (Which
On Sun, 13 May 2001, SpiderSpell wrote: they tell you to put in the 'machine name' box in windows) must be presented to the DHCP server as the 'hostname'. If you're using dhcpd, declare this with the -h flag. With dhclient, it's declared in dhclient.conf. I'm not up on pump, so a little research will find the equivalent syntax. -- Rick Green "I have the heart of a little child, and the brain of a genius. ... and I keep them in a jar under my bed"
I just installed Suse 7.1 and I can't get my cable modem to work with it. It is recognizing the Ethernet card and dhcp is loading correctly at start up but for some unknown reason I am not able to communicate with my provider. I am in the US using the @home service. If anyone has any ideas they would be greatly appreciated.
Diane There are several companies, using different equipment, that seem to be using the '@home' trademark, so YMMV... In the Detroit area, Comcast @home service uses a system based upon hostname, rather than MAC address. The account name they gave you (Which
-----Original Message----- From: rtg@aapsc.com [mailto:rtg@aapsc.com]On Behalf Of Rick Green Sent: Monday, May 14, 2001 11:22 AM To: SpiderSpell Cc: suse-linux-e@suse.com Subject: Re: [SLE] Cable Internet Problems On Sun, 13 May 2001, SpiderSpell wrote: they tell you to put in the 'machine name' box in windows) must be presented to the DHCP server as the 'hostname'. If you're using dhcpd, declare this with the -h flag. With dhclient, it's declared in dhclient.conf. I'm not up on pump, so a little research will find the equivalent syntax. -- Rick Green "I have the heart of a little child, and the brain of a genius. ... and I keep them in a jar under my bed" Thanks for the suggestion Rick. I did go into usr/sbin/rcdhclient and added the hostname/computer name and the -h flag as you suggested. The @home service uses the same system here in Virginia that you described above. That got the dhclient to load correctly at start up but there seems to be another problem that I just can't put my finger on. When I open a browser in Linux I just keep getting messages saying server not recognized. I talked to Suse and they pinged me successfully however I am not able to ping out and they are at a loss as well but they also are not very familiar with cable. I also use the ethernet card and cable modem on windows on this machine with no problems at all. I have also tried searching the internet for information about this problem or anything related to using linux with the @home service but so far every link I found leads to a file that no longer exists. Diane _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
participants (4)
-
Curtis Rey -
David Bottrill -
Rick Green -
SpiderSpell