windows systems 
and I can see the SAMBA server
in my workgroup inside the network neighborhood. 
When I double click on the server nothing happens for about 5 seconds and 
then I get a 
pop up error (text of error is):
--------
\\Sambaserver is not accessible
Windows cannot find the computer or share name. 
Make sure the computer or share name is valid and that you are connected to 
the network, 
and then try again.
-----------
When I double click any of my other windows systems I can see the services 
that are shared
and I have no trouble reading/writing files on other windows systems.
My SAMBA servername is SAMBASERVER (192.168.1.102)
(pcguest is a valid login that does not require a password)
My smb.conf file is included here: 
[global]
    workgroup = homenet
    server string = This Samba Server
    security = user
    netbios name = SAMBASERVER
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    dns proxy = no
    encrypt passwords = yes
    smb passwd file = /etc/samba/smbpasswd
    guest account = pcguest
    log file = /var/log/samba/log.%m
    password level = 8
    debug level = 8
    local master = false
    interfaces =  192.168.1.102/255.255.255.0
[homes]
    comment = All the home directories
    browsable = no
    writable = yes
[public]
    comment = Public Share
    path = /home/Thesamba
    browsable = yes
[XDRIVE]
    comment = THE X DRIVE
    path = /home/X
    browsable = yes
    writable = yes
--------------------------
END OF SMB.CONF
I have checked and I am only running one copy of samba processes(nmbd and 
smbd).
I start them from the command line as smbd -D and nmbd -D
I am logged in as root
I can see the processes running using "ps"
 
I ran the tests detailed in DIAGNOSTICS.txt and I did a packet trace using 
ethereal
I found an interesting difference between doing an nbquery on another windows 
machine
and on the SAMBA server. The samba server name query seems to result 
in an ICMP response saying destination unreachable:
The Samba server does 
a broadcast name query on the name HOMENET (frame 1)
Frame 2 shows the windows ME client (192.168.1.99) respsonding to the 
Samba server (192.168.1.102) with a name query response to port 137
Frame 3 shows the Samba Server linux system sending out an ICMP
destination unreachable message for port 137. 
This packet sequence is repeatable and I see it many times 
in the traces
To me this seems like NBMD
is not listening on port 137. If so How can I fix
given all the other steps I've taken?
 
    
        
The netstat result looks like this:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State     
  PID/Program name   
tcp        0      0 0.0.0.0:32768           0.0.0.0:*               LISTEN    
  626/rpc.statd       
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN    
  1578/smbd           
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN    
  611/portmap         
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN    
  786/sshd            
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN    
  846/sendmail: accep 
udp        0      0 0.0.0.0:32770           0.0.0.0:*                         
  626/rpc.statd       
udp        0      0 192.168.1.102:137       0.0.0.0:*                         
  1576/nmbd           
udp        0      0 0.0.0.0:137             0.0.0.0:*                         
  1576/nmbd           
udp        0      0 192.168.1.102:138       0.0.0.0:*                         
  1576/nmbd           
udp        0      0 0.0.0.0:138             0.0.0.0:*                         
  1576/nmbd           
udp        0      0 0.0.0.0:802             0.0.0.0:*                         
  626/rpc.statd       
