Access same windows server via different IPs and gateways

Question

I have Windows server 2012 has One LAN with two IPs as follow

IP - Mask - Gateway

and the client 192.168.1.5 255.255.255.0 192.168.1.1

Router IP is 192.168.1.1

I need to access (file/print, remote desktop, IIS,ping) the server using the IP 50.65.1.52 without changing the client IP

By the way the second IP (50.65.1.52) is static (Real IP)

by access, do you mean, file/print, remote desktop, IIS? If the WAN router/firewall is setup correctly, it's likely a local firewall issue. What error messages do you get? — Tom, Jul 30, 2016 at 12:32
Windows operating systems don't and can't use multiple default gateways. Your trying to solve this problem the wrong way. By the sounds of it, this is a hairpin NAT issues with your firewall and that's where you should be looking to solve the problem. — joeqwerty, Jul 30, 2016 at 15:36

Sysadmin Guy · Accepted Answer · 2016-07-30 12:51:28Z

1

On your client machine, try adding the following route. I can't say that it will work but it would be what I would do.

At the command prompt with administrative privileges type in:

Route add 50.65.1.52 mask 255.255.255.255 192.168.1.100

Any traffic destined for 50.65.1.52 will be sent to your server. Your server should then know that it's itself. Let us know how you go.

-Sysadmin Guy

answered Jul 30, 2016 at 12:51

Sysadmin Guy

262 bronze badges

didn't work ,any ideas
– Farahatology
Jul 30, 2016 at 13:12
1

A diagram would be good. You mentioned that the server has two IP addresses and connected to the same LAN. Is the Gateway 50.65.1.1 the same physical device as 192.168.1.1 but a different interface ?
– Sysadmin Guy
Jul 30, 2016 at 13:19
50.65.1.1 is different physical device
– Farahatology
Jul 30, 2016 at 13:24
1

Can I ask what you are trying to do? Is this a test environment and you are trying to simulate an external IP access to the server ? Because in a real environment the client would be connecting directly to 192.168.1.100 and not the 50.65.1.52 address because it is on the same LAN.
– Sysadmin Guy
Jul 30, 2016 at 13:32
1

@Farahatology I am trying to help you with your problem. Pretend just for a moment that none of us can actually see the computer you're having trouble with. Stupid idea I know, but just pretend for a second. Now if that were actually true then we wouldn't know that you were not getting an error message until you just mentioned that a moment ago. That will be useful information for people trying to fix your issue for you. Perhaps a little less trying to be a smartass on your part and a little more trying to think "what will help these people help me" might do well in the future?
– Rob Moir
Jul 30, 2016 at 15:32

| Show 8 more comments

1 Answer 1