James Long
2000-Sep-22 20:28 UTC
'Resource temporarily unavailable' with 2.0.7 under FBSD 4.0R
Samba 2.0.7 on 4.0R: [2000/09/21 10:55:51, 0] smbd/oplock.c:open_oplock_ipc(93) open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Resource temporarily unavailable Clues appreciated. Also, even with the 'wins server' line and 'name resolve order' set to use wins only, nmblookup still says: pbssamba:/usr/local/etc> nmblookup pdx-james querying pdx-james on 172.16.1.255 172.16.1.247 pdx-james<00> Note that nmblookup is querying on the broadcast address, rather than using the wins server. How can I get nmbd to talk to the WINS server instead of broadcasting? smb.conf is: # NOTE: Whenever you modify this file you should run the command "testparm" # to check that you have not many any basic syntactic errors. # #======================= Global Settings ===================================[global] workgroup = XXXXXX security = share # security = user # domain logons = true # NetBIOS name = JLRserver wins server = 172.16.1.2 # name resolve order = wins lmhosts hosts bcast name resolve order = wins [test] comment = For testing only, please path = /usr/ports read only = no guest ok = yes writeable = yes [root] path = / read only = no writeable = yes guest ok = yes # [homes] # writeable = yes # [printer$] # path = /usr/local/etc/smb/printers # public = yes # writeable = no # browseable = yes [printers] comment = All Printers path = /var/spool/samba browseable = no # # Set public = yes to allow user 'guest account' to print guest ok = yes writeable = no printable = yes
James Long
2000-Sep-25 19:02 UTC
'Resource temporarily unavailable' with 2.0.7 under FBSD 4.0R
I'm running Samba 2.0.7 on FreeBSD 4.0R. I am *not* running smbd via inetd. It appears that samba will allow one Windows client to connect, and on subsequent attempts, I get an entry in log.smb that reads something akin to: [2000/09/21 10:55:51, 0] smbd/oplock.c:open_oplock_ipc(93) open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Resource temporarily unavailable This suggests to me that smbd is having trouble opening a UDP socket on the localhost (lo0) interface. Pinging that interface works fine, and I have the ipfw rules set to allow all traffic on lo0. How can I eliminate this error? Also, even with the 'wins server' line and 'name resolve order' set to use wins only, nmblookup still says: pbssamba:/usr/local/etc> nmblookup pdx-james querying pdx-james on 172.16.1.255 172.16.1.247 pdx-james<00> This appears to indicate that nmblookup is querying on the broadcast address, rather than using the wins server. How can I get nmbd to talk to the WINS server instead of broadcasting? Thanks, James smb.conf is: # NOTE: Whenever you modify this file you should run the command "testparm" # to check that you have not many any basic syntactic errors. # #======================= Global Settings ================================[global] workgroup = XXXXXX security = share # security = user # domain logons = true # NetBIOS name = JLRserver wins server = 172.16.1.2 # name resolve order = wins lmhosts hosts bcast name resolve order = wins [test] comment = For testing only, please path = /usr/ports read only = no guest ok = yes writeable = yes [root] path = / read only = no writeable = yes guest ok = yes # [homes] # writeable = yes # [printer$] # path = /usr/local/etc/smb/printers # public = yes # writeable = no # browseable = yes [printers] comment = All Printers path = /var/spool/samba browseable = no # # Set public = yes to allow user 'guest account' to print guest ok = yes writeable = no printable = yes
Josh Durham
2000-Sep-26 00:55 UTC
'Resource temporarily unavailable' with 2.0.7 under FBSD 4.0R
As far as I know, nmblookup doesn't use the smb.conf file to figure out how to resolve, you have to tell it manually. Try doing a nmblookup -U <WINS Server> -R <NetBIOS name> If you want to make sure nmbd is resolving names the right way, you have to bump up the log level. I think running ./nmbd -d 5 is right, and I think (by looking at the source, I havn't tested this,) you should be looking for a line like: query_name_response: On subnet %s - positive response from IP %s for name %s. IP of that name is %s Hope this helps. Don't know about your resource problem, though. Can you do things like telnet localhost? (ie, normal loopback communcations work?) - Josh You wrote: Also, even with the 'wins server' line and 'name resolve order' set to use wins only, nmblookup still says: pbssamba:/usr/local/etc> nmblookup pdx-james querying pdx-james on 172.16.1.255 172.16.1.247 pdx-james<00> This appears to indicate that nmblookup is querying on the broadcast address, rather than using the wins server. How can I get nmbd to talk to the WINS server instead of broadcasting? * Josh Durham | AOE at Virginia Tech | (540) 231-9061 jdurham@vt.edu *