Is NTLM2 Broken in SP2?

[Chris Cummings]

I just installed SP2, and I can no longer see any devices
on my local network that require NTLM2 to connect.

I have the firewall completely shut off and my
lmcompatibilitylevel in the registry is set to 3.

I can connect to any Windows PC, but our CE.net 4.2
devices are no longer available. With
lmcompatibilitylevel set to 1 or 2, I get to the initial
connect, but the CE device rejects the login, as expected.

When lmcompatibilitylevel is set to 3, Windows comes back
with "Network Path not Found". I can ping the devices
just fine, but neither IP format or Hostname format will
allow Windows to see the devices.

Does anyone have any insights?

 

[Quaoar]

I just installed SP2, and I can no longer see any devices
on my local network that require NTLM2 to connect.

I have the firewall completely shut off and my
lmcompatibilitylevel in the registry is set to 3.

I can connect to any Windows PC, but our CE.net 4.2
devices are no longer available. With
lmcompatibilitylevel set to 1 or 2, I get to the initial
connect, but the CE device rejects the login, as expected.

When lmcompatibilitylevel is set to 3, Windows comes back
with "Network Path not Found". I can ping the devices
just fine, but neither IP format or Hostname format will
allow Windows to see the devices.

Does anyone have any insights?

Check TCP/IP properties/TCP/IP filtering settings; these might be set to
Permit Only. Have you set an exclusion to NTLM2 in the Windows
Firewall? It might be set in the TCP/IP protocol filter also.

Q

 

[Guest]

Thanks, Quaoar.

In fact, none of those items were evident. I later found that a .Net app we
created in-house lost the ability to see any removable media connected to USB
2.0 readers, so I decided to roll back to SP1.

To Microsoft's credit, the SP2 uninstall went off without a hitch! After I
was back to SP1, both problems were solved. I guess SP2 is not a good fit for
my particular operating environment