Can Someone Please Post "The Complete Idiots' guide to samba networking!' ???

shassouneh · 04-04-2003, 05:18 AM

1.) Both Machines ping each other fine, with about 20 ms
2.) Windows XP reports the following when issuing nbtstat -A <linux_ip>

Code:

 Node IpAddress: [208.152.2.199] Scope Id: [] 
  
            NetBIOS Remote Machine Name Table 
  
        Name               Type         Status 
     --------------------------------------------- 
     SUSE_LAPTOP    <00>  UNIQUE      Registered 
     SUSE_LAPTOP    <03>  UNIQUE      Registered 
     SUSE_LAPTOP    <20>  UNIQUE      Registered 

(02:52:40) DrMSH:   ..__MSBROWSE__.<01>  GROUP       Registered 
     WORKGROUP         <00>  GROUP       Registered 
     WORKGROUP         <1D>  UNIQUE      Registered 
     WORKGROUP         <1E>  GROUP       Registered 
  
     MAC Address = 00-00-00-00-00-00

3.) Linux reports the following when issuing nmblookup -A <windoze_ip>

Code:

linux:~ # nmblookup -A 208.152.2.199
Looking up status of 208.152.2.199
        COMP            <00> -         B <ACTIVE> 
        WORKGROUP       <00> - <GROUP> B <ACTIVE> 
        COMP            <20> -         B <ACTIVE> 
        WORKGROUP       <1e> - <GROUP> B <ACTIVE> 
        WORKGROUP       <1d> -         B <ACTIVE> 
        ..__MSBROWSE__. <01> - <GROUP> B <ACTIVE> 

linux:~ #

4.) Windows XP reports the following when issuing nbtstat -a <linux_name>

Code:

Local Area Connection: 
Node IpAddress: [208.152.2.199] Scope Id: []

    Host not found.

5.) Linux reports the following when issuing nmblookup <windoze_name>

Code:

linux:~ # nmblookup Comp
querying Comp on 208.152.6.255
name_query failed to find name Comp
linux:~ # nmblookup COMP
querying COMP on 208.152.6.255
name_query failed to find name COMP
linux:~ #

6.) Linux reports the following when issuing smbclient -L Comp

Code:

linux:~ # smbclient -L Comp          
added interface ip=208.152.6.101 bcast=208.152.6.255 nmask=255.255.255.0
Connection to Comp failed
linux:~ #

HOWEVER, its different when using IP as smbclient -L <ip>

Code:

linux:~ # smbclient -L 208.152.2.199
added interface ip=208.152.6.101 bcast=208.152.6.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: 
Domain=[WORKGROUP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

        Sharename      Type      Comment
        ---------      ----      -------
        IPC$           IPC       Remote IPC
        Samer          Disk      
        floppy         Disk      
        mp3            Disk      
        mp3 2          Disk      

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

        Workgroup            Master
        ---------            -------
        WORKGROUP            COMP
linux:~ #

7.) Windows XP reports the following when issuing "net view \\<linux name>"

Code:

System error 53 has occurred.

The network path was not found.

Here is some information that might be helpful when looking through this data:

Machines involved: 1 SuSE Linux Professional 8.1 machine running Samba 2.2.5, 1 Windows XP professional SP1 machine
Linux machine name: SuSE_laptop
Windows XP machine name: Comp

Here is my smb.conf file AS IS:

Code:

# smb.conf is the main samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SuSE
# Date: 2002-09-12
[global]
        workgroup = Workgroup 
        os level = 1
        encrypt passwords = yes
        netbios name = SuSE_laptop
[homes]
        comment = Home Directories
        valid users = %S
        browseable = no
        writeable = yes
        create mask = 0640
        directory mask = 0750
[printers]
        comment = All Printers
        path = /var/tmp
        printable = yes
        create mask = 0600
        browseable = no
[print$]
        comment = Printer Drivers
        path = /var/lib/samba/drivers
        write list = @ntadmin root
        force group = ntadmin
        create mask = 0664
        directory mask = 0775

Please provide feedback if you can. Thanx for all the reply and helfulness everyone. Certainly much appreciated.

david_ross · 04-04-2003, 11:36 AM

I would try setting one machine up to be the master browser. I find the linux does this better than Windows. Set os level to 65 and preferred master to yes.
OR
You could probably get away with ip addresses or hostnames in hosts files if it is only 2 machines.

shassouneh · 04-04-2003, 06:56 PM

I tried networking via IP. Even though it worked in principle it was incredibly slow. and i mean INCREDIBLY.

As for the Os Level I tried that too. I tried levels of 1, 2,5, and even 100 to no avail!!!

baldy3105 · 04-05-2003, 12:36 PM

OK, this is wierd. Query on the IP's works but query on the names you get in response doesn't, not good. And if comms via IP is having problems on its own then your problem is more fundamental than Samba. Whats your network setup? Do you have/ can you borrow a third machine to cross check the other two? You may have a network problem , or possible a dicky nic or driver. You could test it with a crossover cable which would eliminate a network fault.

baldy3105 · 04-05-2003, 12:46 PM

On XP you could try doing a netstat -e, and on linux do ifconfig, see what the ethernet stats look like.

P.S. The commands used here are independant of the browsing mechanism, which can take (according to MS) up to 45 minutes to show a new network device i.e. its crap. Using these commands causes lookups to be done as a B-node i.e. direct unicast or broadcast for the destination hosts, thats why I use em. Worry about the browsing malarky (about which you are quite right IMO) later, as its so unreliable.

aherm · 04-05-2003, 01:09 PM

Oops, did anyone notice this:

See it again (I may make mistake here):
208.152.2.199 -> = windows ip (I think I am wrong here)
try run on win ipconfig and post it here

