>
> What I'm trying to achieve is that the filesharing and ICS should be
> transparent to the kids - they shouldn't need to know which OS I'm running.

Quite right. A Samba server will look just like an NT server to the other 
computers.

>
> Currently, we run a MS peer-to-peer network, with my W2K box acting as
> gateway.  I have read that it is notoriously difficult to set up Samba
> if NETBUI is installed (which it is on the W98 m/cs), and one should get
> rid of it if at all possible.

True: Samba does not work over NETBEUI  The Windows computers must have the 
TCP stack installed, and there should be a binding between TCP/IP and 'Client 
for Microsoft Networks' service  in the Windows Network Control Panel. It 
does not matter if you remove Netbeui or not.(Right click on the TCP/IP 
protocol in the Windows Networking control panel, and select 
'Properties>Bindings')


>
> Unfortunately, it doesn't seem to be possible, as without it the W2K
> machines and the W98 machines cannot see each other.

Take a look at that binding. 

>
> TCP/IP is on all m/cs, and is properly set up, as the W98 m/cs connect
> to the Internet from my W2K m/c over TCP/IP.
>
> I wonder, too about m/c names.  Under the peer-to-peer setup, no name
> server is required.  I don't see how a hosts list can be set up when two
> m/cs have static IP addresses and the other two have dynamic (provided
> by my m/c).  We haven't used either DNS or WINS.  This sets me to
> thinking about host names on Mdk - I haven't set this up, I think, and I
> guess I need it?  How can Samba recognise and authenticate a m/c without
> DNS?  And how could I set up DNS with m/cs that don't have a static IP
> address?

Samba does not need the hosts table or DNS to find Windows computers. The 
Windows machines will respond to a broadcast poll and identify themselves 
with the name you define in 'Identity' in the Windows Network Control Panel
You only need a hosts table or DNS lookup when you want to refer to a remote 
machine with a meaningful name instead of an IP address. So for example
'ping micky' requires the host name Micky to be either in the /etc/hosts 
table, or able to be looked up in a DNS server, or searchable in the 
localdomain.  It is_permissable to have 1 machine with a static address while 
the others are dynamic so long as the static address is known to the DHCP 
server so it does not award the same IP address to someone else, and so it 
can resolve searches to that host.  You are best off however just defining 
your Linux computer to use DHCP and let your Win2k machine serve an IP 
address to it. You should also define the win2k machine to be the 'default 
gateway' for the Linux computer, and set your ISP's DNS server addresses so 
that the Linux computer can resolve names on the Internet.
A convenient GUI to set this all up in is 
KMenu>Configuration>Networking>netconf


>
> I have a feeling that there are lots of things like this that I will
> have to set up.  I forgot that this will not be peer-to-peer, but in
> fact I will be using this m/c as a server - and I didn't specify that at
> installation.  Yet I was offered the ICS option?
You did not select Internet Connection Sharing did you?
You select that if the Linux machine is the gateway. You are using Win2k as 
the gateway aren't you?



>

BTW: Did you see this 
http://www.mandrakeforum.org/article.php?sid=2169&lang=en

It should help you access Windows shares from Linux which is a lot easier 
than the other way round. Note komba2 is recommended.

derek




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to