Sometimes when Outlook changes network contexts (i.e. from wired to wireless), it triggers an annoying authentication popup. There’s a way around:
- Open Outlook.
- Go to “Tools” > “Account Settings”.
- Double click on your account.
- At the bottom right, click on “More Settings…”.
- Click on the “Connection” tab.
- Under “Outlook Anywhere”, click on “Exchange Proxy Settings”.
- Uncheck the “On slow networks, connect using HTTP first, then connect using TCP/IP”.
Since I try to put everything here that gives me headache, makes me pull my hair or worse, makes me want to run to the closest hardware store to buy the biggest hammer I can find, here is my latest discovery…
A Windows XP user requests a new computer running Windows 7.
Backup the old computer to a network share.
Take a new computer out of the box.
Put a standard image on it.
Have the user logging in.
Let the user go.
A few days after the system deployment, the user starts complaining about connectivity issues (i.e. getting an IP but no connectivity) and general slowness of the computer.
- Hardware swap -> no improvement.
- OS complete reinstallation -> good for a few hours then bad again.
- Switch configuration, patch panel, network cable and outlet check -> no improvement.
- The user ended up giving up and asking for his old computer.
Since I got the new one back, I had some more time to investigate…
Here’s what I found after running ipconfig /all:
Default Gateway . . . . . . . . . : 0.0.0.0
Very interesting, that explains why he has an IP but no connectivity. A quick Google search confirmed the issue:It’s related to Adobe CS3 software that installs Bonjour which basically breaks WinSock on Windows and the solution is to remove Bonjour using the following steps:
- Go to http://cexx.org/lspfix.htm and download lspfix.zip.
- Unzip to a desktop folder.
- Open task manager and terminate mDNSResponder.exe.
- Open a command prompt and navigate to c:program filesbonjour
- Run “mdnsresponder -remove”. This will uninstall the exe and remove the service from the reg.
- Rename mdnsnsp.dll to anything else.
- Run lspfix and use it to fix the broken winsock.dll.
- Delete c:program filesbonjour folder.
- Open a DOS window and run “netsh winsock reset”.
Courtesy of FritoBandito from the Adobe Forums.