208.152.2.199 -> = linux ip (I think I am correct here)
try run on linux ifconfig and post it here

is it windows ip = linux ip ???

That's why (is it yes)! You cannot have the very same ip address to do networking. This is often happened if your linux and windows need the very same ip address to access the leased ip from the internet provider and you use a switch (or hub) intead of a router e.g without proper double NIC setup on one of your computer (the server). The easiest way is to buy a personal router for that, and setup win and linux using dhcp. (or the cheaper way is buy another different NIC for the server and setup the server correctly). What is your hardware setup?

Try copy some of this in your smb.conf

[global]
workgroup = WORKGROUP
os level = 2
time server = Yes
unix extensions = Yes
encrypt passwords = Yes
log level = 1
syslog = 0
printing = CUPS
printcap name = CUPS
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
wins support = true
veto files = /*.eml/*.nws/riched20.dll/*.{*}/

[homes]
comment = Home Directories
path = %H
valid users = yourwinuser1here anotheruserontheworkhere
invalid users = root sysadmin administrator
browseable = Yes
writeable = Yes
public = Yes
create mask = 0640
directory mask = 0750

One more question:
Do you install harden-suse or bastille? This may cause problems tho.

shassouneh · 04-05-2003, 07:27 PM

Ok, before running net stat or ipconfig, note that networking on the SAME cable, SAME machine, different OS (Windows 2000) works PERFECTLY.

So Windows 2000 / XP networkign works PERFECTLY.

It is LINUX / WIndows XP that has a problem!!!

SAME SETUP, SAME HARDWARE, SAME CABLES, different OS!

aherm · 04-05-2003, 11:39 PM

Doh!

I think that's the reason why. XP is not very cooperating with the current linux samba et al. Hopefully this will be fixed soon :-)

Upgrade your samba et al whenever any fix on this problem become available.

Have a lot of fun :-)

fhj518 · 04-06-2003, 07:32 AM

Quote:

Originally posted by baldy3105
OK just had fiddle with mine (as it were).

On 2000 set your guest account to no password. On linux you should now be able to do -

smbclient -L \\<win_name> -U guest

at password prompt, just hit return, you should get a share listing from your windoze box.

Now on Linux, add a user and make sure that user, password and smbuser password match the user and password that you logged onto windoze with. You can do it differently but windoze can be a bit funny about it.

now on windows do "net use * \\<linux_name>\<share>" and it should go.

THNX a lot man, this solved the problem that I had left with SAMBA, but after all, I'm just a

aherm · 04-06-2003, 03:36 PM

Anybody knows that Konqueror in KDE 3.1.1 can do share access graphically instead of using smbclient in command line?

For that SuSE Linux 8.1 requires: samba-client, kdenetwork3-lisa, kdenetwork3-lan, and kdebase3-samba ;-)

kdenetwork3-lisa and kdenetwork3-lan provide plug-ins for Konqueror to allow convenient access to windows shares.

Anybody try this? How to setup LISa to do this?

bax · 04-06-2003, 09:19 PM

I'm a late comer to this thread but I would recommend from my past experiences to knock up your OS level to 35 so Samba will be the master browser. I have Samba on Debian working flawlessly by the way.

baldy3105 · 04-07-2003, 08:37 AM

You're right about the IP, it reads above as if you have the same IP on both machines. Check the IP addreses on both machines and make sure that the network number is the same but the host number is different. i.e on a 255.255.255.0 mask the first three digits are network, the last digit is host.

This will definitley upset the whole shooting match.

aherm · 04-07-2003, 02:41 PM

I'm glad sombody finally notice that.

208.152.2.199 = from windows
208.152.6.255 = from linux

No wonder they do not talk to each other, I mean .2. != .6. ;-)

Thanks a lot :-)

shassouneh · 04-07-2003, 09:59 PM

Quote:

I'm glad sombody finally notice that.

208.152.2.199 = from windows
208.152.6.255 = from linux

No wonder they do not talk to each other, I mean .2. != .6. ;-)

Thanks a lot :-)

NOT true! See this:

Code:

linux:~ # ifconfig     
eth0      Link encap:Ethernet  HWaddr 00:60:97:92:E7:0D  
          inet addr:208.152.6.101  Bcast:255.255.255.255  Mask:255.255.255.0
          inet6 addr: fe80::260:97ff:fe92:e70d/10 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:153054 errors:0 dropped:0 overruns:0 frame:0
          TX packets:74871 errors:0 dropped:0 overruns:0 carrier:0
          collisions:409 txqueuelen:100 
          RX bytes:119826301 (114.2 Mb)  TX bytes:10809361 (10.3 Mb)
          Interrupt:3 Base address:0x300 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:13656 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13656 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4097954 (3.9 Mb)  TX bytes:4097954 (3.9 Mb)

linux:~ #

The Linux IP is 208.152.6.101 !!!!!

Quote:

I'm a late comer to this thread but I would recommend from my past experiences to knock up your OS level to 35 so Samba will be the master browser. I have Samba on Debian working flawlessly by the way.

I tried an OS level as high as 1000 and as low as 1 (I tried MANY numbers). No dice!!!

Quote:

You're right about the IP, it reads above as if you have the same IP on both machines. Check the IP addreses on both machines and make sure that the network number is the same but the host number is different. i.e on a 255.255.255.0 mask the first three digits are network, the last digit is host.

This will definitley upset the whole shooting match.

And in English this means???

]Thanx For The Replies Everyone. Please Keep The Coming

aherm · 04-07-2003, 11:10 PM

inet addr:208.152.6.101 Bcast:255.255.255.255 Mask:255.255.255.0
conclussion -> ifconfig = OK
if... wait,

Where is your ipconfig? Post it here !

Have a lot more fun :-)