Hyper-V 2012 remote management works on same subnet but not on another
hello all!
realize there ton of other discussions on similar issues i've tried various suggestions no success , think problem unique (but applicable many other people experiencing similar errors).
environment:
machine a: client remote management - running server 2012
machine b: hyper-v server 2012
- no domain - workgroup mode
- firewall disabled on both troubleshooting purposes
- setup same administrator user/password on both machines identical admin user test with
- allowed anonymous remote access in dcomcnfg
- hosts files edited add server/client host names
- set vds service start / automatic start
problem:
when installing machine b (hyper-v server) client machine directly plugged same lan , static ip on same subnet, remote management works fine. able use hyper-v manager server manager, computer manager, powershell remoting successfully.
when move machine (client) remote isp , connected our colo facility via vpn (has ip on subnet), , connect server in hyper-v manager, error "rpc server unavailable. unable establish communication between 'server' , 'client'." note can edit hyper-v settings, edit , inspect disks, etc. within hyper-v manager , other types of management work (server manager, computer manager, mmc, powershell remoting) exception of connecting disk management service in computer manager throws "rpc server unavailable" error.
vpn hardware-based ipsec tunnel trendnet router isp-side (machine a) cisco pix firewall colo-side (machine b). there no pix rules restricting data flow regarding vpn tunnel.
can ping in both directions successfully, , tracert completes single hop both ways.
noticed firewall rule windows remote management (http-in) on public profile restricted local subnet only, added vpn subnet well. should not affect outcome firewalls disabled.
so, seems directly related being on different subnet works when on same subnet. insight appreciated. , have great weekend!
cheers, rich
realize there ton of other discussions on similar issues i've tried various suggestions no success , think problem unique (but applicable many other people experiencing similar errors).
environment:
machine a: client remote management - running server 2012
machine b: hyper-v server 2012
- no domain - workgroup mode
- firewall disabled on both troubleshooting purposes
- setup same administrator user/password on both machines identical admin user test with
- allowed anonymous remote access in dcomcnfg
- hosts files edited add server/client host names
- set vds service start / automatic start
problem:
when installing machine b (hyper-v server) client machine directly plugged same lan , static ip on same subnet, remote management works fine. able use hyper-v manager server manager, computer manager, powershell remoting successfully.
when move machine (client) remote isp , connected our colo facility via vpn (has ip on subnet), , connect server in hyper-v manager, error "rpc server unavailable. unable establish communication between 'server' , 'client'." note can edit hyper-v settings, edit , inspect disks, etc. within hyper-v manager , other types of management work (server manager, computer manager, mmc, powershell remoting) exception of connecting disk management service in computer manager throws "rpc server unavailable" error.
vpn hardware-based ipsec tunnel trendnet router isp-side (machine a) cisco pix firewall colo-side (machine b). there no pix rules restricting data flow regarding vpn tunnel.
can ping in both directions successfully, , tracert completes single hop both ways.
noticed firewall rule windows remote management (http-in) on public profile restricted local subnet only, added vpn subnet well. should not affect outcome firewalls disabled.
so, seems directly related being on different subnet works when on same subnet. insight appreciated. , have great weekend!
cheers, rich
rktect
i tend @ security imposed vpn connection. can test if subnet issue using initial configuration both nodes on same subnet in lab , placing 1 on different subnet. if can't manage between 2 subnets when machines on physical wire, can conclude subnet issue. if can manage, start looking @ vpn.
.:|:.:|:. tim
Windows Server > Hyper-V
Comments
Post a Comment