VirtualBox Networking does not pass DCE RPC BIND packets with OS X host

Host packet capture screenshot

guest packet capture screenshot

Note - all other windows networking (file shares, browsing, HTTP, kerberos) seem to be working fine.

VBox log included

Could you please add log for the same issue with NAT networking?

Log file when NAT networking used. (Other log is with bridged)

A bit more information. I've been through the normal outlook issue steps of deleting and recreating the mail profiles. At one point I suspect the guest OS, but even with clean installs of both Vista and Win7 plus O2K7 the issue is repeatable and happens every time.

Replying to fm2503:

A bit more information. I've been through the normal outlook issue steps of deleting and recreating the mail profiles. At one point I suspect the guest OS, but even with clean installs of both Vista and Win7 plus O2K7 the issue is repeatable and happens every time.

Would you mind to send me (vasily[dot]levchenko[at]Sun[dot]COM) pcap file of guest to NAT interaction (please see pcap for details)

Replying to Hachiman:

Would you mind to send me (vasily[dot]levchenko[at]Sun[dot]COM) pcap file of guest to NAT interaction (please see pcap for details)

Annonmised pcap mailed as requested.

I'm seeing something similar but I have a Ubuntu 9.04 host and a Windows XP guest. Also, I've had success connecting to Exchange but only intermittently and after a wait of 10 minutes or so. I can provide pcap data if desired.

Replying to robmoore:

I'm seeing something similar but I have a Ubuntu 9.04 host and a Windows XP guest. Also, I've had success connecting to Exchange but only intermittently and after a wait of 10 minutes or so. I can provide pcap data if desired.

Thanks for information, please do it. will compare and will try found some solution

BTW: Is it new issue appeared in 2.2.4 or it presents in 2.0, 2.1 as well?

Replying to Hachiman:

BTW: Is it new issue appeared in 2.2.4 or it presents in 2.0, 2.1 as well?

It certainly wasn't present in 1.6, nor I think 2.0. Unfortunatley I switched from an Ubuntu host to a OS X around the 2.1 time frame, so can't be certain when exactly it broke.

IIRC the problem manifested itself around the 2.2 time frame. I think 2.1 was OK, but am not in a position to test at the moment. Could probably do a binary chop to determine exact version this regression was introduced, but that will have to wait for the weekend.

Matt

I've sent the pcap file to your email. A small note, in the pcap instructions you link to the command line options are a bit out of date -- it appears the option is modifyvm rather than just modify.

Replying to robmoore:

I've sent the pcap file to your email. A small note, in the pcap instructions you link to the command line options are a bit out of date -- it appears the option is modifyvm rather than just modify.

Thank you for files, and noticing mistype on wiki (updated).

I've done some version testing and on OS X the problem is present in 1.6.4 2.0.8 2.1.4 and 2.2.4. Clearly this is an OS X specific thing, as I didn't see this issue on Kubuntu at all.

Replying to fm2503:

I've done some version testing and on OS X the problem is present in 1.6.4 2.0.8 2.1.4 and 2.2.4. Clearly this is an OS X specific thing, as I didn't see this issue on Kubuntu at all.

Thank you for update and investigation.

This seems to be a generic problem with the RPC traffic and VB on OS X. Using a host only network I was unable to domain join a W2K03SP2 box to a 2K08 domain until I followed the steps listed in http://support.microsoft.com/kb/899148

Notably I set Server2003NegotiateDisable to 1, and then the 2K03SP2 box was able to join the domain. Without this flag set, the box could not join the domain and failed with RPC errors.

Sadly Server2003NegotiateDisable doesn't solve the problem for Vista and outlook to talk MAPI to exchange

Having said that, I've flicked the Vista VM to bridged networking, and my connectivity to Exchange is restored. I'll double check the NAT configuration. Server2003NegotiateDisable certainly works around the problem using bridged networking.

OK, the situation is confirmed. With host only or bridged networking Server2003NegotiateDisable set allows these RPC packets to pass, and connectivity is achieved. With NAT networking the problem remains.

Hope this helps.

Issue is still present with NAT networking under version 3.0.2. Bridged continues to work fine.

I've upgraded to 3.0.4 and on first glance the problem remained. However I have been able to establish connectivity with Exchange by authenticating in the format fqdn.domain.name.com\user.name and configuring the security settings on the exchange account for Logon network security to "Negotiate Authenticaiton".

So whilst there are various scenarios that do not work, these could equally be down to outlook/exchange strangeness, although server2003NegotiateDisable does seem to be still required.

As a valid work around now exists I'm happy for this to be closed.

Replying to fm2503:

Thank you for publishing workaround.

Replying to fm2503: Could please collect the pcap files for 2.1 and 3.0.4 releases? Still not sure what is real problem for dropping this packets.