On Sat, Dec 21, 2002 at 08:40:45PM -0600, Christopher R. Hertel wrote: > Note also that none of the calls appear to work properly on port 445. If > the call is made on 445 a Windows server will respond, but the response > will be empty. Listing of NBT workgroups, servers, and shares must be > done on port 139, it seems. I am not sure whether this is true of the > newer NetrShareEnum call. > ^
rpcclient -d 3 -S server -W domain -U administrator -c 'netshareenum 1'
lp_load: refreshing parameters
Initialising global parameters
params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
Processing section "[global]"
added interface ip=192.168.3.2 bcast=192.168.3.3 nmask=255.255.255.254
resolve_lmhosts: Attempting lmhosts lookup for name server<0x20>
resolve_hosts: Attempting host lookup for name server<0x20>
Password:
Connecting to host=server share=IPC$
Connecting to 192.168.3.1 at port 445
^^^
Doing spnego session setup (blob length=118)
got OID=1 2 840 48018 1 2 2
got OID=1 2 840 113554 1 2 2
got OID=1 2 840 113554 1 2 2 3
got OID=1 3 6 1 4 1 311 2 2 10
got [email protected]
lsa_io_sec_qos: length c does not match size 8
netname: IPC$
remark: Remote IPC
<snip list of remaining shares>
Looks like this call works fine on port 445.
--
Steve Langasek
postmodern programmer
msg05052/pgp00000.pgp
Description: PGP signature
