Yes, I am a Cox user (Orange County, Calif), and have switched NIC's frequently with
no problems. Don't even remember resetting the modem, although it's been a while, and
perhaps I did.
I do know a Media One Cable modem user who said he specifically had to work with Media
One to switch ethernet cards because Media One (local to Orange County Calif at least)
does only respond to the registered MAC address. He had to go through them to switch
to a different NIC that would work on his NT box, and his demo version of STN.
--
On Thu, 15 Jul 1999 16:24:46 Steve Yenney wrote:
>David Abrams wrote:
>
>> One thing to check. Around here (note @home) they tie access to the MAC of
>> the ethernet card the cable modem connects to.
>
>David, who is your actual cable provider?
>
>My experience has been that when first initialized, the cable modem does
>become temporarily "tied" to the MAC address of the ethernet card it is
>connected at the time of initialization. If you subsequently plug a
>different computer (with TCP/IP stack identically configured) into the
>cable modem WITHOUT reinitializing the modem, that computer will NOT be
>able to access the cable operator's network.
>
>HOWEVER, my experience has been that once the modem has been FULLY reset
>and a full reinitialization performed, the MAC number of any working
>10Mbs ethernet card installed in any properly configured computer has
>ALWAYS worked fine after a reset. To the best of my knowledge, this
>applies to many @Home installations, not just my area and not only
>subscribers who use Comcast.
>
>-----
>> If you want to connect to
>> another computer you have to call them and give them the new MAC number.
>
>Are you absolutely sure about this? Half the people answering the phone
>at the first tier support level wouldn't know what to do with the MAC #
>even if you gave it to them. I find this very unlikely, but perhaps
>your cable company is the exception to the rule.
>
>-----
>> You could try moving the ethernet card from the box they installed it on to
>> the STN box or try booting STN on the box they installed it on to see if it
>> connects.
>
>Yes, he could do that, but the first thing Jason should do is enable
>debugging and ping all relevant addresses from the STN box by invoking
>STN's command line mode. He should most definitely try to ping the
>gateway for his subnet which (based upon the WAN IP he gave of
>24.2.172.162) he would do from the STN command line by typing:
>
>ping 24.2.172.1
>
>
>(Are you listening [EMAIL PROTECTED]? It's really just that
>simple. :-))
>
>
>_______________________________________________
>ShareTheNet maillist - [EMAIL PROTECTED]
>http://www.webserv.com/mailman/listinfo/sharethenet
>
>
Free web-based email, anytime, anywhere!
ZDNet Mail - http://www.zdnetmail.com
_______________________________________________
ShareTheNet maillist - [EMAIL PROTECTED]
http://www.webserv.com/mailman/listinfo/sharethenet
