-
VPN Blues
I have a client's company I need to be able to access remotley from time to time. I am able to connect to the server (server 2003) with no problem. When trying to connect to the individual PC's I am not able to get a connection. All systems on the network have static IP's and they are a public IP. I have the "allow users to connect remotely to this computer" checked and the firewall turned off. It is not running any programs for internet security such as norton or mcafee. I must be missing something but don't know what. Any help appreciated.
-
I know it's a lame question but it needs asking... are the PCs logging into the server's domain with a username and password?
-
That's not a lame question, I forgot to tell you, there is no domain. Each PC does login with user and password though to be allowed to use an app. on the server.
-
How are you connecting to the server? RDP or what?
If you are establishing a VPN to the client network the you should see the other workstations.
"All systems on the network have static IP's and they are a public IP"
So each workstation has a public IP; or they are behind one single IP?
Lot's more info needed here if you can, thanks.
emr
-
I am connecting to the server using the VPN connection and MSTSC for the static IP of the server. Each of the stations have a static public IP as well. When I am trying to connect to the workstations, I am using the IP address for the station I am trying to connect to.
-
Still wondering if anyone can help????
-
http://www.onecomputerguy.com/networ...vpn_server.htm
This describes setting up XP as a VPN server which might be the issue as the workstations might be refusing incoming connections.
-
Thanks futuretech , will give it a shot and let you know.
-
why even bother with a vpn if you use terminal server? Do you need that level of access?
-
When using Term Svcs, you are taking completely over the PC you are accessing. Usin vpn would allow the user to be mirrored and can communicate wth them via the phone on issues the have.
-
Only in XP it logs any and all users off (TS or console). If you are logging into a 2003 server as you stated before, you don't take it over in any respect. A total of 3 people can be logged in at one time (two TS and one console unless you pay 75 bucks a seat, then you can have ~35 per 3ghz, 4gb ram server).
I personally prefer TS over VPN unless its ABSOLUTELY necessary, which isn't very often. TS is protected enough (encryption, only 1 port to open and if you have NAT router, one port to forward, etc) and in 2003, manageable (boot people out after X hours of inactivity, force 128b encrypt, etc). I'd highly recommend going to this if you just need a "jump site" of sorts.
-
I can understand this, however, even with the TS I can not gain access to the stations. I get the error of "can not connect to IP adress". The router is setup for with the correct open port. I am able to access the server but not any of the stations using TS. This is the question of what I need to do to gain access to the stations even using TS?
-
just so I understand completely -- you log into your 2k3 box via TS then try to TS out to the next computer, say an XP machine?
If thats the case, remember you have to have TS enabled on those comps (right click my computer, properties, remote and check the box) and sometimes the account needs to be added for access.
-
Sory it took so long to get back to you Fubarian, had to get a company back up and running for Monday. I log into the server 2003 with the TS fine. I then log out and try to log into the work station using TS, only to receive the message, " cannot connect. This is where I become baffled since it is a public IP as well.
-
can you do stupid stuff on 2k3 box (I'll refer to it as the ts box from now on) like internet? AND can you do a \\othercomputer\c$?