vpn traffic not forwarded to physical network from multibox


hopefully there can answer this.

i have box running hyper-v hosting 2 more servers (a third planned)

the problem is seems impossible connect internal network thru vpn.

the setup is;

box running hyper-v 2012  ip=192.168.9.8 2 physical adapters 1 beeing used virtual adapter

     1 sbs 2008 connected virtual adapter ip=291.168.9.1

     1 server 2012 std edition connected virtual+"physical" adapter acting router , remote access ip=192.168.9.254

the 2012 std ed has nat & vpn installed.

the problem following; if remote router connects vpn cannot access local network @ all, can access 192.168.9.1, 192.168.9.8 & 192.168.9.254 nothing beyond that. on other hand if open command-box on 2012 std can ping entire network not other side of vpn (windows server 2008 std). nat'ed traffic entire network no problem @ traffic coming thru vpn

also note "physical" adapter virtual connected routing server (and ofcourse host itself).

i have checked (and rechecked...) following.

all adapters have been set forward traffic netsh seems not problem vpn-clients can access .1,.8 & .254 meaning traffic get's onto virtual network not off onto physical network , physical network connected can ping routing server (.254) 

hmm... apparently did not read question or i'm not making clear enough...

the problem traffic vpn , connects inside nat.

it apparent traffic vpn not forwarded onto physical network stays on virtual network as all traffic nat works should. i've made temporary solution routing traffic local network onto sbs server , there onto physical network, seems problem server-2012, still needs fixed cannot have 3 servers (thou virtual ones) involved in moving traffic 1 nic next...



Windows Server  >  Windows Server 2012 General



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group