2
For a month or so (up to about 2 weeks ago), I was regularly VPN'ing to our work server, and then immediately RDPing to the SAME server using the servers IP address (we aren't behind a NAT).
So assume my server's internet address is 100.1.1.20
I would VPN to 100.1.1.20 and then RDP to 100.1.1.20
It worked perfectly. If the VPN wasn't on, RDP didn't work, so it must've been going through the VPN.
Same thing for accessing files, VPN in and then type \\servername\ or \\100.1.1.20\ and you could see the files on the server.
Fastforward to today, we haven't changed any configuration on the server, but now its not working. The local computer expert says that it should never have worked that way in the first place, and now we need to add another internal IP and adjust the DNS and all sorts of things.
I'm very frustrated, because I KNOW it used to work.
can anyone shed some light on what could be going on?
When you VPN in now, can you do an IPCONFIG/ALL and post the results? I am more interested in the VPN's interface. We you doing RDP using IP address, or host name (it would seem IP based on the question, but just checking)? – KCotreau – 2011-08-05T05:21:45.123
Incidentally, it would have been fine for your to VPN into the server, and then RDP to it provided your local VPN connection was given a different IP address. I do it all the time. The key is that YOU get a different IP address. Your expert was not correct. – KCotreau – 2011-08-05T05:24:24.513
Ok, something new has happened... today i can VPN in and then access the fileshare at the same server ip address. so whatever was change before has been unchanged. any ideas where i could get a list of the things have been recently changed? also I want to be clear, no matter if you are on the local lan or the world-wide-web, the IP address of all computers at this office is the same (no nat). – user92979 – 2011-08-09T05:39:54.483