udp        0      0 0.0.0.0:111             0.0.0.0:*                         
  611/portmap         
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags       Type       State         I-Node PID/Program name    
Path
unix  2      [ ACC ]     STREAM     LISTENING     1359   859/gpm             
/dev/gpmctl
unix  2      [ ACC ]     STREAM     LISTENING     1399   907/xfs             
/tmp/.font-unix/fs7100
unix  2      [ ACC ]     STREAM     LISTENING     781    508/pump            
/var/run/pump.sock
unix  12     [ ]         DGRAM                    1042   592/syslogd         
/dev/log
unix  2      [ ]         DGRAM                    6292   1427/login -- root  
unix  2      [ ]         DGRAM                    1578   932/login -- root   
unix  2      [ ]         DGRAM                    1402   907/xfs             
unix  2      [ ]         DGRAM                    1371   871/crond           
unix  2      [ ]         DGRAM                    1340   846/sendmail: accep 
unix  2      [ ]         DGRAM                    1293   806/xinetd          
unix  2      [ ]         DGRAM                    1230   759/automount       
unix  2      [ ]         DGRAM                    1191   710/apmd            
unix  2      [ ]         DGRAM                    1088   626/rpc.statd       
unix  2      [ ]         DGRAM                    1051   597/klogd           
unix  2      [ ]         STREAM     CONNECTED     462    1/init [3]          
--part1_76.14acf5d9.2956ae39_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>Sambaserver is
not accessible
<BR>
<BR>I have a problem connecting to SAMBA  from Windows/ME systems
<BR>(using samba--2.2.2 on Red hat Linux 7.1)
<BR>
<BR>
<BR>What I would like to know is - What can I change to get this to work
properly?
<BR>
<BR>SETUP
<BR>I have a simple network - 
<BR>three Windows/ME systems and 1 Red Hat Linux 7.1 system all on the
same subnet.
<BR>There is a linksys router on the same subnet that 
<BR>provides WAN connectivity through a cable modem
<BR>I have a single workgroup named HOMENET. I am  tring to
provide file system shares for
<BR>the windows/ME systems. 
<BR>I do not have a printer connected to my Linux/Samba system
<BR>The 3 windows machines share services back and forth 
<BR>(printers, file shares) without a problem.
<BR>
<BR>PROBLEM
<BR>From my Windows/ME machines using Windows Explorer I can see all the
other windows systems
<BR>and I can see the SAMBA server
<BR>in my workgroup inside the network neighborhood. 
<BR>When I double click on the server nothing happens for about 5 seconds
and then I get a
<BR>pop up error (text of error is):
<BR>--------
<BR>\\Sambaserver is not accessible
<BR>Windows cannot find the computer or share name. 
<BR>Make sure the computer or share name is valid and that you are
connected to the network,
<BR>and then try again.
<BR>-----------
<BR>When I double click any of my other windows systems I can see the
services that are shared
<BR>and I have no trouble reading/writing files on other windows systems.
<BR>
<BR>
<BR>
<BR>
<BR>My SAMBA servername is SAMBASERVER (192.168.1.102)
<BR>(pcguest is a valid login that does not require a password)
<BR>My smb.conf file is included here: 
<BR>
<BR>[global]
<BR>    workgroup = homenet
<BR>    server string = This Samba Server
<BR>    security = user
<BR>    netbios name = SAMBASERVER
<BR>    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
<BR>    dns proxy = no
<BR>    encrypt passwords = yes
<BR>    smb passwd file = /etc/samba/smbpasswd
<BR>    guest account = pcguest
<BR>    log file = /var/log/samba/log.%m
<BR>    password level = 8
<BR>    debug level = 8
<BR>    local master = false
<BR>    interfaces =  192.168.1.102/255.255.255.0
<BR>
<BR>[homes]
<BR>    comment = All the home directories
<BR>    browsable = no
<BR>    writable = yes
<BR>
<BR>[public]
<BR>    comment = Public Share
<BR>    path = /home/Thesamba
<BR>    browsable = yes
<BR>
<BR>[XDRIVE]
<BR>    comment = THE X DRIVE
<BR>    path = /home/X
<BR>    browsable = yes
<BR>    writable = yes
<BR>--------------------------
<BR>END OF SMB.CONF
<BR>
<BR>I have checked and I am only running one copy of samba processes(nmbd
and smbd).
<BR>I start them from the command line as smbd -D and nmbd -D
<BR>I am logged in as root
<BR>I can see the processes running using "ps"
<BR> 
<BR>I ran the tests detailed in DIAGNOSTICS.txt and I did a packet trace
using ethereal
<BR>I found an interesting difference between doing an nbquery on another
windows machine
<BR>and on the SAMBA server. The samba server name query seems to result 
<BR>in an ICMP response saying destination unreachable:
<BR>
<BR>The Samba server does 
<BR>a broadcast name query on the name HOMENET (frame 1)
<BR>
<BR>Frame 2 shows the windows ME client (192.168.1.99) respsonding to the 
<BR>Samba server (192.168.1.102) with a name query response to port 137
<BR>
<BR>Frame 3 shows the Samba Server linux system sending out an ICMP
<BR>destination unreachable message for port 137. 
<BR>
<BR>This packet sequence is repeatable and I see it many times 
<BR>in the traces
<BR>To me this seems like NBMD
<BR>is not listening on port 137. If so How can I fix
<BR>given all the other steps I've taken?
<BR>
<BR> 
<BR>    
<BR>
       
