Rudolf Kollien
email: Rudolf.Kollien@medas.de
Rudolf.Kollien@kollien.de
***************************************************************************
Never trust a operating system you have no sources for
***************************************************************************
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
***************************************************************************
For the NSA only: bomb drug shit terror islam attack
-----Urspr?ngliche Nachricht-----
Von: Rudolf Kollien [mailto:Rudolf.Kollien@medas.de]
Gesendet am: Freitag, 4. Dezember 1998 17:22
An: fwo@gcal.ac.uk
Betreff: AW: Windows 3.1 and Samba
Works great on all versions of samba. For WFWG you need the MS-TCP/IP-32
(not part of WFWG). For W3.1x without workgroup enhancement, i don't now
which software you need. I guess the DOS Lanman-Package.
With samba set to encrypted pwd you even can login to the samba (NT) domain
to. Logon scripts execute well.
Attached i send you the latest TCP/IP for WFWG (not included in the mail to
the list). Use the "network setup" of WFWG to add the protocol (Add
protocol -> have disc etc).
Rudolf Kollien
email: Rudolf.Kollien@medas.de
Rudolf.Kollien@kollien.de
***************************************************************************
Never trust a operating system you have no sources for
***************************************************************************
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
***************************************************************************
For the NSA only: bomb drug shit terror islam attack
> -----Urspr?ngliche Nachricht-----
> Von: samba@samba.org [mailto:samba@samba.org]Im Auftrag von Frank Wornle
> Gesendet am: Donnerstag, 3. Dezember 1998 16:19
> An: Multiple recipients of list
> Betreff: Windows 3.1 and Samba
>
> Has anybody got some experience with connecting machines running
> Windows3.1
> or WfWG (3.11) to Samba? We would like to run a small lab network with
> user accounts and a shared printer off the samba box. Samba is
> running fine
> and there's no problem to connect to it from the Win95/WinNT
machines...
>
> Any help appreciated.
>
> Frank Wornle,
> Glasgow Caledonian University
> Dept. of Engineering
>
James,
i don't think so. It's not a problem of Win 3.x. I've got the same
problem
with Win95 and WinNT. I heard, this is a matter of some nic's. I tried a
couple of manufactures but the server isn't shown. I use the wins service on
all systems but it has no effect for the browselist. On my network at home i
can see (my own local) samba server. But at the corporate network i'm not
able to. May be because all servers use two nics. I don't matter above this
behavor. I can see the shares over the search option (Win95) or on WFWG via
entering only the desired server name in the connection box (don't append
any share name, use only \\SERVER. So you will see the shares).
Have a nice weekend
Rudolf Kollien
email: Rudolf.Kollien@medas.de
Rudolf.Kollien@kollien.de
***************************************************************************
Never trust a operating system you have no sources for
***************************************************************************
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
***************************************************************************
For the NSA only: bomb drug shit terror islam attack
> -----Urspr?ngliche Nachricht-----
> Von: Frank Wornle [mailto:fwo@gcal.ac.uk]
> Gesendet am: Freitag, 4. Dezember 1998 20:57
> An: Rudolf.Kollien@medas.de
> Betreff: Re: Windows 3.1 and Samba
>
> Rudolf,
>
> thanks for your prompt reply. I'm running WfWG 3.11 and I've added
> TCP/IP-32. So far everything works fine, I can use the supplied FTP and
> TELNET tools, however I can't map any network drives - the server
doesn't
> appear in the browse list (works for the Win95 machines on the same
> network). Could that possibly be some WINS problem (I've also enabled
> LMHOSTS and both the HOSTS and the NETWORK files on the WfWG machine
> contain info about the server's IP address...).
>
> Any idea what could be wrong?
> Thanks for your help anyway,
>
> Frank
> Glasgow Caledonian University
> Dept. of Engineering
>