Symantec PCanywhere10.0 & Remote Desktop Used

[Joe]

Hello Everyone,
I have tried to explain with user education but, I have an enduser whom
still insist on using Symantec's PCanywhere version 10.0 on their xp pro
workstation within a new Small Business Server 2003 Standard domain, to
connect with any another site to do syncronization of files. The challenge
is that when attempting to install the Symantec product I get an error
message warning of disabling the RDP or Terminal Services on the local
machine.What should I do? Anyone every run into this situation? I have
posted to several different groups hoping for an expierienced answer. As
allways, I am humbly grateful for your feedback. SBS Rocks!!!!!

Joey

 

[Frank McCallister SBS MVP]

Hi Joe

PCNowhere 10.0 for starters is not compatible with XP Pro 10.5 or later is
required as 10.0 replaces a DLL which escapes me at moment (something like a
heart attact angina).

10.5 can be made to work but RDP, RWW, and VNC are much better solutions. I
wouldn't allow PCNowhere on a SBS network myself.

 

[Jack]

Hi
Or suggest to the End user to try the Free Ultr@VNC.
Setting VNC: : http://www.ezlan.net/vnc.html
Jack (MVP-Networking).

 

[Jim Vierra]

pcAnywhere will create a big headache in a domain if you install the "host"
components. You need the latest version of pcAnywhere to work at all with
XP in an SBS environment. 10.0 IS NOT COMPATIBLE WITH XP.

 

[scott harman]

msgina or something along those lines -
yeech - it's a bit silly to consider pcanywhere given the issues it can
cause. a client of mine did much the same with 8 servers at my location.
messy and expensive to correct their it dept's assumption (i.e we had to use
pcanywhere with nt4 - why can't we use it with windows server 2003?).
I'd tell them they're creating a major technical issue - and their
environment is now unsupportable. i'd agree - vnc is worth the license
fee - since it's now so much better under multi-os environments. however -
rdp works exceptionally well and has got me out of a jam more than once.
ssh and sftp have good safe working ports under windows environments - and
sftp is probably the best and safest way of syncing files between
servers/desktops.

atb

scotty

 

[Jim Vierra]

To fix XP after a failed 10.0 install run SFC /scannow. XP will be very
unstable and fail to authenticate in an AD environment if 10.0 has been
installed.

Be sure to fix Gina "msgina.dll" before trying to upgrade to 10.5. Only
install remote. Do not install host on W2K server or WXP.

!0.5 is good for W2K workstation and NT 4. Used it for years with no
problems.

Need Service pack for 10.0 to install on W2K from Symantec. Apply service
pack after install but before any reboot. reboot will lock you out of W2K.

 

[Interrogative]

Hi Joe

PCNowhere 10.0 for starters is not compatible with XP Pro 10.5 or later is
required as 10.0 replaces a DLL which escapes me at moment (something like
a heart attact angina).

10.5 can be made to work but RDP, RWW, and VNC are much better solutions.
I wouldn't allow PCNowhere on a SBS network myself.

Care to share why?

I am not defending it - don't get me wrong - but I have used it many times.
I have used 10.5 and 11 on XP and though sometimes you get connect probs,
most of the time it runs well enough to get the job done.

 

[Interrogative]

To fix XP after a failed 10.0 install run SFC /scannow.

Much easier to do a system restore.

 

[Bob Genestet]

If you need to interact with the logged on user or transfer files, I would
reccomend NetMeeting.
Microsoft has been considering dropping NetMeeting and probably will in
their next OS.

Thanks,
Bob

 

[Interrogative]

Skype and XP's own Remote Desktop. You would find it works and is free.