scottgus1 wrote:Shut down your guest.
Connect your PC to Corp. Run "ipconfig /all" on the host. Start the guest. Let it stabilize then run "ifconfig" on the guest. Please post the outputs of these two commands, labeling each.
Shut down your guest again.
Connect your PC to RD. Run "ipconfig /all" on the host. Start the guest. Let it stabilize then run "ifconfig" on the guest. Please post the outputs of these two commands, labeling each.
fth0 wrote:@Stradman:
Can you also provide PCAP files from the guest and from the host, capturing all network interfaces on the host simultaneously?
socratis wrote:If ZIPPING them doesn't get you down below the 128 KB limit, then an external site is your only option. For example, in the following site your file is available for 30 days, limit 5 GB, no registration required: https://uploadfiles.io/
You do see that many attempts to get useful diagnostic data have been made.fth0 wrote:When issuing the "ipconfig /all" command, also issue a "route print" command to show the current routing table on the host.
No way for us to verify that, and just because it is written on the internet does not necessarily make it true.Stradman wrote:There should not be any IP overlaps in the current setup,
I agree exactly.fth0 wrote:If you like to have a 2nd opinion, you should deliver the information that you have been interpreting only yourself.
Private IP addresses are not hackable. If you are worried, ask your IT folks. But to get further help you will need to give us something solid to go on. And you have not done that yet.Stradman wrote:I am not quite sure about how much information I can share on specific details here from the corporation.
FWIW if Host-Only works on one network and does not work on the other network, then it's the other network's fault, not Virtualbox's.