![]() ![]() There is no firewall rule in SEP that would be blocking this level of SSH - in fact, disabling all firewall rules does not solve the problem, nor does creating a "catch all" rule that allows all traffic as the first rule. I can SSH from the host to another PC and then from there to the guest just fine, and outbound connections from the guest work just fine. ![]() I'm unable to SSH from the host to the guest on any interface, but H-T-T-P traffic (why do these forums think this abbreviation by itself is a link?) on port 8888 from the host to the guest works fine. Network Configuration: Guest has 3 interfaces: #1 is bridged to the host's Ethernet interface (192-x), #2 is a host-only network (172-x) and #3 is NAT. Guest Antivirus/Firewall/Etc: None, and no iptables rules either. Guest: Debian Linux 6-0-6 amd64 (squeeze/stable) Host Antivirus/Firewall/Etc: Symantec Endpoint Protection 12-1 (SEP) Virtualbox 4-2-14 and 4-2-16 (tested with both versions) This particular host was actually the first test subject, as it's my development machine and I'm the system admin who pushed for the deployment.Įverything was working fine for me last week, but as of today I'm experiencing this absolutely bizarre issue: We recently swapped to using Symantec Endpoint Protection after a recent evaluation period, during which there were no problems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |