[NTLUG:Discuss] argh! using nmbd for that stupid @home service

[Rob Holland]

Given the diversity of the responses so far, I wonder if different parts of
the @home network are configured differently (some use DHCP, some don't ?)

Anyway, I got @home installed a couple of weeks ago in Flower Mound.  My
machine is dual boot Windows 98 and Red Hat 6.2.  They configured it in
Windows 98.  I simply extracted the necessary information from the Windows
setup and entered it into Red Hat, and everything worked fine.  Step by step
in Red Hat:

login as root
system menus --> system --> linuxconf
config
    networking
        client tasks
            basic host information
                hostname tab
                    hostname: gatewayg6350 (this doesn't impact the @home
config)
                adapter1 tab
                    enabled: yes
                    config mode: manual
                    primary name + domain: cXXXXXXX-a.flrmnd1.tx.home.com
(my @home-assigned name)
                    aliases: cXXXXXXX-a
                    ip address: XX.XX.XX.XXX (my @home-assigned address)
                    netmask: 255.255.255.0
                    net device: eth0
                    kernel module: tulip (because I have a Linksys card)
            name server specification (DNS)
                default domain: flrmnd1.tx.home.com
                ip of name server 1: 24.4.48.35
                ip of name server 2: 24.4.48.36
                search domain 1: flrmnd1.tx.home.com
            routing and gateways
                set defaults
                    default gateway: 65.10.18.1
quit
activate the changes

I do not have any Samba services running.

----- Original Message -----
From: "Michael B. Lee" <mlee at loopstart.com>
To: <discuss at ntlug.org>
Sent: Thursday, January 25, 2001 8:51 PM
Subject: [NTLUG:Discuss] argh! using nmbd for that stupid @home service


>
>
> HOW exactly did you manage to use their assigned name? I can't get it
> going. I know it's not my linux box or the eth card in it (I was using the
> same machine just fine today on another network, and was using that same
> card to receive a DHCP address.
>
> But when I plug it into that cable modem, it won't dhcp anything off of
it,
> most likely because it's not finding that silly NETBIOS name it's looking
for.
>
> I've tried renaming my hostname to the @home name, as well as:  nmbd -D -n
> [@home name]
>
> Linux seems to take that line, but then I still can't bring eth0
up!!!!!!!!!
>
> Help!!!!!!
>
>
>
>
>
>
> At 06:05 PM 1/24/01 -0600, you wrote:
> >When I had a cable modem, I had to use their assigned name initially to
get
> >things to connect.  Once an initial connection had been made, I changed
the
> >hostname to my domain name and it worked fine.
> >
> >On Wed, Jan 24, 2001 at 11:15:10AM -0600, Michael B. Lee wrote:
> > > I just noticed something odd about AT&T's @home cable service. Unless
it
> > > finds the Windows computer name they assign you, it won't work.
(Network
> > > Neighborhood --> Identification --> Computer name).
> > >
> > > So, if I'm going to run my LINUX box over the cable service, how do I
> > > replicate that computer name in LINUX? (Where do I configure it?). I'm
> > > using the Red Hat 7.0 distribution, if that makes any kind of
difference.
> >
> >--
> >Tom Hoover N5NTM <tom at hisword.net> - http://www.hisword.net/tom
> >     - checkout HisWord(tm) Palmtop Bible at the above URL -
> >      ------- finger thoover at pobox.com for PGP key --------
> >_______________________________________________
> >http://ntlug.org/mailman/listinfo/discuss
>
> _______________________________________________
> http://ntlug.org/mailman/listinfo/discuss