| > Is it possible for a remote user (Windows 95 / PATHWORKS32) to connect
> to shares on a PATHWORKS Server if the server is not running TCP/IP?
> The customer will be using a PPP connection to their DECServer700.
In that case, no. I think the easiest solution is to
add TCP/IP to the destination PATHWORKS Server.
If they dial in to a Windows NT RAS server with NetBEUI
and the RAS server shares a network protocol with the
destination PATHWORKS Server then it can be made to work.
If they dial in to a DECrouter (DDCMP Server) and the
destination PATHWORKS Server runs DECnet then it can
be made to work.
> Will LAT work on dial-in?
Again, if they want to use PPP the easiest solution would
be to add TCP/IP to the destination PATHWORKS Server. They
could then use TELNET for multiple terminal sessions at the
same time they are using file and print shares.
If they dial in to a DECrouter (DDCMP Server) and the
destination PATHWORKS Server runs DECnet then they can use
CTERM instead of TELNET.
Not all the way from the PC to the PATHWORKS Server. They
can configure their DECserver 700 to act as both a terminal
server and PPP server. They could connect to the DECserver
700 and have the DECserver 700 connect (via LAT) to the
destination PATHWORKS Server. This will, of course, not
provide access to shares.
|