New
#11
Have you tried to disable all the Network Connections (execpt for the interface you are going use) and then try to join the domain?
Have you tried to disable all the Network Connections (execpt for the interface you are going use) and then try to join the domain?
That is just odd because originally I had tried all the other connection XP Mode offered, and knew not to use NAT. I have a M4400 as well. I'll have ot give it another try and I'll let you know if that works....
I was curious if when you said #3 fixed it the wireless is joined to the domain and working properly......???
This is what I did to make this work using NAT (bridged is way easier but if the IP addresses are limited NAT may be necessary) on a Vitrtual XP machine.
Set VM settings to use NAT. After logging in to the XP VM change the TCP/IP settings within the virtual machine to use the VMs gateway (192.168.131.254) as the preferred DNS server and the domain's DNS server as the alternate.
Then:
Start Registry Editor.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\ Kerberos\Parameters
*Note: If the Parameters key does not exist, create it now.
On the Edit menu, point to New, and then click DWORD Value.
Type MaxPacketSize, and then press ENTER.
Double-click MaxPacketSize, type 1 in the Value data box, click to select the Decimal option, and then click OK.
Quit Registry Editor.
Add the VM to the domain (you may need to use the FQDN)
Restart the virtual machine.
Login to the domain.
It still takes a bit of time to login once completed but comparable to starting a physical PC.
Thanks for the help, changing the NIC settings in the vm is what did the trick for me!