The VPN software we use is sanely configured and will not allow other network connections to function while in use.
Once I detached from the VPN everything worked fine. Michael Rasmussen wrote: > Indeed it is the Windows host based packet filtering. > Which is managed by a 3rd Party app. think of the bing names and it will > be semi-obvious. > > Sometimes working for a bank is a bitch. > My boss didn't think we had host based firewalling. > Note: We both work in the corporate security department. > > > Michael Rasmussen wrote: >> >> chris (fool) mccraw wrote: >>> On Tue, Aug 4, 2015 at 4:05 PM, Ken Stephens <k...@cad2cam.com> wrote: >>> >>>> Michael Rasmussen wrote: >>>> >>>> > Both hosts can ping their own interface, yet neither can ping the >>>> other's >>>> > interface. >>>> >>> >>> No surprise there - you can ping any address you configure as local by >>> default :) >> >> And the sanity of "did I set up the interface?" was verified. >> >>> >>>> Check your firewall settings on both the virtual and real machines. >>>> You >>>> are probably blocking port 22 on one of them. >> >> No FW settings on the VM. This one is a clone of a production system >> that >> we ssh to as part of regular work. >> >>>> >>> >>> ...but blocking ICMP by default as he mentioned ping doesn't work? >>> That >>> seems odd and unexpected to me. >>> >>> Michael, can you tell us what the setup is on each machine (eg VM = >>> 10.1.1.1/255.0.0.0 w/route to that network via the interface, host= >>> 10.1.1.2/255.0.0.0 route - note that I am more interested in what the >>> Host >>> machine's network settings are on the private network that gets setup >>> for >>> the VM than what its "external" IP/routes are)? Also, what host passes >>> out >>> the DHCP address to the VM - that should be in the logs somewhere? (My >>> centos 7 VM puts it in /var/log/messages as 'server identifier x.y.z.q' >>> in >>> the middle of a bunch of NetworkManager output.) >> >> The DHCP server seems to be the VMWare player. >> >> Windows (host) side: >> >> Ethernet adapter VMware Network Adapter VMnet1: >> >> Connection-specific DNS Suffix . : >> Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter >> for >> VMnet1 >> Physical Address. . . . . . . . . : 00-50-56-C0-00-01 >> DHCP Enabled. . . . . . . . . . . : No >> Autoconfiguration Enabled . . . . : Yes >> IPv4 Address. . . . . . . . . . . : 192.168.118.1(Preferred) >> Subnet Mask . . . . . . . . . . . : 255.255.255.0 >> Default Gateway . . . . . . . . . : >> NetBIOS over Tcpip. . . . . . . . : Enabled >> >> Linux (VM instance) side: (this is typed as I can't cut and paste from >> there. >> >> >> ip addr show eth1 >> 2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast >> state >> P qlen 1000 >> link/ehter 00:0c:29:e3:63:d7 brd ff:ff:ff:ff:ff:ff >> inet 192.168.118.128/24 brd 192.168.118.255 scope global eth1 >> inet6 <snipped> >> >> ip route >> 192.168.118.0/24 dev eth1 proto kernel scope link src 192.168.118.128 >> >> That all looks sane to me. >> >> Curiously tcpdump shows: >> 11:32:56.130921 arp who-has 192.168.118.1 tell 192.168.118.128 >> 11:32:56.131059 arp reply 192.168.118.1 is-at 00:50:56:c0:00:01 >> >> So there's some communication on the line. The mac addr matches the >> Window's mac. >> >> Now researching Windows FW and what happens to VM connections when I've >> a >> VPN connection going. >> >> >>> In my setup, that IP is given out by my host machine - which is not >>> running >>> DHCPd, so VirtualBox is using its builtin DHCP server, and just passes >>> on >>> many the same settings (eg nameservers) as the host OS is already using >>> - >>> but this is NAT, not host-based networking, mode. I used to use the >>> Host-based networking, but lately I've fallen back to NAT which I >>> realize >>> won't work for you, but hopefully the above can give us some ideas as >>> to >>> what's wrong. In my old setup I'm pretty sure I had Host-based >>> networking >>> and still used the auto-dhcp and the default route on that VM got an >>> automatic gateway set that was the IP of the host machine (from the >>> point >>> of view of the VM). >>> _______________________________________________ >>> PLUG mailing list >>> PLUG@lists.pdxlinux.org >>> http://lists.pdxlinux.org/mailman/listinfo/plug >>> >>> >> >> > > -- Michael Rasmussen Be Appropriate && Follow Your Curiosity _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
