Sunbelt Remote Administrator software: problem connecting

I am evaluating "Remote Administrator" software from Sunbelt. I put the software on two computers at home and it works great. My main computer is the server and my wireless laptop is the viewer. I have a cable connection with a router so the program sees the routers IP. It has no problem connecting.

The problem is when I take the laptop to a different location (work) and try to connect I get an error message saying it can't connect to server.

 

Help please

 

Yes it is. I believe its the routers address.

I tried to use two different laptops at a different location where there was no router involved and dial-up was used and got a "cannot find server" error.

 

You will need to use your ISP's IP address to access your home network "outside" the network not your internal 192.168.#.#. If you go to Network Connections, right click your connection, then go to properties and details...you can find that IP address. That is the one you will need to use.

Good luck.

 

It is set to obtain an IP addess automatically. I don't have a static IP.

 

Win98 - Start > Run > winipcfg

Win XP - Start > Run > cmd. Then ipconfig

This will tell you the IP Address of the server, but probably won't help. It is likely a 198.162.x.x address. You need the "external" IP Addrss of the router and then you need to configure it to "forward" the packets.

DRD

 

The other way to go is to use one of the dynamic DNS services on the internet. Then set up your system to connect by name (fully qualified domain name: so mycomputer.adomain.com rather than mycomputer).

However, if the other network you are going to is using network address or port address translation (NAT) on the router, you would need to set up port forwarding too.

If you have a static PC you are administrating remotely, then with a little effort you should be able to get it working. If you want to roam around remotely administrating different computers in different places, you are going to find it very difficult unless you have very obliging network admins.

 

I notice in my previous post I transposed the IP numbers. Should be 192.168.x.x

Sorry

DRD

 

I noticed that, its OK. I'm still trying to figure out if this is worth it.

I tried a couple of laptops at work with dial up (no router) and still had a problem with it.

 

If the "server" has a 192.168.x.x address, this will not get routed across any sort of connection. These addresses are designated non-routable, except in private networks. This means you will not be able to connect to it from outside.

However, it may be possible to address the packets to the router (public address) and have it forward them. This generally requires that you specifiy that requests to the specific port being accessed be forwarded to another address, the server.

DRD

 

I went into the routers set-up and found the actual IP on the Status page. I also forwarded the port the program suggested. I took the laptop off of the network and dialed up to get online. I used the IP I found and used the laptop to connected to my home computer. Although it works very slow with dial-up, it actually worked. I'm going to take the same laptop to work tomorrow and see if it will connect from there.

 

Here's hoping.

DRD

 

Another easy way to find out what WAN IP your at through a router is www.whatismyip.com

 

As I posted earlier I had success at home and now I've succeeded in getting it to work at work. One thing that was a problem was the Windows XP firewall. Once turned off and the proper IP used, all went well.