Remote Desktop and/or PCAnywhere Problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a number of machines (All XP pro) both on my home network and at work.

I use normally PCAnywhere for remote access to the two networks.

I have over the last few days tried to connect to two machines not connected
to before. One a desktop at home and on a laptop that travels between the two
sites. The PCAnywhere host program has been run on both machines, but they
cannot be seen from other machines on the network. This includes each other.
A ping suggests that both machines respond OK. The shared folders on both
machines can be seen from all other machines on the network.

Moving on from there, I thought it was a PCAnywhere problem. Hence I
switched to remote desktop, but the problem is still there, no connection can
be made.

I have moved the laptop from home to work, and the problem is still the same.

What could be the cause? Its as though the machines are deaf to the remotes
looking for them.
 
Any personal firewall software running on either machine that may be
blocking Remote Desktop? NAV worm protection and OneCare Live Beta can also
cause issues...

As far as Remote Desktop is concerned see this troubleshooting information
for possible help...

http://theillustratednetwork.mvps.o...pSetupandTroubleshooting.html#Troubleshooting

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Hi

There are no firewalls running except the standard windows one (which I have
tried to switch off with no effect)

Froman AV point of view I use Sophos, what is Onecare Live? I have never
heard of it so don't think this is an issue.

What ports should I look for in netstat -a? I have not modified any of the
listeningports from default.
 
As noted in the troubleshooting section you need to verify TCP Port 3389 is
listening...

Sophos on both PCs? Try disabling that or uninstalling...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
I think that may be the problem.

TCP Port 3389 does not appear at all with netstat -a.

Nor does 5631 which I think is the PCAnywhere port.

Is it easy to enable these?


Sorry but I am not very experienced with this kind of process.

Thanks in Advance
 
Again from the troubleshooting section you need to start the Terminal
Services service and make sure it is configured for "Automatic"... I can't
speak to PCAnywhere...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
I have confirmed that Terminal services is started and set to automatic.
Still no port 3389 listeneing though.

One question mark I have is that in the list of devices for the remote
connection (on the host machine) there is no network interface only the
modem. Is this correct? If not how can I get this listed.
 
Hmmm... What list is this?

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
I went to Network Connections

Under Incoming I clicked Incoming Connections

Incoming Connections Properties gives a list of divices to allow incoming
connections on. The network adaptor isn't in this list. Is that relevant?
 
I have looked at the Symantec Site, and following Knowledgebase articles on
their and using telnet I have confirmed that ports on the machines causing
problems are not open and listening. How do I get them to open?

PC Anywhere uses port 5631 and 5632 whereas RD uses 3389, but both on the
machines casuing problems all three of these ports are closed.
 
No that is not relevant...

Have you tried removing this Sopho AV program? Its possible that is blocking
RDP and PCAnywhere inbound...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
I have now found out how I can make the connections work, but this does not
help from a remote point of view, only within the office.

If I open up a telnet screen on both machines.

The type open x.x.x.x 3389 on both machines where x.x.x.x is the others IP
this opens the ports up and allows a connection.

The question I need to answer now is how do I make the ports open
automatically.?
 
Well, I don't know then. If the Terminal Services service is started but the
PC is not listening on TCP Port 3389 then the last thing I can think of is
to make sure you check dependencies for Terminal Services. They should also
be started...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
I seem to have found the cause (and hence the solution.

On the machines that are 'invisible' I am running the VPN client software
for our Symantec Box. This has a 'port control' option, which allows
restriction of ports unless they have been recently used. Hence the reason
why if I telnet out (and use the port) this then stays open until reset.

The Symantec VPN software also has an option to leave all ports open. This I
presume is a type of rudementary firewall, which I have now set to totally
open, which seems to have solved the problem.
 
Thanks for the feed back...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Back
Top