No one can see my Linux/samba machine!

Avatar · 06-08-2004, 08:38 AM

Hello, my computer is a IBM Netvista 566MHz Intel celeron, 384 MB ram.

It used to run Windows ME. Well windows crashed too much so I replaced it with Mandrake 9.2 (kernel 2.4.22) (which also crashes too much but that's aother story).

This computer has a Lexmark laser printer hooked up to it, and also a file share. The printer works fine in Linux. When it was a Windows computer, I used the printer from a Windows 98 machine. Also I shared files between the two computers using a network share.

Now that I have Linux, I can't do either. My Linux computer can see my Windows 98 computer file share, but can't write to it (I can, however, copy a file from that share onto the Linux computer's hard drive and go from there.) So If I want to share a file from Linux to Windows, i have to use floppy diskettes. The Windows 98 computer can not see the linux computer at all, nor print to the printer. It's fairly important that I get at least the printer working.

here is my smb.conf. file. Note that the workgroup and netbios name are the same that I had when the computer had Windows. Also, when Linux boots I can see that it sets the computername to IBMFB1L0DH.mydomain.ca, so I think it should work.

#======================= Global Settings =====================================
[global]
workgroup = 2E18
netbios name = IBMFB1L0DH
server string = Samba Server %v
printcap name = /etc/printcap
load printers = yes
printing = cups
printer admin = @adm
log file = /var/log/samba/log.%m
max log size = 50
log level = 3
hosts allow = 192.168.1.121 127.
map to guest = bad user
security = user
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = no

#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writable = yes

[printers]
comment = All Printers
path = /var/spool/lpd
browseable = no
# to allow user 'guest account' to print.
guest ok = yes
writable = no
printable = yes
create mode = 0700
print command = lpr-cups -P %p -o raw %s -r # using client side printer drivers.

[ddrive]
comment = Windows Files
path = /mnt/windows
read only = no
public = yes
writable = yes
--------------------------

Hope someone can help me!!!!

michaelk · 06-08-2004, 09:03 AM

Did you create a samba user that matches your regular linux user and windows user?

If I remember correctly the default for a share is browsable = no. So that is why it isn't visible in network neighboorhood. You should still be able to connect via windows file explorer.

In a windows DOS prompt type the following command:
net view

Do you see the linux computer?

On the linux box make sure that both smbd and nmbd are running. The command testparm does not return any errors.

You should see the browsable linux shares with the following command:
smbclient -L host_name

Replace host_name with actual PC hostname.

Avatar · 06-08-2004, 12:51 PM

Quote:

Originally posted by michaelk
Did you create a samba user that matches your regular linux user and windows user?

There is no Windows user. Its Windows 98. I used to connect to the Windows ME computer by going into Network Neighborhood.

If I remember correctly the default for a share is browsable = no. So that is why it isn't visible in network neighboorhood. You should still be able to connect via windows file explorer.

In a windows DOS prompt type the following command:
net view
Do you see the linux computer?

No. It's not in Network Neighborhood either. Typing \\IBMFB1L0DH into the network neighborhood address bar gives: "Windows cannot find 'IBMFB1L0DH'. Check the spelling and try again, or try searching for the item by clicking the Start button and then clicking Search."

On the linux box make sure that both smbd and nmbd are running. The command testparm does not return any errors.
I am not sure how to check if smbd and nmbd are running. Testparm returns:
Load smb config files from /etc/samba/smb.conf
Processing section [homes]
Processing section [printers]
Processing section [ddrive]
Loaded services file OK.
Press enter to see a dump of your service definitions.

You should see the browsable linux shares with the following command:
smbclient -L host_name

Replace host_name with actual PC hostname.

# smbclient -L IBMFB1L0DH
added interface ip=192.168.1.160:139 bcast=192.168.1.255 nmask=255.255.255.0
error connecting to 192.168.1.160:139 (Connection refused)
Error connecting to 192.168.1.160 (Connection refused)
Connection to IBMFB1L0DH failed

# smbclient -L IBMFB1L0DH.mydomain.ca
added interface 192.168.1.160 bcast=192.168.1.255 nmask=255.255.255.0
Connection to IBMFB1L0DH.mydomain.ca failed

waaah!!

michaelk · 06-08-2004, 04:16 PM

Check to see of samba is running. You can use top or ps commands
ps ax | more

If you see smbd and nmbd processes then samba is running. If not check the logs in /var/logs/samba.

Avatar · 06-09-2004, 11:54 AM

Hi Michael. The services smbd and nmbd are not running. How do I start them?

My log.smbmount shows the following entries.

Code:

[2004/06/02 09:49:22, 0] client/smbmount.c:send_fs_socket (383)
      mount.smbfs: entering daemon mode for service \\APTIVA\shared, pid 2320
[2004/06/02 13:21:37, 2] client/smbmount.c:send_fs_socket (393)
      mount.smbfs[2320]: got signal, getting new socket
[2004/06/02 13:21:37, 3] lib/util_sock.c:open_socket_out(845)
      Connecting to 192.168.1.121 at port 139
[2004/06/02 13:27:15, 0] client/smbmount.c:send_fs_socket (383)
      mount.smbfs: entering daemon mode for service \\APTIVA\shared, pid 3106
[2004/06/07 15:38:17, 0] client/smbmount.c:send_fs_socket (383)
      mount.smbfs: entering daemon mode for service \\APTIVA\shared, pid 2891

I think that's from when I mounted the shared drive on the Windows 98 computer manually.

Avatar · 06-09-2004, 04:01 PM

Thank you for all your help. I found the problem.

The package samba-server-2.2.8a-13 was not installed on my system (I did have samba-client and samba-common, though).

Now that I installed it, I ran "samba start" and now I can see the computer with Windows 98.

Thanks again.

nbhalala · 06-16-2004, 09:34 AM

Hi Guru,
This is Naresh Bhalala, Mumbai
My Machine having - LINUX 7.2 & Win 2000
I have installed SAMBA 2.2.1a including SWAT 2.2.1a
In LINUX : http://127.0.0.1:901 is working properly, and showing SAMBA screen...
In Windows : http://127.0.0.1:901 or http://Naresh:901 (Naresh is User) -> NOT WORKING............WHY ???
I can see my LINUX machine as localhost in other windows machine which is connected to our company's network........i want samba screen on browser of WINDOWS machine (not my one but other connected to network as my machinr will in a mode of smb running)

i know only u can solve my prob.....plz
thanks in advance....

reply to nbhalala@yahoo.com

Naresh

Avatar · 06-21-2004, 08:45 PM

It doesn't matter what you have installed in Linux. Your Windows 2000 partition can neither see nor interact with anything on the Linux side. Samba will not work in Windows unless you install it there too.

Hope this helps.

nbhalala · 06-21-2004, 11:48 PM

Thanks for your reply.....
I was waiting for that very badly....as i got stuck at some point....
Now plz help me in finding the download of SAMBA for WINDOWS 2000....
thanks....Regards,,,
Naresh

Avatar · 06-24-2004, 01:29 PM

nbhalala,

Your question is not related to my original thread.

Please start a new thread for your questions from now on.

In the mean time, you dont need to install Samba on Windows 2000 because Windows 2000 natively supports SMB protocol:
------------------------------------
Samba
Samba is a freely available SMB server for UNIX, OpenVMS (recently ported and maybe not very stable) developed by Andrew Tridgell and maintained by a loosely knit group of people all over the world. Samba runs on a great many UNIX variants (Linux, Solaris, SunOS, HP-UX, ULTRIX, DEC OSF/1, Digital UNIX, Dynix (Sequent), IRIX (SGI), SCO Open Server, DG-UX, UNIXWARE, AIX, BSDI, NetBSD, NEXTSTEP, A/UX, etc).

Microsoft Windows Servers
Microsoft has a number of SMB server implementations for the Windows range of operating systems. These are not separate products, rather, they are integral to the appropriate version of the Windows operating system. However, they can be switched off either though the Control Panel or at the command line (net stop server at DOS prompt).
------------------------------------

what i meant in my last post, is that you have to set up things in your Windows partition as in your Linux partition, You can't just set up one partition and expect the other one to also work. A partitioned hard disk is like two separate computers.