----- Original Message -----
To: Schools List <suse-linux-uk-schools(a)suse.com>
Sent: Friday, November 10, 2000 9:45 AM
Subject: [suse-linux-uk-schools] Samba logins and IP/NetBeui (Was: The
secret diary ...)
> One aside, the Windows machines would typically
> install windows networking (SMB) onto NetBeui
> *and* TCP/IP as the underlying protocols. Samba
> only supports TCP/IP.
> It is possible to remove NetBeui on *all* Windows
> machines and the server - and just have one
> network protocol running on your network - ie
> all machines just talking IP.
Definitely do not do this if you are running RM Connect as that does use
NetBeui. In fact, if you followed Kevin's excellent "If it ain't broke fix
it" advice you most probably wouldn't be bothering to remove it.
> I am not advising this though - unless you know
> that you have no machines that only talk NetBeui
> (ie not IP) - and that all machines are configured
> for IP. It is something else to think about though
> as life can often be simpler if you only have one
> network protocol on your system.
> This is not an important point though - and if
> everything is working, then 'ain't broke, don't
> fix' probably applies ... :-)
I'm trying to synch my Win and Linux passwords but I'm having problems debugging my passwd chat. I'm using SuSE 6.3. with my Linux box as a domain master.
All passwords are encrypted. smbpasswd is populated Win password caching is off(relevant?)
Initial logon Ok and shares accessible.
This is what I see when I use passwd at the console. (The following done as root)
New password (again):
passwd program /usr/bin/passwd %u
passwd chat *New*password* %n\n *New*password* %n\n *changed*
unix password sync Yes
Invoking '/usr/bin/passwd sand' as password change program.
talktochild: chatbuf=[*New*password*] responsebuf=[New password: ]
talktochild: sendbuf=[sandstorm ]
talktochild: chatbuf=[*New*password*] responsebuf=[New password (again): ]
talktochild: chatbuf=[*changed*] responsebuf=
[2000/11/10 09:40:08, 3] smbd/chgpasswd.c:talktochild(266)
response 3 incorrect
[2000/11/10 09:40:08, 3] smbd/chgpasswd.c:chat_with_program(316)
Child failed to change password: sand
Thanks in advance for any suggestions. Apologies if it's anything obvious.
Ysgol Glanymor School
Llanelli SA16 0AL
Tel 01554 832507
Fax 01554 832424
By default samba uses plaintext passwords.
The newer flavours of Win (and NT) encrypt their passwords resulting in what
your experiencing (I too was caught out..for many fruitless hours!)
There are solutions
You can hack the Win registry (on every machine that is to access samba) so
that it uses plaintext passwords
or you can amend samba config to use encryption.
This involves creating and populating a smbpasswd file(separate to the
normal passwd file)
Have you allowed the SWAT service on port 901 in your services file. It was not enabled by default on my system (SuSE 6.3)
Hope this is some help
Ysgol Glanymor School
Llanelli SA16 0AL
Tel 01554 832507
Fax 01554 832424
Thanks for the continued useful comments
Its probably only my impatience to get things moving that is causing me
When you only sitting at the Linux machine in snatched moments between
lesons its difficult to build up any sort of momentum
Things seem to be progressing.
I installed Tera Term Pro on the PC and managed to TelNet to the server
(including changing back up to su(root). I fiddled round with smb.conf
directly and managed to get a share appearing in Networkwork
neighbo(u)rhood but it doesn't seem to like my passwords...?!!!
I think you are right about the Netscape problem with localhost:901. When
the ISDN lead was plugged in it took me onto the web???!!!!!
Maybe I'll know more when I run ifconfig tomorrow
p.s yes reply was supposed to go to list so here it is below if it helps any
other newbies out there.
p.p.s Just received copy of Running Linux
BOL was cheapest online (£19 inc p&p)
> > I haven't run the suggested commands yet but I know the ISDN card and
> > ethernet card are installed and recognised.
> Thats the first stage then. Sounds like you need to try the
> 'ifconfig' commands next. If you let me know the following
> information for *both* your machines :
> IP Address
> Subnet mask
> Default router (sometimes called gateway)
> This is basically the output of the ifconfig command on Linux.
> In windows, this is Control Panel->Networking->Protocols->TCP/IP
> (or something like that).
> I gave the eth card an address of 192.168.1.1
> > Do I need to add anything to smb.conf before I can link from a PC?
> You need to configure Samba - either using linuxconf, SWAT
> or man smb.conf ;-)
> > Do I need to set up some sort of nameserver file?
> You will need to do name resolving - but lets get the
> basic IP numbering/networking sorted first.
> > I have noticed on boot up that it is flagging a FAIL
> > against Routing services.
> Sounds a bit suspicious. Will know more after the
> output of ifconfig.
> > I tried going into SWAT on Netscape at localhost:901 but after thinking
> > a while I was told that Netscape could not find Keywords.netscape.com
> > something similar)
> Sounds like netscape was trying to perform a search for
> SWAT by going to the netscape Internet site ... don't know why.
> A good book to have/read is the Network Administrators
> Guide (either on-line or the hardcopy O'Reilly book) -
> see http://www.linuxdoc.org/ or http://www.ora.com/
> (by the way - did you mean this to come just back to me and
> not to the list ? If we carry on the conversation on the list, there
> may be things we talk about that can help other people ...)
Thought some of you may be interested to know that the
XDM/X Terminal mini Howto has been updated.
I have revamped some of the wording to make things
(hopefully) a little clearer. I have also started a section
describing common configurations and updated the
references. Thanks to everyone who commented
on the first version.
As always comments are welcome on this new one too.
> > > However, if thin Ethernet avoids needing a hub, this
> > > may be viewed more favourably by my budget-holding bosses!
> >Thin Ethernet is a pain - which is why people are
> >chucking it out (bend the cable a few times and
> >you could bring down the whole network).
> >UTP would be the way to go.
> Excellent - I'll head that way then!
This is very good advice - thin Ethernet, just don't go there. we had it
here on our admin net, yep it's cheap, but you get what you pay for -
trouble! It took lots of tweaking before it settled down.
We have a Gb back bone and loads of flashy kit here (had to sweet talk the
bursar and hassle several firms (all out of favours with the bursar now!)),
but at one of our feeder schools I have set up a 10 machine network with
patch leads, a couple of palm hubs (dirt cheap) and some sticky back
trunking. It works well enough at 10Mz
If you can't do it, most local PC shops will make leads to any length - The
usual max length of a patch lead is 10M (this is laid down in the CAT5 Spec
- Does anyone know if this is different for CAT5E or CAT6 ?)
If you can find a local firm who will 'fluke' your system for nothing, go
for it. If you KNOW that the cabling is sound, it will cut down the time it
takes to diagnose any faults. You don't need any unknowns! :-)
PS if you have any crossover leads, make sure that they are clearly labeled
as such, otherwise they WILL trip you up in the future.
Oakridge Lane, Winscombe, Somerset BS25 1PD.
Please reply to
admin(a)sidcot.org.uk for general enquiries
> However, if thin ethernet avoids needing a hub, this
> may be viewed more favourably by my budget-holding bosses!
Thin ethernet is a pain - which is why people are
chucking it out (bend the cable a few times and
you could bring down the whole network).
UTP would be the way to go.
You could start with 2 nodes talking point to
point, using a UTP cross-over cable (ie
no hub would be required).
Eventually, you need to either :
- Plug into your existing hub(s)
- Buy a new hub to plug into your existing hub
I would recommend staying with the type
of kit you already use (assuming that it is
ok) - it just simplifies things in the long run.
Let us know when you get things hooked
together, and we can chat again ...
I'd personally attempt to avoid thin ethernet (10Base2 - which is 50
ohm co-axial cable with locking BNC connectors on the end - similar but
not the same as TV co-axial and the cable is very different
electrically so *never* attempt to use TV cable for this). 10Base2
works fine when it works... when theres a problem its very difficult to
isolate just where the problem is - a single poorly wired connector can
make a machine at the other end of the cable misbehave for example.
Basically 10Base2 is unsupportable in a hostile environment - such as a
You can get 10/100BaseT PCI cards (twisted pair cabling with RJ45 plugs
on each end - RJ45 are 8 way plugs made of clear plastic with a central
locking clip on the opposite side of the plug to the connectors. They
are similar to BTs phone plug but not the same or interchangable) for a
cost of less than 10 pounds per card. Choose your cards relatively
carefully as some types are more supportable and reliable under linux
than others (I would give a specific card recommendation but I don't
have web access right now). These cards have 100BaseT capability which
might be useful later
You need a hub for more than 2 10/100BaseT devices. Cost of this is
roughly the same per-port as cheap cards. Unfortunately for your 25
machines thats looking like around 500 pounds plus the cable itself.
BTW for those just setting up a small network, with ISDN network
access, look carefully at the small office networking kit - ie DLink
206 ISDN router, which does DHCP and provides external access etc and
has an embedded 10BaseT hub for just over a hundred quids.
[ - Opinions expressed are personal and may not be shared by VData - ]
[ Nigel Metheringham Nigel.Metheringham(a)VData.co.uk ]
[ Phone: +44 1423 850000 Fax +44 1423 858866 ]
> Now what do I do? :o)
I am not quite sure how far you have got ?
Do you have a physical network installed ?
Do you have a working IP network between the machines ?
Have you looked at Samba yet ;-)
These are the 3 stages - let us know where you
are, and we can take them one at a time.
>From your comments, I think you are at the first -
if so, what type of physical network connection
do you have on your cards ?
Twisted Pair ? (Phone type sockets on the cards)
Thin ethernet ? (BNC connectors on the cards).
For twisted pair, you need a TP hub (approx
30 to 50 quid for a cheap one with 4 to 8 ports).
For thinnet, you need lengths of thin ethernet
cable and 2 terminators.
Many places are throwing out thin ethernet and
replacing it with twisted pair - so depending on
your level of playing, and how much money you
want to spend right now - you may be able to
pick up some thin ethernet - or alternatively,
invest in a hub - but we need to know what sort
of network cards you have installed.
Books to consider :
Network Administrators Guide (LDP and ORA book)
Samba (ORA book - also available online).
Ethernet Howto (LDP)
I am an ICT Co-ordinator (ex network manager) at The Romsey School. We
use Linux for web serving and proxying but its RedHat. I'm testing the
SUSE 6.4 at home before swapping over to using that instead of RH6.1.
I have installed ROX filer on it so we get a RISC OS look alike filer.
Its pretty good and I feel more comfotable with its drag and drop
Has anyone else tried this or need help doing so ?
Its available via :-
Colin McQueen : Using an Acorn StrongARM Risc PC
Web Domain : http://www.mcqueen.uk.net/
BSc Zoology + Oceanography : PGCE : MSc in CBL/T