Samba: not seeing Win XP share

Questions at bottom after long boring description.

System: QNX 6.2.1b Pro. (evaluation copy) with Samba 2.2.7a installed
Network: Small company LAN with MS Windows PCs (mostly XP Pro)
QNX working normally with Microsoft DHCP server, etc.

Goal #1 – view QNX share from XP boxes.
With some struggle, smb.conf file seems to be correct for a small test setup. With nmbd and smbd running, QNX-based shares are visible from XP boxes. Some mysteries remain (not all XP users can see shares) but further work may fix this.

Here’s the reason for this message…
Goal #2 – view XP share from QNX 6 box.
Reading QNX online Help for fs-cifs suggests two methods:

A. 2-step method: start fs-cifs; use mount command…

fs-cifs &

mount -t cifs -o user=guest,password=none \

           //my_xp_pc:192.168.x.y:/xp_share_name  \

The response with verbose option (-v) turned on yields command line parse information then, following a pause, this shows up:
mount: Can’t mount /xp (type cifs)
mount: Possible reason: bad file descriptor

B. 1-step method…

fs-cifs //my_xp_pc:192.168.x.y:/xp_share_name /qnx_mnt_pt \

         guest none

The response here is many lines of this:
cifs[1019942-1]: smb_logon: Permission denied
… then
cifs[1019942-1]: smb_mount: Bad file descriptor
cifs[1019942-1]: io_mount: smb_connection: Bad file descriptor
fs-cifs: missing arguments or all mount attempts failed

Is method A telling me that the QNX mount point (/xp) is bad?
Is method B telling me the same but the real cause is numerous failures at “smb_logon”?
Anybody successfully done this QNX peeking at XP?
Know what’s wrong?

In advance, thanks for reading this far!


I would suggest you get syslogd running. fs-cifs writes any error messages to the system log.

make sure your “xp_share_name” is really a Windows share and “guest” has the access privillage.

Have you resolved this issue yet? I am having the same problem with WinXP Pro.

Thanks in advance, jack

I use fs-cifs to mount my XP pro shares all the time…

fs-cifs //bigbox:bigbox:/armle /armle cdm XXXXX

So the thing you have to ensure is that the remote end will authenticate your user properly. Sometimes you may have a problem if you are part of a domain, and so your best bet is to add a specific local-user to your share with the proper access.