VNC Viewer & ATT Uverse 2Wire Modem Error 11004

I just signed on to ATT uverse. I have a home wireless network through the ATT modem that works fine.

Desktop running WinXp is wired to the ATT modem.
Gateway Laptop running Win7 Home Premium 32 bit
HP Laptop running Win7 Home Premium 64 bit.

I am trying to get the HP laptop to access the desktop from offsite via VNC viewer. I can access the desktop when the laptop is at home. When I get off-site and try to log into vnc viewer I get and 11004 error message.

Does anyone know how to resolve this issue?

Thanks

 

Switch to Teamviewer.

 

Thanks for the advice. However, I am unfamiliar with TeamViewer. My brief review on their website suggests that it requires action by parties on each computer before access is granted. Am I wrong about that?

With vnc Viewer I was able to access my computer off site without anyone else doing anything.

 

Do you have VNC ports forwarded to the XP machine on your AT&T 'modem'?

It would be a good idea to set the XP up with a static IP if you want to ensure this connection works everytime.

 

Teamviewer can be set up to run without user intervention, and no ports to open. A lot more secure option than VNCviewer.

 

Foogoo,

Thanks for the reply. I do have the modem settings to open the ports for vnc. As I recall these are ports 5800 and 5900. I did set the modem for a static IP address for the XP. The modem sets one and it also shows a "public" IP address that is different. I don't understand this. I also think that there is some setting on the modem that I am missing.

I am accessing my XP computer via DynDNS. I have also set the ATT modem to open the ports for Dns. I think I did it correctly but am not sure.

 

OK, the staic IP has to be set on the XP computer not the router, unless you mean your reserving the IP on the router so it doesn't get handed out via DHCP.
You have dydns running on the XP machine updating you public ip and resolving to a name you have picked, good deal.
The router needs the ports forwarded to the XP machine, somewhere is the router you can do that.
port 5900 forward to the XP static IP
port 5800 forward to the XP static IP


The public IP is your address on the internet, it maybe static (not likely) or dynamic (changes occasionly) that is where dydns comes into play.
Private IPs are the ones used by you network, the devices you have connected and are not used past the router, this is called NAT'ing, its a service the router provides.

 

Foogoo,

Thanks for all of the info. I do have the ports forwarded as you suggested. Do I want Dyndns looking for the public IP or the private IP?

 

DyDNS doesn't need to be looking at nothing. It automatically finds your public IP and updates the DyDNS server if it changes.
Here is the logic.
DyDns is used to resolve your public IP to a name so instead of 65.189.12.100, you type mypc.dydns.com and it sends the data to your Internet -Public IP.
Dydns client insures that if you public IP changes their server will have the most up to the minute IP.
Ok now you have a connection to your IP, we have to get past the router. The router receives the request for port 5900, looks at its rules and says port 5900,eh? The client at 192.168.1.100 wants that info, so it sends it to the local IP address via port 5900. Now the PC at 192.168.1.100 must have a service running monitoring port 5900 or all is lost, the packet is rejected.
Now if the PC at 192.168.1.100 is not static then it could change its IP when the next DHCP lease request is made, then when the router send the packet to 192.168.1.100 and finds no one home, its rejected again.
Notice the ports, names annd IPs may of been changed to protect the innocent.

If it is not working now I fear you may of changed something else.

Test it out here
http://gotomyvnc.com/

 

Foogoo,

Thanks.