View Single Post
Old 19-06-2004, 11:48   #13
Stuartbe
Inactive
 
Join Date: Jan 2023
Posts: 4,984
Stuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this point
Stuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this point
Re: remote assistance within XP

Quote:
Originally Posted by monkeybreath
Doesn't windows remote assistance use port 135?? (haven't used it myself so can't be sure)

If so, then port 135 is blocked on the ntl network which is why you are having the problems.

Try installing tight VNC on both computers and letting the firewall allow the program to connect, then you should be able to access remotely.

MB
MB
Terminal services ( remote assistance ) uses port 3389 m8 so a blocked port is not going to be the problem.

My money is on the firewall configuration.
Stuartbe is offline   Reply With Quote