Bluetooth Pan Connection To Win Xp

[Marty]

I have a Z sl5500 sharp 3.10 rom with Bluez installed. At work I can ping,sync, map a drive
in winxp,browse, and move files using z manager and admin z through vnc on my laptop via the usb docking cradle.
At home I can setup a GN pan bluetooth connection to the same laptop and do all of the above except map a drive to the z within xp.
I have read all the faqs about samba , bluez and believe I have done everything
by the book. Curiously setting up the PAN on the z using NAP in the pand command would not work-I had to use GN.(I have DELL True Bluetooth on my Dell 400 laptop which has widcomm BT drivers )

pand --role PANU --service NAP --connect xx:xx:xx:xx:xx:xx --nodetach
(This throws a permissions error - doent work)

pand --role PANU --service GN --connect xx:xx:xx:xx:xx:xx --nodetach
(This allows me to make a solid BT connection to my laptop)

followed by :

ifconfig bnep0 192.168.129.201

and..

route add default gw 192.168.129.1

Any ideas why the drive mapping works in the cradle but not via bluetooth pan?
Also why doesnt NAP work in the pand command? Why does GN work?
Note I get the same problem when logged onto our system at work .Using GN allows me to establish a BT connection.Ping z is ok , everything
except map to the Z using win xp explorer.
XP says it cant find the z on 192.168.129.201
Any ideas what is up?Looks like I am missing something
simple.

[craigtyson]

look at your smb.config

the interfaces line has to have
   interfaces = usbd0 eth0 bnep0
to work over usb, ethernet (inc some wifi) and bluetooth

[Marty]

I have a Z sl5500 sharp 3.10 rom with Bluez installed.

Interfaces line in smb.conf looks ok (see below)

interfaces = usbd0 bnep0 eth0 ppp0

If something was missing I would'nt expect to be able to sync and ping the z on the cradle or BT but I can. Only the drive mapping is the problem...

[craigtyson]

on the xp side is windows client ticked on the pan icon in your network connections?

[tumnus]

Have the smb and nmb processes been restarted since you edited your smb.conf file?

Syncing doesn't use Samba and of course neither does ping, so it still looks like a samba config problem.

Also, make sure you are editing the smb.conf under /usr/lib/samba . The version of Samba on the Zaurus defaults to this one instead of any under /etc.

If you're still having problems please post your smb.conf (minus any private details) as there can be a few other settings that affect interfaces and share visibility.

[Marty]

Have restarted processes ok.Note I can map to the z ok when its docked in the cradle - thats ok. Tried setting up a pan on the xp side. Although it said I was connected I couldnt do anything with this connection. The bluetooth GN connection I initiate from the z is rock solid .. except for the drive mapping bit! Here's my smb.conf  ....I've replaced my company domain name with xxxx.

[global]                  
# workgroup is either a domain name or a workgroup name
   workgroup = xxxx
        netbios name = zaurus
     log file = /dev/null
#
# encrypt passwords is required for Win98, NT and Windows 2000
#
   encrypt passwords = yes

   coding system = utf8
   client code page = 932
   force create mode = 0755
   strict sync = yes
   sync always = yes

   interfaces = usbd0 bnep0 eth0 ppp0
   wins support = yes
[system]                     
   comment = System Folder
   path = /root/samba
   read only = no
   browseable = yes
   guest ok = yes
   force user = root
[home]                     
   comment = for User Data
   path = /home/samba
   short preserve case = no
   read only = no      
   guest ok = yes
   force user = zaurus

[craigtyson]

It might be that though you are able to connect with IP from the XP bos on the PAN the windows client is not bound to that interface.  This would stop you browsing and mapping drives.  Its been a while with bluetooth on XP but somewhere you should have a setting that allows NetBIOS over TCP\IP without netbios running you will be able to ping but not map a drive.  Also when you ping do you ping zaurus or an ip address if by ip address try
ping -a ipaddress
from you xp box
the a is lower case and has to be infront of the ipaddress.  it should resolve the host name of your zaurus if netbios is running.

