Yet Another Stupid Samba Problem [SuSE 8.1]

shassouneh · 02-01-2003, 03:33 PM

Hi All,
Before flaming me, please note that I DID search the forums and the archives and read quite a bit about Samba and its setup. I also re-read my own posts looking for ideas, but even after all of that I am still having problems. So bear with me.

OK. Things you should know:
distro: SuSE Linux Professional 8.1
samba version: samba 2.2.5
LinNeighborhood version: 0.6.4
network setup: two machines on a 10 base T hub (as simple as it gets)
OS summary: one Windows XP Professional Machine. One SuSE L:inux machine
smb.conf file: HERE
Workgroup: Workgroup

Description of the problem:
I cannot get either machine to see the other on the network. Both machines are on the orkgroup "Workgroup", and LinNeigborhood is also configured to scan that group. If I use smbclient -L <ip> it gives me some results, as follows

Code:

samer@host12:/etc/samba> smbclient -L //208.152.2.199
added interface ip=208.152.5.12 bcast=208.152.5.255 nmask=255.255.255.0
session request to 208.152.2.199 failed (Called name not present)
session request to 208 failed (Called name not present)
Password:
Anonymous login successful
Domain=[WORKGROUP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

        Sharename      Type      Comment
        ---------      ----      -------
Error returning browse list: NT_STATUS_ACCESS_DENIED

        Server               Comment
        ---------            -------
        COMP

        Workgroup            Master
        ---------            -------
        WORKGROUP            COMP
samer@host12:/etc/samba>

BOTH MACHINES' FIREWALLS HAVE BEEN COMPLETELY TURNED OFF.

Also, the Windows XP machine is configured to allow guest logins, AND its configured to NOT deny remote logins (from administrative tools).

Again, I have read my posts again, and read quite a bit of information from other posts. I DID search the forum before posting this. Can anyone please help?

balam · 02-01-2003, 03:49 PM

is samba running, make sure that server is runing if so, go to xp box you should see the linux from xp.

shassouneh · 02-01-2003, 04:22 PM

Yes, Samba is running of course.

Code:

host12:~ # rcsamba status
Checking for Samba classic NMB daemon                               running
Checking for Samba classic SMB daemon                                running
host12:~ #

Thanx for the reply. Keep these replies coming please

eallen · 02-01-2003, 10:11 PM

Here is a copy of my smb.conf file... I have aprox 50 clients connecting to this machine... Win98, WinXP, and WinME. I think you might be missing the "interfaces" line. Remember to do a "rcsmb reload" or "rcsmb restart" when you are done editing your smb.conf file. I also am using SuSE Linux 8.0 and 8.1

Good luck...

--------------------------

Samba config file created using SWAT
# from localhost (127.0.0.1)
# Date: 2002/04/18 06:10:47

# Global parameters
[global]
workgroup = Workgroup
netbios name = 32backup
interfaces = 192.168.32.13/16
security = user
encrypt passwords = Yes
update encrypted = Yes
map to guest = Bad User
log level = 3
log file = /var/log/samba/%m
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
character set = ISO8859-15
os level = 2
kernel oplocks = No
printing = lprng

shassouneh · 02-01-2003, 10:37 PM

OK, I will backup my smb.conf file and try yours. I will let you know how it goes

shassouneh · 02-01-2003, 10:54 PM

OK I tried your smb.conf file, and stopped/started the services back up again. Same thing. I had to comment out the "interfaces=..." bit as I did not know why i would need that.
Repeat: Even with the given smb.conf file, the same problem exists.

Note that the Linux machine DOES seems to establish itself on the network, and the same wih the windows machine, but boith can't find each other.

eallen · 02-02-2003, 12:46 PM

The "interfaces = ..." tells samba which ip address to listen on so you may need it. it should be "interfaces = " and then the ip address of your samba machine. I don't have a need to make a connection from my samba box to my windows boxes but I *do* connect my windows boxes to my samba box. Try (on the windows box) going to start -> find -> computer and typing in the IP address of your samba box in the search dialog. This is usually follproof. Also, make sure you can ping your samba box from your windows box.

shassouneh · 02-02-2003, 02:45 PM

Thanx for the information eallen. I have an update. I could get the linux machine to see the windows box and mount a share through a console like this:

Code:

linux:/mnt # smbmount //208.152.2.199/Samer net -o username=guest
INFO: Debug class all level = 3   (pid 3107 from pid 3107)
opts: username=guest
mount.smbfs started (version 2.2.5)
added interface ip=208.152.5.12 bcast=208.152.5.255 nmask=255.255.255.0
Connecting to 208.152.2.199 at port 139
3107: session request to 208.152.2.199 failed (Called name not present)
Connecting to 208.152.2.199 at port 139
3107: session request to 208 failed (Called name not present)
Connecting to 208.152.2.199 at port 139
Password:
linux:/mnt # cd net
linux:/mnt/net # ls
.  ..  DVD region Killer  TinyToonsAndAnimaniacsIcons.zip  ps2emu-beta.zip  winxpkeychanger  winxpkeychanger.zip
linux:/mnt/net #

However 2 problems STILL exist:

1.)The Windows Machine fails to see the Linux machine
2.) Both LinNeighborhood and Network Neighborhood fail to recognize the other machine (so even though Linux can see windows, LinNeighborhood can't).

I shall try the interfaces= trick although I doubt it will solve anything. Also I shall see about searching by IP.

Also, how do u set up the interfaces? my ip is 208.152.5.12 Do I just go interfaces=208.152.5.12 ?

Thanx for all the help everyone.

eallen · 02-02-2003, 07:28 PM

specify "interfaces = 208.152.5.12/24" the "/24" is setting your subnet to 255.255.255.0, "/16" would be equivilent to 255.255.0.0.

I don't usully deal with LinNeighborhood but you could try konquerer and type in "smb://" and then the IP address of your windows box. I don't remember if there's any setup involved or not but when you do this you should be able to browser your windows shares. Also, make sure you set up the "windows shres" preferences (linux) by clickig on preferences -> network -> windows shares.

shassouneh · 02-02-2003, 11:14 PM

K, I;ll give that a shot with /16 for now.
Also, For everyone's information (FYI) there is something waaay superior to LinNeighborhood called xfsamba. Give it a shot. i like it way better hehe.
I will try the interfaces and see what I will get.

thanx for all your help eallen

Much appreciated indeed.

baldy3105 · 02-04-2003, 11:35 AM

you have to use the hostname to get a connection to windows using the smb commands. If you use the ip address, the connection request goes to the right ip host, but in the SMB layer connection setup message the called host is show as 208.152.2.199 which the SMB layer doesn't understand.

If you use the name, the ip will resolve either via nmb or via the hosts files, and the request goes to the right ip host , but NOW with the correct hostname in the SMB layer.

Worked for me

abhijitgaikwad · 02-04-2003, 11:41 AM

Hello Guys,
I am new to this world... I need help. I want to do
a Project in Linux networking(Hope You all will help me) .. But The probleme is I am not getting any idea.. Please tell me any idea or the Project which will be Very Tough to implement and will require
Great efforts...
Hope you guys will help me .. Please Suggest me a Project in Linux Networking....

RonS · 02-04-2003, 02:34 PM

abhijitgaikwad - How about implementing a GUI frontend (probably browser based is best) for iptables??

shassouneh · 02-04-2003, 03:55 PM

Quote:

you have to use the hostname to get a connection to windows using the smb commands. If you use the ip address, the connection request goes to the right ip host, but in the SMB layer connection setup message the called host is show as 208.152.2.199 which the SMB layer doesn't understand.

If you use the name, the ip will resolve either via nmb or via the hosts files, and the request goes to the right ip host , but NOW with the correct hostname in the SMB layer.

Worked for me

I would much rather be able to use xfsamba or LinNeighborhood to do everything. I am a big fan of GUI things.
Anyways, the problems STILL exist with both machines not knowing anything about the other.

baldy3105 · 02-06-2003, 04:04 AM

I was just pointing out that the tests you were doing with the smbclient command would not have worked, in my experience, because you were using ip addresses not names.

I have a natural distrust of GUI stuff in networking due to the windows network browser, it is unreliable and unpredictable at the best of times, and yet the command line NBTSTAT command always gives you the right answers.

In this case as in that one the GUI is a bolt-on to code written to be configured on the command line. Day to day use? Sure the GUI is better, but for diagnostics go for the commands. How do you know that the gui bolt-on isn't malfuntioning in some way?

The fact that you are getting "called name not present is positive as it is a communication from the Windows box. So your IP network is ok. Check that the nmb deamon is running. Check you are in the same workgroup. use the nmblookup command to see if you can get the IP by supplying the netbios name.

Do a smbclient -L localhost what machines do you see? Who is the master browser?

Try doing the mount command again but using the netbios name. If the name doesn't resolve then there is something wrong with nmb, so shortcircuit it by putting an entry in the LMHOSTS file. Does this work? You can map shares without nmbd running, and you can have nmb running without any shares to map, this is a complex system, we know it doesn't work, but which specific bit isn't doing its job?