Topic: rogers cable settings

[peter]

Still having no luck with establishing internet connection. Any help would be appreciated.

I have two pci network adapter cards and will connect one to the cable
modem and the other to a hub. The ethernet adapters in the server are external -
dlink 530 tx -picked up as via rhine, and internal smc ez 10/100 smc 1211 series,
picked up as rt18139. I have not tried connecting the hub and any other computers, am just trying to have the internet tested positive.

e-smith settings are:

operation mode - dedicated server and gateway
DHCP enabled - send system name as client id (this is a number given to me by rogers cable, crxxxxx-a)
DNS service - not used.
local ip address 192.168.101.1.
local subnet mask 255.255.255.0
DHCP host numbers from 192.168.101.65 to 198.168.101.250
Pimary domain name - anyoldname (not using server for webhosting or email)  system name - myserver
external proxy - no.

[Terry Brummell]

When Rogers switched from @Home to their own network, they also changed the way they authenticate machines.  They are now using the MAC address from your external facing nic card.  If you had your existing cable service up and working with, say, your Windows machine, using whatever nic it has, then unplug the RJ45 from the Windows machine and plug it into the SME machine, it will not get an IP address from Rogers.  They are expecting to see the MAC address from the Windows machine.  If you pull the nic card out of the Windows machine, and install it in the SME, using it for the external interface, you should be able to renew your lease.
If you are still unable to get an IP, or are not able to install the Windows nic in the SME (because it's ISA), then call Rogers tech support and tell them you need to change the MAC address that they are authenticating you with.  This could take 3-4 days to complete.
One other thing you may try, if you are still using your Rogers connection on your Windows box, before you unplug your RJ45, or shut down your Windows box, using winipcfg (Win9X/ME) or ipconfig /release (NT/2000/XP), release your current IP info and you may be able to renew your lease with the SME box.  I've heard of this working in the past when switching nic's.
Hope this sheds some light on your situation.

Terry

[Christian Gravelle]

One other quick suggestion (which you may have already tried) is to unplug the power from the cable modem for 5 minutes (or at least one minute). I use to have to do this every time I wanted to switch which computer was hooked up to my cable modem, such as when I wanted to surf with my laptop instead of a desktop.

This seemed to reset the modem and the MAC address that it was using and all worked well once it would synch back up.

[David]

I've been running esmith for 2 yrs now. When Rogers changed from @home, I didn't have to change anything on my machine. The Netcard I've got on my esmith(btw the version is 4.1) is NOT the one the rogers gave me. I haven't rebooted my esmith box in about 50 days so don't know if that has any effect, but I'm still surfing away.

[Terry Brummell]

No David, that wouldn't affect anything.  Once they made the switch, as soon as the 1st time your E-Smith renewed it's DHCP lease they would have recorded the current MAC address.  I don't use my original nic card from Rogers either, it died the 1st week of service (3 years ago!).

David wrote:
>
> I've been running esmith for 2 yrs now. When Rogers changed
> from @home, I didn't have to change anything on my machine.
> The Netcard I've got on my esmith(btw the version is 4.1) is
> NOT the one the rogers gave me. I haven't rebooted my esmith
> box in about 50 days so don't know if that has any effect,
> but I'm still surfing away.

[Jon Williamson]

This sounds similar to the problem I get with e-smith server.

I've installed e-smith as a private server running as a gateway, but I can't get the external interface up at all.  

Looking in the logs I can see when the system tries to bring up the external interface that DHCP cannot get an address from the cable modem.  I get a DHCP timeout after 1 minute.

I've tried releasing the address from my windows box before disconnecting it, and even swapping the ethernet card.  I can get any of 4 different cards to work through windows (have to release the previous card or turn the cable modem off for a few minutes when I make the switch - otherwise I get a 'no address available' message), but none of them can get an address when running though e-smith.

Windows does take a very long time sometimes to get an address, so I'm wondering if the timeout is too short under e-smith but I don't know where/how it is configured.  Any thoughts on this?

You can check if you are having the same problem by going to the linux shell (alt-f2 and log in as root), and try and bring up the external interface ( 'ifup ethX' where X is 0 or 1 depending on your configuration).  If this fails then check /var/log/messages ( 'tail /var/log/messages' ), you should see messages about DHCP, this is where I see the timeout message.

I'd be interested to know if we are having the same problem.  I'd be even more interested if someone has a solution!

Jon

PS - I've used the machine in question with the Linux Router Project and it worked fine, so I don't think it's a generic Linux issue.