[Marty]

Checked the netbios setting in the bt network connection on my Win XP Laptop , the default setting in tcp/ip seems to use netbios ok. Tried "ping -a" with google's IP address and it resolved to "google.co.uk"
Tried z's ip address with "ping -a" but it replied with 192.168.129.201 - could not resolve to netbios name "zaurus".
Checked my inetd.conf file as I had to add a couple of lines as per "Samba over non - usb"  paper .  See below

#
# inetd.conf   This file describes the services that will be available
#      through the INETD TCP/IP super server.  To re-configure
#      the running INETD process, edit this file, then send the
#      INETD process a SIGHUP signal.
#
# Version:   @(#)/etc/inetd.conf   3.10   05/27/93
#
# Authors:   Original taken from BSD UNIX 4.3/TAHOE.
#      Fred N. van Kempen, <waltje@uwalt.nl.mugnet.org>
#
# Modified for Debian Linux by Ian A. Murdock <imurdock@shell.portal.com>
#
# Modified for RHS Linux by Marc Ewing <marc@redhat.com>
#
# Further modified by Olaf Kirch <okir@caldera.com> for Caldera Open Linux
#
# <service_name> <sock_type> <proto> <flags> <user> <server_path> <args>
#
# Echo, discard, daytime, and chargen are used primarily for testing.
#
# To re-read this file after changes, just do a 'killall -HUP inetd'
#
# Note: builtin UDP services now silently drop packets from ports < 512.
#echo   stream   tcp   nowait   root   internal
#echo   dgram   udp   wait   root   internal
#discard   stream   tcp   nowait   root   internal
#discard dgram   udp   wait   root   internal
#daytime   stream   tcp   nowait   root   internal
#daytime dgram   udp   wait   root   internal
#chargen stream   tcp   nowait   root   internal
#chargen dgram   udp   wait   root   internal
#time   stream   tcp   nowait   root   internal
#time   dgram   udp   wait   root   internal
#
# These are standard services.
#
### With tcpd (TCP Wrapper) ###
#ftp   stream   tcp   nowait   root   /usr/sbin/tcpd   in.ftpd -l -a
#telnet   stream  tcp    nowait  root    /usr/sbin/tcpd   in.telnetd
### Without tcpd (TCP Wrapper) ###
#ftp   stream   tcp   nowait   root   /usr/sbin/in.ftpd -l -a
#telnet   stream  tcp    nowait  root    /usr/sbin/in.telnetd

#
# Mail and news
#
# Do not uncomment either unless you *really* know what you are doing.
# Both are started as standalone daemons from the /etc/rc.d scripts.
#smtp   stream  tcp    nowait  root    /usr/bin/smtpd   smtpd
#nntp   stream   tcp   nowait   root   /usr/sbin/tcpd   in.nntpd

#
# Shell, login, exec and talk are BSD protocols.
#
#shell   stream   tcp   nowait   root   /usr/sbin/tcpd   in.rshd
#login   stream   tcp   nowait   root   /usr/sbin/tcpd   in.rlogind
#exec   stream   tcp   nowait   root   /usr/sbin/tcpd   in.rexecd
#talk   dgram   udp   wait   nobody.tty   /usr/sbin/tcpd   in.talkd
#ntalk   dgram   udp   wait   nobody.tty   /usr/sbin/tcpd   in.ntalkd
#dtalk   stream   tcp   wait   nobody.tty   /usr/sbin/tcpd   in.dtalkd

