Can connect to Samba share in Windows, but not in Linux.

I'm trying to network two computers. System 1 is an AMD box running Mandriva 10.2, and system 2 is a P4 box with a dual boot of Win XP and Mandriva 10.2. I've shared a folder on the AMD box, and am able to map a drive letter to it from the P4 box in XP, and everything works. However, I'm not able to connect to the share when I boot into Mandriva.

SWAT Status Excerpts from AMD machine (printer and PDF related sections ommitted for space):

Quote:

---

# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2005/09/03 23:09:12

# Global parameters
[global]
workgroup = FAMILY
netbios name = AMD
server string = Samba Server %v
map to guest = Bad User
log file = /var/log/samba/log.%m
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap cache time = 60
printcap name = cups
dns proxy = No
printer admin = @adm

[amdshare]
path = /home/redbeard/shared
read only = No
guest ok = Yes

---

To mount the share on the P4 box, I've added the following line to fstab:

Code:

---

//Amd/amdshare /mnt/amd smbfs noauto,user 0 0

---

This doesn't mount the share automatically, and when I tried to manually mount it I received the following error message:

Quote:

---

[root@localhost redbeard]# mount //AMD/amdshare
10534: Connection to AMD failed
SMB connection failed

---

Does anyone have any suggestions? I feel like I'm very close to making this work, but must be overlooking some detail somewhere. Sorry for the long post, I just wanted to provide the details in case that helps. Any assistance would be greatly appreciated!

Although this was for a different problem with Samba (I was connecting to a W2k3 server, not a Linux one), it may help to use 'cifs' instead of 'smbfs'.

I may, of course, be totally mistaken, as your server may not be serving a cifs share whereas Windows does, but it may be worth a try...

Thanks for the suggestion! I tried changing that part of the line, but it still won't connect. Now I get a different error when I try to mount manually though, so maybe this will help:

Quote:

---

[root@localhost redbeard]# mount //AMD/amdshare
mount error: could not find target server. TCP name AMD/amdshare not found rc = -1073744520
No ip address specified and hostname not found

---

I was reading through the SMB HOWTO, and saw a line to tell what shares were seen by the client box (P4) from the server (AMD). I ran this line on the P4 box, and this is what I got:

Code:

---

[root@localhost redbeard]# /usr/bin/smbclient -L AMD
Connection to AMD failed

---

I'm assuming this error means I don't have the right services/settings on the P4 to even see the AMD machine. I'm just not sure what to test. I did go into SWAT and look at the "status" tab for the P4 system, and noticed that two services aren't running:

Quote:

---

version: 3.0.13
smbd: not running
nmbd: running
winbindd: not running

---

I tried starting the two services, and even stopped all three and tried starting all at once, but can't make either smbd or winbindd run. Does this sound like where my problem likely lies? Can anyone suggest some tips on how to get these services running?

I'm not an expert on this, so please someone tell me if I'm totally off base here.

I think that smbd is only needed for serving a Samba share, not to connect to one. You should have it running on your AMD box, right?

Also, have you tried running smbmount instead of mount? Or explicitly telling it to use the smbfs?

Code:

---

mount -t smbfs //AMD/amdshare /mountpoint -o username=<user>

---

Just some thoughts, I've been dealing with this stuff a whole lot lately.