VPN for dummies

help!

[mcjohnson]

I have a client who, unlike the 99% of my previous clients who use shared hosting, has their own server.

It's a windows server w/ PHP and MySQL installed. I need to access MySQL to set up a database so that I can run a CMS on their public web server (different server)

I have so far, been flummoxed. They would like me to access their network via VPN to get all of this accomplished. I can connect via a VPN connection....but then what?

In order to "see" the computer at the other end of the VPN connection, how do I do that? I get a "connected to the network" message once the VPN connection goes through, but I can't view the computer on the other side.

Do I use remote desktop connection at that point?

Any quick thoughts would be GREATLY appreciated.

[LifeinAsia]

Basically, once you have connected to the network, it's as if the remote computer was on your local LAN. So Remote Desktop should work just like RDing into a computer on your LAN.

[phranque]

get something like putty or another terminal client.
then you should be able to telnet or ssh to the server if it's all set up correctly...

[mcjohnson]

ok...this is going to sound like a really ridiculous question...

but, I was able to connect to the client's VPN connection. Now, I open up "remote desktop connection", and it's promtping me for the "name" of the computer...

hmmm....should that show somehwere? If I click "browse for more" it simply shows me my OWN computer.

the address I used to VPN is vpn1.mywebsite.com or vpn2.mywebsite.com

am I looking to use the IP address of the server I am trying to connect to?

sorry for the newbie questions. Any help would be appreciated.

[LifeinAsia]

You can use the IP address or the computer name.

[jtara]

I was able to connect to the client's VPN connection. Now, I open up "remote desktop connection", and it's promtping me for the "name" of the computer...

The client will have to tell you this.

It's as if you have a very long Ethernet cable connecting your network and their network.

Of course, you will not know what is at the other end unless your client tells you.

You will need the IP addresse(s) of the server, and any other equipment that you will be working with (router, firewall, etc.) In case a router NATs to their internal network, make sure you specify that you need the PRIVATE (internal) IP address(s).

DNS names probably won't be very useful, unless they also give you the address of a DNS server to resolve them.

[LifeinAsia]

No, DNS names probably won't be helpful. I'm talking about the actual computer name (e.g., "workstation1"). That's what I do when I need to Remote Desktop into a client's machine on a VPN:
1) Connect to the VPN
2) RD to workstation1
3) Logon to workstation1
Bam- I'm in.

[jtara]

No, DNS names probably won't be helpful. I'm talking about the actual computer name

Not sure what an "actual computer name" is. Some people do name their computers, like they might a pet, but somehow I don't think that is what you are talking about.

Do you mean "NetBios name"? That only applies to Windows machines, though.

Linux machines have a DNS name and a host name, which may or may not be the same. Which one is the "actual" computer name, though?

In any case, you client is going to have to tell you.

[dbdev]

i think you need to be in the same workgroup... is there a domain controller on the VPN server?