make sure you are using VNET in Win4Lin, I do not think WinSock
networking does works with PcAnywhere (It does some strange protocol things)
I myself am able to run PcAnywhere 10.0 with Win4Lin 3.0 with the VNET
networking
to change from WinSock to VNET networking, login with the username you
use to use Win4Lin and execute
1) 'win_network -vnet'
2) then proceed to the Networking Control Panel and add the following
Network Adapter
Merge/NIC - Merge NIC
3) and add and configure the TCP/IP, Client for Microsoft Networks, and
File/Printinter Sharing protocol as needed.
4) Allow Windows to reboot and Win4Lin should be seen as a seperate
computer on the network and PcAnywhere should now work.
(instructions borrowed from the Win4Lin 3 Manual PDF)
now, if you are already using VNET networking then I do not know what to
say excapt that maybe the VPN software IS getting in the way, because,
as I have previously said, pcAnywhere 10.0 works flawlessly on my end,
but I'm not using any sort of VPN software either.
Chris
>>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
>>
--
"Never again will they hunger; never again will they thirst.
The sun will not beat upon them, nor any scorching heat.
For the Lamb at the center of the throne will be their shepherd;
He will lead them to springs of living water.
And God will wipe away every tear from their eyes."
Revelation 7:16-17
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
