Yahoo Messenger 11 connectivity issues behind ISA 2006 firewall


With update Yahoo messenger has additional issues with negotiating a handshake with ISA server. Please read this KB article for additional IE setting changes in order to let yahoo through ISA server.


Do you “still” IM using yahoo messenger? The latest version has facebook integration and more to offer which allows you to communicate (chat) with your friends online over social networks.

However, Yahoo messenger fails to establish a connection to it’s servers if behind ISA firewall. Here we are offering you some guidelines dealing with such scenarios.

Most acceptible reasoning for connectivity issues behind ISA firewall should be, YM failing to forward the NTLM authentication credentials to ISA fiewall while trying to establish a connection. Once failed to establish a connection, user will be provided a chance to troubleshoot the issue, which does the trick!

All you need to do is to click the troubleshoot button and wait for the process to complete. If curious, click on the details button to see multiple connectivity checks performed by YM. As soon as the troubleshoot activity completed, rush to login again with your username and password

You should able to logon to yahoo services without troubles this time. Please note, you should try to logon immediately once after the troubleshooting process is completed. This means you cannot wait minutes after the troubleshoot activity is completed. Else you will once again have to go through the entire process of troubleshooting until you manage to logon.

Enjoy all new features offered by Yahoo Messenger from “work” now

Windows 7, ISA 2006, Nokia Ovi suit, Nokia Map Updater, Nokia Map Loader etc

Was it easy ever to get your favorite(?) nokia applications connect to respective servers behind ISA? We think not at all! We were behind ISA from last many years and until recent days we were almost unable to get Nokia software through ISA.

While Nokia Ovi suit still being the shittiest application behind ISA, you can easily get other products contact the servers  by following these:

Enable WPAD (please refer the posts referring to “Windows 7, Additional log on information may be required”)

Install ISA 2004/2006 Firewall client.

Go to Internet Explorer options, LAN settings and make the changes as you could see them with the attached image. Please make sure other than “Automatically detect settings” NONE of the other checkboxes should be checked!

Go to ISA Firewall client->Web browser and uncheck “Enable Web browser automatic configuration” so that ISA firewall client will not automatically configure the IE settings (polls once in few hours). Please refer the attached image.

Try to start Nokia map update or Map loader application and ISA would happily allow the connections. Please make sure you have download permissions with ISA Server, else you will not able to.

We hope this helps ‘few’ frustrated souls out there…

Windows7bugs team.

Dealing with “Windows 7 Additional log on information may be required”

Scenario: Windows 2008 R1 AD Domain, Windows 2003 ADC, ISA 2006 proxy, Windows XP, Windows 7 Clients.

I had couple of other posts related to the same topic in the past. Last week, March 2009, we almost ran into a solution which we expected as a permanent resolution for the annoying “Additional log on information may be required, click here to open the browser” message. However, immediately after couple of days without issues, this message started popping up, especially with 64bit Windows 7 Professional clients (I have one)

This time rather than spending our whole attention towards the client, we tried to do troubleshooting for the live connection and the detailing pans suggested we should sign up with the ISP for this network. Because we are behind ISA server proxy, we assumed the connection assess the same as a re-direction.

We had ISA from last five years and right now running ISA 2006. However we never enabled the auto discovery method for ISA and finally after spending few minutes and with the help of a document from we managed to get the wpad work fine for us.

However, other than my particular box, rest three test boxes running both 64bit and 32 bit clients stopped receiving “Additional log on information may be required” or “ no internet access” status messages. In order to re-produce the scenarios which caused my system to have persistent error messages, I opted for a fresh installation of the OS and started creating manual restore points (how to?)

Post-installation activities

Re-joined my box with previous hostname

Installed ISA firewall client<>’No more You may require additional log on information or the yellow triangle with “ no internet access”

Installed Avast free antivirus<> No problems yet (Many posts refer about antivirus programs causing the status/error messages)

Installed ZoneAlarm free firewall<>Better manageable than built-in firewall, still no error messages.

As writing this post on 20th March 2010, I am yet to receive any error messages about the connectivity. Following are the software I am yet to install which MAY cause problems with the connectivity

  • Java VirtualBOX
  • VMWare free player

Right now I am too busy to install the virtual machines, however too eager to assess what would happen once after I will finally install them. Please come back and read to know whether one of the installations specifically causes the most annoying error messages you would come across with your Windows 7 network connections!

Even though while connected to the LAN physically I don’t get warning/error messages, while establishing a PPTP connection from home to work, I do receive “Additional log on information may be required” followed by “click here to open the browser” messages.

Update 20.March.2010 afternoon session

Installed VMWare free player (latest edition). Everything works fine. “Additional log on information may be required” message still appears along with the hated yellow triangle only when the cable is physically detached and attached back. Nothing (restarting “Network Location Awareness”) clears the status message and a forced restart required to clear the message.

Uninstalled VMWare player, re-produced the situation to confirm it was not the VMWare networking components causing the error

Found a latest driver for the NIC from BroadCom site itself as HP site provided NIC drivers are rejected by Microsoft stating the drivers supplied by Microsoft being the latest dated to 26th April 2009. The drivers from BroadCom is dated 08th of June 2009 and Windows agreed to upgrade the drivers.

By virtue or out of curiosity disabled the option “Allow the computer to turn off this device to save power” under Power Management node.

Re-installed VMWare free player, restarted the machine. Everything seems working fine.

Unplugged the cable, plugged back and bingo, within few seconds the network connection established without throwing any error messages!

Does it mean we are finally dealt with more than a month-long painful exercises to find a solution for this annoyance? Wait, let us wait another couple of days. Last time when we “found” such a solution, the error messages started appearing after 2-3 days…

Minor update (21st March 2010)

Umm I didn’t have to wait for 2-3 days! Now, the latest problem which triggers a hated yellow triangle tightly related with the power saving “enhancement”. After the fresh installation the power options were not altered to suit my current working atmosphere and the machine was having default settings, in which, even while the power is plugged in the system was asked to go into sleep mode after 5-10 minutes of idle time.

Once awaken, the system tries “hard” to re-initiate the network, eventually fails to authenticate(?) something, something, brings back the favorite(?) yellow triangle and the love message “Additional log on information may be required”

The only solution I had was to set up never to allow the PC to enter into the sleep mode while power is plugged in! Seems it is working perfectly (I spent around 12 minutes for lunch and when returned the network connection was still intact without the yellow triangle or error message(s))