Remote IP Connection via VPN to an Intranetware server
dmo...@sencon.com
I have a working IP VPN connection from a "remote" system into my network,
but I cannot see the Novell (Intranetware) server, although I can ping
it. I have tried setting up the client as IP only, IP with CMD and IP/IPX
to no avail. I suspect that the packets looking for the server are not
going anywhere (local subnet only?). Is there a way to force the client
to look at a specific IP address (as the VPN will automatically handle the
forwarding)? Does 4.11 even support a pure IP login? I have tried
messing with the tunnel settings, but without success (yet!).
Any suggestions would be appreciated. Thanks.
Derek
Donald Albury
NW 4.x servers use only IPX for NCP, so you need an IPX connection,
either direct or tunneled through IP. Novell's current method for
tunneling IPX over IP is SCMD, which requires running SCMD on the
server, and the client installed 'IP with IPX Compatibility'. A
client installed 'IP and IPX' or IPX-only does not use CMD.
Donald Albury
Novell Product Support Volunteer SysOp
Sorry, no replies to e-mail responses
dmo...@sencon.com
I have tried this, but as this capability came out late in the
Intranetware product cycle, none of my books discuss implementing it.
Could you possibly give me some advice on getting the tunnel running? I
am currently getting an error on the server indicating that it cannot find
the board IPTUNNEL... even though I have added it to the system (per TID
10014154).
Thanks,
Derek
Donald Albury
Forget IPTUNNEL. That is old. The preferred method now is SCMD.
Start with TID 10014705
(http://support.novell.com/cgi-bin/search/searchtid.cgi?/10014705.htm)
on setting up SCMD. You can search the knowledgebase for SCMD. Ask
any questions back here that you have along the way.
dmo...@sencon.com
I had already printed out that document and was reviewing it. I also
printed out a number of other TIDs (10069486 "SCMD: Configuration
Parameters" was particularly helpful). Apparently all I needed to do was
LOAD SCMD /BS and properly configure the CMD agent on the client to get
everything working. Woo-Hooo! :-)
Sorry about the delay in responding, but this system administration stuff
is only one of many hats I wear around here.
Thanks for the guidance,
Derek