Computing.Net > Forums > Linux > Linux as client on NT network

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Linux as client on NT network

Reply to Message Icon

Name: David Krings
Date: August 9, 2001 at 08:04:28 Pacific
Comment:

I have a Linux box (hostname Lslinux) that I want to be able to access ressources on out NT network and vice versa. I installed samba and have the following smb.conf
[global]
workgroup = HARROW ;our NT domain
encrypt passwords = yes
domain logons = yes

[david]
comment = just a test
path = /home/david
read only = no
guest ok = yes

#end of smb.conf

I can see the linux machine in the network neighbourhood, but I cannot access the defined share (error "\\Lslinux is not accessible. The network path was not found"). Neither can I smbmount any other share on our network from Linux. We use DHCP and I can ping each other client, but a ping using the hostname fails. I do not want the Linux machine act as server, only as client. What am I doing wrong ?




Sponsored Link
Ads by Google

Response Number 1
Name: mike blum
Date: August 9, 2001 at 10:31:27 Pacific
Reply:

You should provide some more information, Linux version, kernel, samba version...
In the global section of smb.conf, what is security set to ?

If you can't ping by name there is something wrong in general.


0

Response Number 2
Name: David Krings
Date: August 9, 2001 at 12:04:55 Pacific
Reply:

Linux version RedHat 7.1
kernel 2.4.2
samba version 2.0.7

Currently there is no security entry in the [global] section

I set the hostname to lslinux, the domainname to HARROW (as it is in the NT network). I guess that should make the machine be able to be pinged by hostname.


0

Response Number 3
Name: mike blum
Date: August 9, 2001 at 12:31:15 Pacific
Reply:

Hi,
I use the same samba version and it works fine in the office and at home.

There must be an entry for security= user or share or server or domain !!!
I prefer security=user.

You should make linux accounts for all users and make smbpasswd's.

