Forgive my ignorance...
I used cox for about 3 weeks at a prior address, until I moved.
They didn't have the area finished so they were only giving the Cox
@home Express option, which was just half speed for half the price..
I played a lot with the dhcp trying to get it to work. I had no other
choice. I can't remember real well, but I did get it to work.
I set eth0 to be static at 192.168.1.1 then setup samba to be on the
@home workgroup like they want the windows systems.
I set the 'netbios name = ' to whatever the name was, I forget now..
I would wait a few minutes and try smbclient -U% -L //mynetbiosname
and as long as it worked I would then
ifconfig eth0 down
dhcpcd
Then it would pick up an ip and if I waited a few minutes.. I could try
smbclient -U% -L //mynetbiosname and it would list a cox machine as the
domain master..
after which cox' network couldn't tell I wasn't a windows box and the
internet would start working.
I was under the impression that they had ip checking setup and only
allowed access if the netbiosname was in their database.
I may be completely wrong, but it's worth a shot to anyone who must
play. I hope this helps in the battle somewhere. If someone does get it
to work, please post back here for anyone else who might be having
problems.. I'm sure we'd all be interested in seeing working results.
Sorry I can't give more details, but that was over a year ago now and
only a 3 week stent..
nathan
On Thu, 2001-10-25 at 22:44, tim cutler wrote:
> Like most linux users on Cox@home, I have a static IP address. Now,
> Cox@home has sent me email and tells me that they have "identified" my
> computer as having a static address and not using DHCP protocol. They
> are now insisting on my computer to adopt the DHCP protocol.
>
> I never managed to get DHCP protocol to work on my linux and wound up
> using a static IP address (as was recommended here, thanks) to good effect.
>
> I've tried the linux netcfg GUI, selecting "DHCP" for the protocol. As
> soon as I do that, I'm off the network.
>
> So, my trial and error begins again. I'm looking for any breadcrumb
> clues to speed this unpleasant process up. I prefer NOT to use the f!@**
> netcfg GUI (I hate that GUI; unless it works EVERY time it should always
> tell you what files it's "fixing"). I would rather get pointed to any
> /etc/ files that matter.
>
> I have RedHat 7.1. I don't get why this is so hard for linux.
>
> tc
>
> ________________________________________________
> See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail.
>
> PLUG-discuss mailing list - PLUG-discuss@lists.PLUG.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)