Re: can't connect remotely

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks for the responses. I'm not very computer literate, so i didn't
understand all of your questions to even give you a satisfactory answer. What
i did understand, i can get with my system adim. at work and go from there.
Thanks so much.
Nubspeace

"Pegasus (MVP)" wrote:


"nubspeace" <nubspeace@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3EF50473-3439-459B-B910-886E4CEBEAC9@xxxxxxxxxxxxxxxx
my home computer is running xp home. so why is it, that i can't connect
from
work?

"Malke" wrote:

nubspeace wrote:

i can't connect to my home computer from work remotely. I've gone
through the connection wizard and set up my home computer to accept
remote access and i put in the correct ip address, but it wont
connect. My computer name is my first name. should it be my ip
address?

When you say you've set up your home computer to accept remote access,
does that mean that you've opened required ports in the firewall and -
if the machine is behind a NAT router - given the computer a static IP
address and forwarded the ports from the router's configuration? Does
your office security allow the remote access ports to be opened in its
firewall?

In addition to those questions, what version of XP is the home computer
running - Home or Pro (you cannot access the home computer w/Remote
Desktop Access if it is running Home Edition)? If you get error
messages, what is the exact text?

Malke
--
MS-MVP Windows User/Shell
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"


To paraphrase Malke's excellent reply:
- You must install a product such as WinVNC on your home PC.
- You must determine the ***external*** IP address of your
home PC.
- You must use this external address when starting a connection
from your office PC.
- You must give your home PC a fixed internal address.
- You must create a tunnel on your home router so that
the WinVNC packets are directed to the fixed internal
address of your home PC.
- You must set your home PC firewall so that it does not block
your WinVNC packets.
- You must discuss your approach with your network administrator
in the office to ensure that the work firewall does not block
your attempts.
This is not a trivial process. Perhaps you can get your network
adminstrator at the office to assist you.



.

Relevant Pages

  • Re: Messenger Service on W2K server
    ... > a lot of conflicting information about what other ports may be used. ... > an IIS RPC proxy that would enable clients to access RPC services ... > behind a firewall through port 80. ... I wasn't sure if it would also break remote access ...
    (microsoft.public.security)
  • Re: Can only connect to local RWW, over internet cannot
    ... It has a hardware sonicwall firewall. ... setup of this configured firewall ports as below. ... If you have two NICs on the server then go to Routing ... I have run ceiw tool, recreated ssl cert, Run remote access tool etc ...
    (microsoft.public.windows.server.sbs)
  • Problem in remote access of outlook due to random port
    ... I need some help regarding remote access of outlook. ... Then we have to identify new ports and open those ports in firewall. ...
    (microsoft.public.exchange.admin)
  • Problem in remote access of outlook due to random port
    ... I need some help regarding remote access of outlook. ... Then we have to identify new ports and open those ports in firewall. ...
    (microsoft.public.outlook.installation)
  • Problem in remote access of outlook due to random port
    ... I need some help regarding remote access of outlook. ... Then we have to identify new ports and open those ports in firewall. ...
    (microsoft.public.exchange.admin)