command srvshares in rpcclient 2.0.7 hangs server
Wilhelm Chana
samba at ws6539.sie.Siemens.at
Thu Jun 8 12:12:32 GMT 2000
We are using rpcclient to test for shares on windows machines.
Command srvshares in rpcclient version 2.0.0 did the job. Now we liked upgrade
to rpcclient version 2.0.7, however faced the problem that the command srvshares
times out and leaves the machine on the other end in a blocked condition.
The first response is: cli_pipe: return critical error. Error was code 0
Subsequent connections report that:
cli_nt_session_open: cli_nt_create failed on pipe \srvsvc to machine PC0510SD. Error was ERRDOS -
ERRpipebusy (All instances of the requested pipe are busy.)
See the following log:
cd /home/chan/samba-2.0.7/source
security# bin/rpcclient -S PCxxxxxxx -I 111.111.111.111 -U % -W PCxxxxxxx -n SECURITY
added interface ip=222.222.222.10 bcast=222.222.222.255 nmask=255.255.255.0
smb: \> lsaq
lsaq
LSA Query Info Policy
Domain Member - Domain: DOMAIN SID: S-1-5-21-496132549-597184365-1849977318
Domain Controller - Domain: PCxxxxxxx SID: S-1-5-21-1461015677-1148614760-612134452
smb: \> srvi
srvi
Server Info Level 101:
PCxxxxxxx Wk Sv Sql Din NT PtB
platform_id : 500
os version : 4.0
smb: \> srvsha
srvsha
cli_pipe: return critical error. Error was code 0
smb: \> srvsh
srvsh
cli_nt_session_open: cli_nt_create failed on pipe \srvsvc to machine PCxxxxxxx. Error was ERRDOS -
ERRpipebusy (All instances of the requested pipe are busy.)
smb: \> q
q
security# !!
bin/rpcclient -S PCxxxxxxx -I 111.111.111.111 -U % -W PCxxxxxxx -n SECURITY
added interface ip=222.222.222.10 bcast=222.222.222.255 nmask=255.255.255.0
smb: \> lsaq
lsaq
LSA Query Info Policy
Domain Member - Domain: DOMAIN SID: S-1-5-21-496132549-597184365-1849977318
Domain Controller - Domain: PCxxxxxxx SID: S-1-5-21-1461015677-1148614760-612134452
smb: \> srvi
srvi
cli_nt_session_open: cli_nt_create failed on pipe \srvsvc to machine PCxxxxxxx. Error was ERRDOS -
ERRpipebusy (
All instances of the requested pipe are busy.)
smb: \> q
q
What I have found is the difference between version 2.0.0 and 2.0.7 when debug level is 10 at this point:
Version 2.0.0:
[000] 5C 50 49 50 45 5C 00 00 00 05 00 00 03 10 00 00 \PIPE\.. ........
[010] 00 60 00 00 00 09 00 00 00 48 00 00 00 00 00 0F .`...... .H......
[020] 00 01 00 00 00 0B 00 00 00 00 00 00 00 0B 00 00 ........ ........
[030] 00 5C 00 5C 00 41 00 33 00 30 00 30 00 30 00 31 .\.\.A.3 .0.0.0.1
[040] 00 33 00 32 00 00 00 00 00 01 00 00 00 01 00 00 .3.2.... ........
[050] 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 ........ ........
[060] 00 FF FF FF FF 00 00 00 00 ........ .
write_socket(4,176)
write_socket(4,176) wrote 176
got smb length of 348
size=348
Version 2.0.7:
[000] 5C 50 49 50 45 5C 00 00 00 05 00 00 03 10 00 00 \PIPE\.. ........
[010] 00 54 00 00 00 09 00 00 00 44 00 00 00 00 00 0F .T...... .D......
[020] 00 01 00 00 00 0B 00 00 00 00 00 00 00 0B 00 00 ........ ........
[030] 00 5C 00 5C 00 41 00 33 00 30 00 30 00 30 00 31 .\.\.A.3 .0.0.0.1
[040] 00 33 00 32 00 00 00 00 00 01 00 00 00 01 00 00 .3.2.... ........
[050] 00 00 00 00 00 FF FF FF FF 00 00 00 00 ........ .....
write_socket(3,164)
write_socket(3,164) wrote 164
read_socket_with_timeout: timeout read. select timed out.
That means the data written to the pipe in version 2.0.7 are shorter than in version 2.0.0.
We are working with Sun Solaris 2.7 and gcc version 2.8.1. We tried it on both Ultra Sparc 60/360 and Sparc
5/170.
So far we can live with rpcclient 2.0.0, however it would be nice to have the opportunity to upgrade.
Best regards.
--
Wilhelm Chana E-mail: Wilhelm.Chana at siemens.at
CCN SECURITY Phone: (+43) 51707 29390
Siemens AG Austria Fax: (+43) 51707 59390
Siemensstrasse 92
A-1211 Wien
More information about the samba-technical
mailing list