Richard,
It is very likely that I was part of those threads. I've had this problem
with Win4Lin ever since I started using it, and I was hoping that
NeTraverse might have fixed this. I still do actually. Maybe it's just a
mistake on my part.
The problem with the VNC model that you tout here is that it assumes that
you own the host. I don't. The host belongs to someone else. It's been
running PC Anywhere for years, and it isn't going to change to VNC. I like
VNC, I use VNC, but the PC Anywhere Host (I'm the remote, right?) isn't
going to change because then we'd have to change the remote on about 20
other people's PCs. It isn't practical.
If I'm misunderstanding something here Richard, please clarify for me.
Are you suggesting that there is a VNC remote that will control a PC
Anywhere Host? If so I'd be very happy to try that out, but I don't know
about that one.
Thanks,
Mark
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Richard K
Scotford
Sent: Tuesday, June 05, 2001 1:20 AM
To: [EMAIL PROTECTED]
Subject: Re: [Win4Lin-users] VPN & PC Anywhere 10
Hi,
The PCanywhere issue was an issue I had also with version2. One of the guys
on the beta-list filled me in on the beauty of VNC and I've never looked
back.
I remoteley administer a couple of NT4 Servers via the web and an old
netware
Lite DOS system by dialing direct with pcanywhere in win4lin to a dos
pcanywhere host server.(I haven't tried it in ver3 yet but it worked fine in
ver2).
http://www.uk.research.att.com/vnc/
and for some new work there is the tridiavnc update at
http://www.tridiavnc.com
hope this helps
RKS
On Tue, 5 Jun 2001 12:32, you wrote:
> Hi,
> Well, up until this test Win4Lin 3.0 had really addressed all of the
> problems I had seen in previous releases and half way through the setup of
> all of this I was hopeful.
>
> My machine is RH 7.1 stock, with the prebuilt Win4Lin kernel installed.
> My permanent license came through with no problems. I managed to get a
> couple of apps installed and working, and then went for the tough one -
> Using PC Anywhere under Win4Lin to control a remote PC. If I could do
this,
> then basically I could give up Windows as a at home working environment
and
> keep Windows only for my musical endeavors. So far, not that lucky.
>
> The Microsoft VPN client installed fine, and I am able to connect to my
> office just fine. Once connected, I correctly receive a remote IP address
> via the office DHCP server, and can ping known addresses inside my office.
> Everything looks good.
>
> Then I installed PC Anywhere 10 Remote Only and attempted to connect to
> my office PC, and unfortunately PC Anywhere says there's nothing to
connect
> to. I know there is because I can drop over to my Windows PC at home and
> connect to the office PC, and my Win4Lin environment can ping my office
PC,
> but something going on here can't find the PC Anywhere host at the far
end.
>
> I tried to use PC Anywhere to connect to my home PC and this didn't
work
> either, so I don't think it's the VPN connection.
>
> I'm wondering if anyone has:
>
> 1) Tried this yet?
>
> 2) Does anyone at NeTraverse know that this WILL NOT work for a known
> technical reason?
>
> 3) Know if it could be the default ipchains setup in RH 7.1? I installed
> with 'normal' security, whatever that means. How can I make sure that PC
> Anywhere's port (5631, 5632) are open and not stopping this from working?
> (I know nothing about administering ipchains.)
>
> Again, thanks in advance for any ideas.
>
> Regards,
> Mark
>
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