#
# Pop and imap mail services et al
#
#pop2   stream  tcp     nowait  root    /usr/sbin/tcpd   ipop2d
#pop3   stream  tcp     nowait  root    /usr/sbin/tcpd   ipop3d
#imap   stream  tcp     nowait  root    /usr/sbin/tcpd   imapd
#
# The Internet UUCP service.
#
#uucp   stream   tcp   nowait   uucp   /usr/sbin/tcpd   /usr/sbin/uucico -l
#
# Tftp service is provided primarily for booting.  Most sites
# run this only on machines acting as "boot servers." Do not uncomment
# this unless you *need* it.  
#
#tftp   dgram   udp   wait   root   /usr/sbin/tcpd   in.tftpd
#bootps   dgram   udp   wait   root   /usr/sbin/tcpd   bootpd
#
#  This is for the finger service
#
#finger   stream   tcp   nowait   root   /usr/sbin/tcpd   in.fingerd
#
# Finger, systat and netstat give out user information which may be
# valuable to potential "system crackers."  Many sites choose to disable
# some or all of these services to improve security.
#
#systat   stream   tcp   nowait   nobody   /usr/sbin/tcpd   /bin/ps   -auwwx
#netstat stream   tcp   nowait   nobody   /usr/sbin/tcpd   /bin/netstat --inet
#
# Authentication
#
#auth   stream   tcp   nowait   root   /usr/sbin/tcpd   in.identd
#
# End of inetd.conf
netbios-ssn stream tcp nowait root /usr/sbin/tcpd /usr/sbin/smbd
netbios-ns dgram udp wait root /usr/sbin/tcpd /usr/sbin/nmbd

[tumnus]

Set 'wins support = no'. When this is 'yes' that turns on the WINS server, which you don't need on your Zaurus. If you want name resolution to work, you have to add a line to smb.conf like this:

wins server = 192.168.129.1

Have you tried entering the following in Start->Run on your PC:

\\192.168.129.201

? It might be that everything is working except name resolution.

That inetd.conf stuff just makes the Samba processes launch automatically when your Zaurus detects something trying to communicate on the Samba related ports. Those lines aren't needed if you run smbd and nmbd manually.

[Marty]

I just got the drive mapping working using the ip address about an hour ago - still cant map using netbios name though. All I did was change interfaces
from:

interfaces = usbd0 bnep0 eth0 ppp0

to:

interfaces = 192.168.129.0/24

ok I can now map a drive , sync , ping all via bluetooth at home - Great!
Just read your post tummnus. Thanks.
I tried adding wins server = 192.168.129.1 in the [global] section and commented out wins support = yes (Note I didnt specifically set wins support = no   - should I have?)
I then tried using the netbios name again to map a drive but it still can find the path.
I'd prefer that samba runs automatically when it detects a connection so thats good.

Update! I just edited the lmhosts file in winxp and added the zaurus ip address and its netbios name (zaurus) to lmhosts. The name resolution works fine now!
So can anyone explain why xp cant do this without the lmhosts file? It looks like that all along that the netbios name in smb.conf is being ignored by xp somehow.

Any other ideas how I can pin down the name resolution problem???

[craigtyson]

It looks like PAN on XP is not fully NetBIOS compatable.

What do you get if you use from yuor XP box.

NBTStat -a zaurus

note as before the a is lower case.

IF netbios traffic is going across the PAN you should get somthing like this.

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

           NetBIOS Remote Machine Name Table

       Name               Type         Status
    ---------------------------------------------
    zaurus       <00>  UNIQUE      Registered
    workgroup <00>  GROUP       Registered

    MAC Address = xx-xx-xx-xx-xx-xx


If not then you wont get anything.

[Marty]

Craig , tried your suggestion - here's the results:

c:\NBTStat -a zaurus

Local Area Connection3:
Node IpAddress: [192.168.36.79] Scope Id: [ ]
Host Not found

Bluetooth Network:
Node IpAddress: [192.168.129.1] Scope Id: [ ]
Host not found

By the way I seem to have established a proper network connection through bluetooth in my setup (I had to use GN rather than NAP in the Panu connect command. )  I did try initiating a PAN connection to the z from XP. That seemed to connect ok and XP called it a PAN connection... but I wasnt able to do anything with it..maybe I'll try this again...