Hi, Dave.
I think that the cisco client changes the
default route on the win98 to point to the corporate
network. Therefore the VNC connection is dead from
that moment.
An easy workaround can be used on the win98 machine.
Before you start the cisco client, add a host specific
route for the w2k machine to the routing table
on the win98.
If you need info about how to add the host specific
route, send me an email. Then you should post
a summary to then list.
Regards,
Miroslav Luptak
>
> on my home lan i can use vpn to go from my main machine
> (win 2000 pro) to a win98 machine.
>
> on that win98 i can run cisco vpn 2000 client window to
> attach to a corporate vpn.
>
> i'd like to access the vpn remotely by attaching to the win
> 98 machine via vnc and then run the cisco client. problem
> is that after i attach via vnc and then run the cisco
> client, i then enter a password and the connection via VNC
> goes dead.
>
> i assume the cisco client is killing vnc somehow or there is
> a conflict. r there any workarounds i can try? the cisco
> stuff will not run on win 2000 so i need to do it this way
> cuz my real intention is to use my win 2000 laptop remotely
> to attach to the win98 machine to ultimately get to the
> vpn...thanks in advance, dave
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