You can do it with linuxconf (I'm not familiar with red hat) or with useradd.
The useradd tool is on all distros.
example:
useradd -G users user123

you will be asked for the password twice.
Now you have a new user named user123 in the group users.

smbpasswd -a -e user123
put in the same password. The option -a means add, the option -e means enable.

If you make user accounts with useradd, they will have no home dir.
I use SuSE and if I create a new user with yast (like linuxconf) I can check if you want a home dir or not.


0

Response Number 4
Name: David Krings
Date: August 9, 2001 at 13:14:44 Pacific
Reply:

I added a new user account using the same user name and password as I use it for the NT network (afaik it shouldn't matter if it is different). I added this user with smbpasswd -a -e username, but was not asked for any password. Does smbpasswd take the linux password when a user is added ?
I also added security = user to the smb.conf and for sure restarted samba to get the new settings used. Nevertheless I still cannot contact to the linux box, NT tells me that the network path is not found. My guess is that the link between name and IP is missing. So I tried accessing the share using the IP address of the linux box, which should leave the name problem out, but it still does not work. Any other clues ? May there some restriction by the NT server based network ?

Besides that, is there someone in central Connecticut who would like to give me hand with Linux ? Books are nice, but don't answer the stupid questions.


0

Response Number 5
Name: mike blum
Date: August 10, 2001 at 04:18:23 Pacific
Reply:

I would bet your samba is not installed properly. Samba cannot read the encrypted
shadow password, so it needs its own password database.
If you use smbpasswd, you should get
New SMB password:
Retype new SMB password:
Added user ******

Check the basics:
In /etc/services these 2 lines:
netbios-ns 137/udp # NETBIOS Name Service
netbios-ssn 139/tcp # NETBIOS session service

in /etc/inetd.conf :
netbios-ssn stream tcp nowait root /usr/local/bin/smbd smbd
netbios-ns dgram udp wait root /usr/local/bin/nmbd nmbd

testparm can check your smb.conf for syntax errors.

Next simple check on your samba server:
smbclient -L localhost

Added interface ip=192.168.200.99
bcast=192.168.200.255
nmask=255.255.255.0
Password:
Domain=[SSP_GL] OS=[Unix] Server=[Samba 2.0.7]
....
....
and more...

Name resolving isn't the issue, you can connect to the share via IP (at least with
NT, Win95 doesn't do the trick)
If you can't ping by name, check your DHCP.



0

Related Posts

See More



Response Number 6
Name: David Krings
Date: August 10, 2001 at 05:39:12 Pacific
Reply:

First of all thank you very very much that you spend your time helping me. :)

I checked /etc/services and the following lines are included:

netbios-ns 137/tcp
netbios-ns 137/udp
netbios-ssn 139/tcp
netbios-ssn 139/udp

I do not have a file /etc/inetd.conf (RedHat special ?), the only inetd.conf I found was under the webmin dirs (3 of them). Shall I create an inetd.conf in /etc with these lines ?

I executed testparm and testparm told me that the /etc/samba/smb.conf is OK. But the dump of the service definitions looks entirely different than the smb.conf. The dump has far more lines, some options are not set (e.g. netbiosname). Does the dump show the actual conf file or all possible configurations ?

Nevertheless I checked samba with smbclient -L localhost and get the following:
SSL error setting CA cert locations:
error:00000000:lib(0):func(0):reason(0)
trying default locations
added inetrface ip=10.44.126.76
bcast=10.44.127.255 nmask 255.255.252.0
Password:********
session setup failed: code 0

I guess I am not supposed to get any error messages. What does this error message mean ?

Hmm, afaik takes DHCP the name I entered as hostname (in my case lslinux), I can even see the machine in the network neighbourhood under NT, but cannot connect to it.


0

Response Number 7
Name: mike blum
Date: August 10, 2001 at 09:22:46 Pacific
Reply:

The testparm dump is OK, samba has a lot configuration entries which are set to defaults.
Red Hat is different to SuSE, maybe I can look it up in a book at home.

SSL is Secure Socket Layer, but I don't know what the message means.
Why do you use these IPs? With the netmask you get a hostrange from
10.44.124.1 to 10.44.127.254 that means a max of 1022 hosts !

Is 10.44.126.76 the Linux IP ?

The global section of a very simple smb.conf, put in your IP:
[global]
workgroup = HARROW
guest account = nobody
keep alive = 30
os level = 2
security = user
encrypt passwords = yes
interfaces = 192.168.200.99/255.255.255.0
wins support = no

You have: domain logons = yes
Do you really want this ?
Your Samba will act as a logon-server for your domain.

Last question: Is the linux set up as DHCP client ?


0

Response Number 8
Name: David Krings
Date: August 10, 2001 at 11:00:02 Pacific
Reply:

I don't know why we use these IPs and this network setup, I may ask our network admin. I got the IP through DHCP.
10.44.126.76 is the Linux IP

I understood sth wrong with the domain logons, I thought it was to allow anyone from the domain to log on. I took it out again, that may be healthier for the system.

I set eth0 to use dhcp and entered as hostname lslinux. Do I have to enter only the hostname or the hostname + domainname ? Is there anything more to setup to be a dhcp client ?

I also tried your smb.conf and changed the IP to my local values which I confirmed with ifconfig. Again, the linux box shows up in the network nbhood, but cannot be accessed (network path not found), same when using IP address.

I also tried to run smbstatus, there i get an error stating "Failed to initialise locking database".

I also checked the hosts file and the name and IP address is in there correctly, although does this file matter for dhcp ?

How can I test if the linux box is correctly configured as dhcp client ?
How can I make sure that the name of my linux PC is added to the hosts file on the network (or whatever is used by NT for identification)?
Is there a way to determine if samba is really up and running ?
Do you know of a source where to get standard smb.conf files ?

*sigh* starting to get a bit frustrated here.


0

Response Number 9
Name: mike blum
Date: August 10, 2001 at 14:40:16 Pacific
Reply:

Yeah frustrating! Did you install the original rpm from the distro ?
I always ran the packet just out of the box, from SuSE, in the office and at home, even updated once or twice and never had any problem!

You can check (as root) if the both daemons are running with
ps ax | grep -w nmbd
ps ax | grep -w smbd

you should get something like
172 ? S 0:00 /usr/sbin/nmbd -D
174 ? S 0:00 /usr/sbin/smbd -D

You can try to start the daemons by hand with
/usr/sbin/smbd -D -s /etc/samba/smb.conf
/usr/sbin/nmbd -D -s /etc/samba/smb.conf

Check the logs, linux does log each and everything, like /var/log/messages and
/var/log/log.smb or log.nmb


0

Response Number 10
Name: kapil
Date: August 16, 2001 at 06:41:40 Pacific
Reply:

I'm using redhat6.2 & samba version 2.0.6. this system is on Lan where we have WinNt, Win2k Professional, Win2k Advance Server(which the Primary domain Controller).

Now, i've added the Linux box on the same network and i installed the samba rpm.

Currently i'm using the Linux Box as a Workgroup and not as a Domain Client.But i want to make as a Domain Client as other systems on the Lan How to make this possible ?

Another problem i cannot see smb service as smb -D where as i can see nmb service as nmb -D.What difference it can make if it is not displaying as smb -D.

But i can access the Linux box.



0

Response Number 11
Name: David Krings
Date: August 20, 2001 at 07:29:22 Pacific
Reply:

I finally went the radical way, ripped out the entire Linux installation and started from scratch. This time I edited the smb.conf that came with samba and voila it works - sort of. I can see the linux box, i can ping it by name, and I can access the shared directory. The section of smb.conf for this share looks like this:
[sharedir]
comment = Shared Dir
path = /home/samba
valid users = ls_dxk
public = yes
writeable = yes
printable = no

ls_dxk is my network account, I successfully added it to smbpasswd and used the correct logon password. Still I cannot write to this share from my NT workstation. Isn't writeable = yes supposed to allow that ?


0

Response Number 12
Name: David Krings
Date: August 20, 2001 at 07:48:22 Pacific
Reply:

It is nice when I can answer my own questions. The shared dir had only write access for root, but not for me as user. I fixed that with a chmod 777 /home/samba, and now it works exactly the way I want it to. One more happy camper. :-))))
Thanks to Mike for all your help.


0

Response Number 13
Name: Lee Hoay Fern
Date: October 28, 2001 at 23:50:34 Pacific
Reply:

Hi,

currently i have linux-redhat as client, i have winnt as primary domain.

my question:

1) how can i set the linux-redhat as client and logon to winnt ?

wat r the steps i need to configure in linux-redhat
please assist

hoay fern


0

Response Number 14
Name: Manish
Date: December 4, 2001 at 03:30:33 Pacific
Reply:

So Devid King,

What is the exact solution of error...
"network not found..."
Please tell me in brief.


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Linux Forum Home


Sponsored links

Ads by Google


Results for: Linux as client on NT network

Linux & Windows servers on same network www.computing.net/answers/linux/linux-amp-windows-servers-on-same-network/7334.html

Putting Linux on NT network www.computing.net/answers/linux/putting-linux-on-nt-network/1261.html

Linux on NT network www.computing.net/answers/linux/linux-on-nt-network/14619.html