Private network accessable from outside

[cmdrdredd]

Here's what we have setup at work... a T1 line and every system setup to 192.168.1.x IPs. Now I want to access this network from home or on vacation. I have 5 static IPs available to me but the problem I see is when I change the system to a static IP which I would like to connect to, that system looses connectivity to the private network (192.168.1.x). What do I do?

Basically want to access quickbooks (I know almost nothing about how it works) while not at the building, which resides on a computer connected to the internal network. We have no server, just each office connected to the T1 for internet access and the LAN for file sharing etc.

I've tried different ways and thought of various plans to try, but nothing comes up as workable.

 

[jlazzaro]

ideally you would have VPN setup at your office. however, the quick and dirty way...

use either RDP or UltraVNC and forward the necessary ports on your T1 router to the system running QuickBooks (192.168.1.x). Then, remote desktop to your public ip address, which will then forward the request to the desired system.

EZLAN UltraVNC

 

[cmdrdredd]

I guess that could work, but I have no idea how to log in to the router...I'm not very familiar with this type of network as all of my experience comes from my home networjk (DSL or Cable...very simple).

 

[James Bond]

Originally posted by: cmdrdredd
I guess that could work, but I have no idea how to log in to the router...I'm not very familiar with this type of network as all of my experience comes from my home networjk (DSL or Cable...very simple).

You're going to need to find a way into the router, like said above.

Then, just make sure that whenever a connection comes in, with that port, it forwards everything to YOUR work computer's IP.

 

[ColKurtz]

Forget port-forwarding. Use Hamachi instead. Hamachi is a p2p VPN client, extremely easy to use, secure, and your "real" IP addresses (192.x.x.x) can change without affecting your ability to remote in. One of the best little programs ever, and still free.

You just install Hamachi on several machines, create a "network" for them all to join. That's all there is to it. It's perfect for your scenario.

 

[kevnich2]

You need a commercial grade router that will do one-to-one NAT (takes a public, routable IP address and any traffic it receives, it forwards to that internal IP address). In our office, we have a Sonicwall TZ170. It handles this perfectly. You DO NOT want to assign computers on the internal network a routable IP address, your just asking for security problems. If your current router supports one-to-one NAT, just setup a policy so that all traffic destined for one of your static IP's goes to your internal IP address, then do a port forward for RDP to that internal IP address. That way you only have one port open to the internet on that one computer.

 

[cmdrdredd]

The ISP (I guess you call it that) who installed our T1 told us we can do a "static route" and open up the ports needed for Timbuktu (available on their website). However, in doing this we also lose the ability to access the files on the network after logging in. For example if we put 66.xxx.xxx.xx as the address that has the ports open for, we cannot then login to that system and access the rest of the network which is on 192.168.1.x

We want to control the desktop and then have access to all the files and the rest of the network.

 

[SoulAssassin]

Originally posted by: ColKurtz
Forget port-forwarding. Use Hamachi instead. Hamachi is a p2p VPN client, extremely easy to use, secure, and your "real" IP addresses (192.x.x.x) can change without affecting your ability to remote in. One of the best little programs ever, and still free.

You just install Hamachi on several machines, create a "network" for them all to join. That's all there is to it. It's perfect for your scenario.

Yup