| Title: | PATHWORKS V5 for DOS and Windows |
| Notice: | OS2LAN::OS2:[PUBLIC] is alive again, but not what it used to be |
| Moderator: | RANGER::CURLESS |
| Created: | Fri Feb 11 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 7404 |
| Total number of notes: | 27276 |
We have Windows NT/95 clients on the inside of an AltaVista Digital
UNIX Firewall with a Windows NT V3.51 server and PATHWORKS for OpenVMS
V5.0A server both on the outside of the firewall. We are running the
TCP/IP protocol exclusively.
We defined a Start-of-Connection packet filter in the firewall that
enables a Windows NT/95 client to make an outbound initiated connection
to either server on port 139/TCP but permits only the corresponding
inbound connection as an ACKed response. In other words, a reverse
inbound initiated TCP connection from either server is not allowed by
the firewall.
The Windows NT/95 client can successfully connect to a share point
offered on the Windows NT server but NOT to the PATHWORKS OpenVMS
server.
A sniffer analysis of the Windows NT/95 to PATHWORKS NetBIOS-over-IP
attempted connection to port 139/TCP reveals that this server performs
a reverse inbound intiated connection back to the client - ugh!
Can anyone explain why this difference exists? Is there any way around
this problem?
Please advise.
\Thanks in Advance
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 7347.1 | nova05.vbo.dec.com::BERGER | Tue Mar 04 1997 12:53 | 5 | ||
The license check maybe ? Anyway, this probably belongs more to the V5 VMS server conference since no PATHWORKS client is involved. Vincent | |||||