Displaying 2 results from an estimated 2 matches for "petep".
Did you mean:
peter
2000 Jul 05
0
smbclient -p <port> worked in samba 1.19.18p10, not in samba 2.x
...nux machine or my NT
machine respectively.
Here are two tests from the same Solaris machine, first with the current
Samba and second with the 1.19.18p10 version.
--------------------
seadog> echo 'some message to home machine' | /opt/samba/bin/smbclient -p $LINPOP -I hashbang.dhs.org -M petep
timeout connecting to 24.147.30.33:139
Connection to petep failed
--------------------
Note that smbclient tried to connect to port 139, not port $LINPOP.
With the old Samba, it works as advertised in the man page:
--------------------
seadog> echo 'other message to my home machine' | /...
2000 Jul 16
1
"smbclient -p <port>" appears to be broken in Samba 2.x
...ux machine or my NT
machine respectively.
Here are two tests from the same Solaris machine, first with the current
Samba and second with the 1.19.18p10 version.
--------------------
seadog> echo 'some message to home machine' | /opt/samba/bin/smbclient -p $LINPO
P -I hashbang.dhs.org -M petep
timeout connecting to 24.147.30.33:139
Connection to petep failed
--------------------
Note that smbclient tried to connect to port 139, not port $LINPOP.
With the old Samba, it works as advertised in the man page:
--------------------
seadog> echo 'other message to my home machine' |...