This is our configuration:

NetWare 5.1 SP 6
BorderManager 3.7 SP 2
SOCKS gateway v4 and v5 enabled
Access control rules for clients are in place and working

The problem is that clients can establish outbound connections through

SOCKS, but they can not receive inbound connections. The SOCKS
define two operations (for v4): "connect" and "bind". The first one is

for outbound connections and is working fine besides the well known
with reply version (which is still not fixed even in SP 3 beta, more than a year and a half after my first report). The "bind" operation is

for inbound connections from server to clients and it is not working properly. When the application send request to "bind" port on SOCKS
server it got malformed reply.

The request packet was:

4 2 0 0 0 0 0 0 0
^ ^
| - command code: "bind"
--- protocol version: 4

And the reply packed was:

4 4 0 0 0 0 0 0 0
^ ^
| - result code: 4???
--- reply code version: 4???

If you look at the SOCKS v4 specification you might notice, that there

is no result code "4". And of course there is no reply code version
it should always be "0".

Could someone persuade Novell to fix that mess at last?

With best regards,
Victor Shkamerda