[NTLUG:Discuss] AT&T@Home redux

Ian Pilcher pilcher at concentric.net
Wed Mar 7 00:17:17 CST 2001


Thanks to all who responded.  Unfortunately, the responses are as
contradictory as they were the first time this topic came up on this
list.  To try to bring some focus to this discussion, here's my summary
of what I've been able to gather.

First off, I verified this issue by booting Windows 2000 on my laptop
and inserting the Ethernet adapter, which was already configured to use
DHCP -- no IP address.  I then changed the "Computer Name" to that
provided by AT&T and got an IP address.  The "Computer Name" was
the only change I made to the system; I did not install any of the
@Home software.

This issue is almost certainly limited to certain @Home areas, probably
those which have been rolled out more recently.  Therefore, I would ask
that people verify that @Home behaves similarly in your area (i.e., that
it depends on the Windows "Computer Name") before posting an "it works
for me" response.  Otherwise, it just confused things.

For those people who have possible solutions, either Samba or DHCP
related, please be specific about what you did to get things working --
what files you editted or what tools you used to make the changes.  As
a starter, here is the smb.conf which I tried last night:

    [global]
        netbios name = {AT&T supplied name}
        server string = Team Fax Server
        security = SHARE
        print command = lpr -r -P%p -U%U@%M %s

    [printers]
        comment = All Printers
        path = /var/spool/samba
        guest ok = Yes
        printable = Yes

(This is a holdover from a project I had previously worked on.  The only
change I made was the NETBIOS name.)

I'd like to make this a constructive conversation.  If I can figure this
out, I'll gladly put together a quick HOWTO, which should benefit a lot
of people.

Thanks!

-- 
========================================================================
Ian Pilcher                                       pilcher at concentric.net
========================================================================



More information about the Discuss mailing list