<BR>
<BR>
<BR>The netstat result looks like this:
<BR>Active Internet connections (servers and established)
<BR>Proto Recv-Q Send-Q Local Address
          Foreign
Address
        State
      PID/Program name
  
<BR>tcp
       0
     0 0.0.0.0:32768
          0.0.0.0:*
              LISTEN
     626/rpc.statd
      
<BR>tcp
       0
     0 0.0.0.0:139
            0.0.0.0:*
              LISTEN
     1578/smbd
          
<BR>tcp
       0
     0 0.0.0.0:111
            0.0.0.0:*
              LISTEN
     611/portmap
        
<BR>tcp
       0
     0 0.0.0.0:22
             0.0.0.0:*
              LISTEN
     786/sshd
           
<BR>tcp
       0
     0 127.0.0.1:25
           0.0.0.0:*
              LISTEN
     846/sendmail: accep
<BR>udp
       0
     0 0.0.0.0:32770
          0.0.0.0:*
                          626/rpc.statd
      
<BR>udp
       0
     0 192.168.1.102:137
      0.0.0.0:*
                          1576/nmbd
          
<BR>udp
       0
     0 0.0.0.0:137
            0.0.0.0:*
                          1576/nmbd
          
<BR>udp
       0
     0 192.168.1.102:138
      0.0.0.0:*
                          1576/nmbd
          
<BR>udp
       0
     0 0.0.0.0:138
            0.0.0.0:*
                          1576/nmbd
          
<BR>udp
       0
     0 0.0.0.0:802
            0.0.0.0:*
                          626/rpc.statd
      
<BR>udp
       0
     0 0.0.0.0:111
            0.0.0.0:*
                          611/portmap
        
<BR>Active UNIX domain sockets (servers and established)
<BR>Proto RefCnt Flags
      Type
      State
        I-Node
PID/Program name    Path
<BR>unix  2      [
ACC ]     STREAM
    LISTENING
    1359   859/gpm
            /dev/gpmctl
<BR>unix  2      [
ACC ]     STREAM
    LISTENING
    1399   907/xfs
            /tmp/.font-unix/fs7100
<BR>unix  2      [
ACC ]     STREAM
    LISTENING
    781
   508/pump
           /var/run/pump.sock
<BR>unix  12     [ ]
        DGRAM
                   1042
  592/syslogd
        /dev/log
<BR>unix  2      [ ]
        DGRAM
                   6292
  1427/login -- root  
<BR>unix  2      [ ]
        DGRAM
                   1578
  932/login -- root   
<BR>unix  2      [ ]
        DGRAM
                   1402
  907/xfs
            
<BR>unix  2      [ ]
        DGRAM
                   1371
  871/crond
          
<BR>unix  2      [ ]
        DGRAM
                   1340
  846/sendmail: accep
<BR>unix  2      [ ]
        DGRAM
                   1293
  806/xinetd
         
<BR>unix  2      [ ]
        DGRAM
                   1230
  759/automount
      
<BR>unix  2      [ ]
        DGRAM
                   1191
  710/apmd
           
<BR>unix  2      [ ]
        DGRAM
                   1088
  626/rpc.statd
      
<BR>unix  2      [ ]
        DGRAM
                   1051
  597/klogd
          
<BR>unix  2      [ ]
        STREAM
    CONNECTED
    462    1/init
[3]
         
<BR></FONT></HTML>
--part1_76.14acf5d9.2956ae39_boundary--