SAMBA error connecting to host:139 (Invalid argument)

[Tom Jackson]

Hi:

Can someone please tell me how to get samba to function???????

I've been struggling. I tried executing the DIAGNOSIS.txt and get the following error when I smbclient -L HOST:
error connecting to 148.98.133.208:139 (Invalid argument)

What does this mean? How do I fix it? Why is samba such a pain????

Tom

[Mark Greene_1]

from man smbclient:

" -L This option allows you to look at what services are available on
a server. You use it as "smbclient -L host" and a list should
appear. The -I option may be useful if your NetBIOS names don't
match your tcp/ip dns host names or if you are trying to reach a
host on another network."

and for the -I option:

" -I IP address
IP address is the address of the server to connect to. It should
be specified in standard "a.b.c.d" notation.

Normally the client would attempt to locate a named SMB/CIFS
server by looking it up via the NetBIOS name resolution mechanism
described above in the name resolve order parameter above. Using
this parameter will force the client to assume that the server is
on the machine with the specified IP address and the NetBIOS name
component of the resource being connected to will be ignored.

There is no default for this parameter. If not supplied, it will
be determined automatically by the client as described above."


so try using the -I in conjunction with the -L option.

HTH
mark

[Tom Jackson]

Hi Mark:

Thanks for the reply. -I didn't change anything. Here's the complete error:

./smbclient -L cathm208
added interface ip=148.98.133.208 bcast=148.98.133.255 nmask=255.255.255.0
error connecting to 148.98.133.208:139 (Invalid argument)
Connection to cathm208 failed

Here's what my smb.conf looks like:

[global]
workgroup = rls
server string = Samba Server
log file = /var/opt/samba/log.%m
max log size = 1000
security = user
encrypt passwords = no
socket options = TCP_NODELAY
local master = no
read only = no
preserve case = yes
short preserve case = no
dos filetime resolution = yes
syslog = 0
[homes]
comment = Home Directories
[tmp]
path = /tmp
[rls]
path = /208data2/rls
writable = true

I'm using inetd to start samba.

Tom

[Mark Greene_1 · Accepted solution]

what is the line from the inetd.conf file that starts smbd? and, have you tried adding the -d 1 option to that to turn on debugging? perhaps then you will get a more informative error message.

mark

[Tom Jackson]

Hi Mark:

You're on the right track...
I removed the entries in /etc/services and /etc/inetd.conf and started the samba as daemons and I'm listing available shares.

Now I'm trying to connect from a windows nt box and I'm getting:

System error 86 has occurred.

The specified network password is not correct.

I tried setting the password with smbpasswd, but that didn't help.

Tom

[Mark Greene_1]

do you need to specify the nt domain in there somewhere too?

mark

[U.SivaKumar_2]

hi,
hope you won't mind attaching your smb.conf.
regards,
U.SivaKumar

[Tom Jackson]

Hi again:

I'm still having problems connecting from NT. I modified the registry by executing NT4_PlainPassword.reg. I have the same user ID and password on the client and server. I get the following error when I execute "net view cathm208":
System error 5 has occurred.
Access is denied.

And I get this error when I execute the "net use" command:
System error 1240 has occurred.
The account is not authorized to login from this station.

Please see the smb.conf in my previous message.

Tom

[Sandra Skinner]

The error regarding not able to log in from this workstation is indicative of issues with password authentication. With user level security, I would suggest changing in the smb.conf file

encrypt passwords = yes

and creating a smbpasswd file entry in

/opt/samba/bin/smbpasswd -a unixusername unixuserpassword

or if you decide to leave

encrypt passwords = no in the smb.conf file, then please refer to these to Microsoft articles to help change the registry for your clients with unencrypted passwords. For NT please refer to article Q166730 and for WIN2000 the article is Q244627

I hope this will help.
Sandra

[Tom Jackson]

Yee Haw!

It finally works!

I set the workgroup on the PC, then turned on password encryption, and presto. (:-)

Thanks to Sandra and Mark for your help and inspiration.

Tom