What you are talking about is SAMBA. It's not that it's impossible it's
just that there is some planning and configuration that needs to be done on
both ends. First you should (or the MCSE's should visit ) www.samba.org all
of the doc's are there. Now you seem to imply that you want the linux box
to be a client to the NT box in the NT domain? If this is true then look at
this doc about Joining an NT domain with Samba 2.0
Another thing is encrypted passwords, look into that.
As a word of caution, MS networking doesn't play nice with others, in other
words what is "OK" in MS networking doesn't always work in the pure TCP/IP
way of doing things. I've seen some messy NT Domain's that require days of
work to "fix" too get them to work the way TCP/IP is meant to be used. Two
examples, one-name computer names, (i.e. Sally has a PC with the IP
192.168.55.27 and the name of sally, not sally.ntdom.com) and spaces in the
computer name (i.e. kit gloves) I know that Most MCSE's wouldn't allow this
due to "best practices" but I've seen it and it's not good if you have to
deal with it. Windows networking in general allows for sloppy
configuration, which just doesn't cut it for pure TCP/IP networks. The
reason for this is in part due to NetBIOS, but is also helped along by MS
things like WINS, and NetBEUI. I've seen a configuration that I was
consulting Client on, they had an NT server that had TCP/IP and NetBEUI
configured. The company I worked for at the time had a pure TCP/IP
client/server product on the Clients system. The complaint was that this
product was giving flaky performance. The Client kept pointing there finger
at us, because they could xfer files between the NT server and the windows
clients but our software was taking hours to do 15 minutes worth of work.
To top it off some of the windows workstations didn't even connect between
our client/server software. First thing they had wrong, running NetBEUI.
Because NetBEUI provides NetBIOS level linkage between all of the Microsoft
boxes that made it seem like the problem was with our software. First thing
I did was told everyone that I know what the problem is and to prove it
when I turn off NetBEUI on the server every thing will stop working. It
did. Next thing no name resolution, they where running with an out of date
and typo ridden hosts file. Next thing hostnames, or NetBIOS names with
spaces in them, bad, bad, bad, not going to work. The last thing I can
remember I found was that they we're using a class B TCP/IP network number
on the server and class A netmasks on the client boxes. I'm sorry if this
was more then you wanted to know but I just started getting into this whole
thing and I started remembering all stuff that can go wrong.
Seth
At 05:46 AM 7/21/99 -0500, you wrote:
>Is there any one there that knows how to use linuxconf to set up windows
>connectivity -- I have seen 3 MCSE people try for 2 hours! It should not, can
>not be that impossible!
>
>All I want to do is share a couple of folders to everyone and access my user
>folder in the nt box. I have Linux Mandrake 6.0 and I have run the update so
>everything should be the latest supported version.
>
>In nt the values are:
>Domain: ASG
>computer name: mandrake
>wins: 209.240.84.14
>
>Share : /home/ftp
>
>I added this to the obvious places in linuxconf, and now it appears in the
>brows list in the domain. However, when ever I double click on the icon in the
>network neighbourhood i get the error: network path can not be found
>
>It is there i can see it, ican ping it...
>
>I can log on from other windows machines...
>
>help!
>stephan
>
>
>___
>Stephan Schutter [EMAIL PROTECTED]
