I don’t think this problem/solution is much different in older versions.
Problem: when you send a link from Communicator client to another, the link isn’t clickable, has a _ (underbar) in front of it, or both. Results may be different on different computers. It’ll look like this
_http://www.google.com
Solution: Two things are happening here that are not related. The first is the OCS Server (and Edge Server) have the URL Filter enabled, which are adding the _ underbar to all links. Also called “Intelligent IM Filter”. You need to tone that filter down or disable all together to your liking. If users are coming in through an Edge Server, they will follow the Filter settings of the Edge Server they are using, which seams to supersede the Front End Server (my guess is the most restrictive wins). So be sure to set it on both servers separately. Results were instant in new IM’s.
The other issue is the lack of a clickable hyperlink. If you disable the URL Filters above, the underbar goes away but links are still not blue and underlined. To fix this you need to apply a GPO or set a local registry setting to allow Communicator to make hyperlinks clickable:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator\
new DWORD EnableURL=1
After that exit and restart Communicator.
In both of these cases they are secure by default, which is great; but even years after this features release over several versions their use and configuration are still a mystery to most starting out.
Just one year from a stock market crash and real estate burst that “we thought” forced us to re-learn the lesson our grandparents knew about leverage: Use it to buy assets, not liabilities. Don’t use it to buy merchandise that doesn’t make you money. I’ve closely followed Macy’s (M) for years, but I guess I missed the part about just how much of their quarterly sales are done with store credit cards! WSJ claims it’s over 50% last quarter (3Q 2009). I’d love to see a graph on this stat (% of sales on store credit) over the last 10 years. Do we really have a 6-month memory about how we spent ourselves into so much debt?
I could go on all night about how maybe we never learned the lesson; about how this could be caused by an over-reactive government that won’t let people and business fail en masse, in order to teach our society a lesson we need to re-learn,.. but I won’t for now.
It’s interesting that the article I read this in wasn’t really about the still shockingly high amount of Macy’s shoppers that are buying on store credit (all this during non-holiday months). As an American, I say YES to this federal proposal that you must prove you can pay before you borrow for clothing, furniture, and electronics.
And on that point, why can I get a retail store card without proof of income but there is no store credit at the grocery store?
What if, regardless of circumstances, you could quit your job and retire within 5 years? What if you could only work 4-8 hours a week and make in a week what you used to make in a year, and do it from anywhere? What if you could leave and take a month to explore something you’ve always wanted to (travel, learn a sport, etc.) and come back with more money then you left?
Imagine spending your time doing all the things “you always wanted to do” but didn’t have the time, money, or energy to do? What if the belief that a job is the safe way and retirement at 65+ is the only way… is actually a lie?
In 2003 I started asking myself these questions, and have found the answers.
I’ve learned in the last 5 years that this is indeed possible and first has to start with believing it can happen. I mostly did this with books, some classes, and support from my Wife. Without any skills in either real estate or the stock market we are quickly coming to a turning point in our mindset and abilities that will allow us to do just that. I imagine this blog will change along with me, since I am quitting my job and phasing out my technology career. I’ve had people tell me this can’t be done, at the same time I’m doing it. I’ve had many moments I thought it was moving too slow and would never happen, or that I didn’t have the magic skills to make it work. But for the moments that it seems to take forever, I’ve had moments (like now) that a huge leap forward has taken place and now realize within a year we’ll both be living the way we started to dream 6 years ago with one simple book: Rich Dad, Poor Dad. It may not be the perfect book, but it lit a spark of hope, and after reading that book we had only one rule we weren’t willing to break: once we started to act on these dreams, we would never give up… never.
Published on
Oct 1, 2009 in
Microsoft, Networking and Security, Solution Writeups and Tech.
Tags: activesync, email, exchange, firewall, isa, Microsoft, timeout, windows mobile.
They were getting random prompts for passwords in ActiveSync on Windows Mobile 6.0 and 6.1. They had Exchange 2007, and ISA Server 2006, but this problem showed up months after Exchange was migrated to 2007. It seemed random. The error on ActiveSync was the generic:
please log in access was denied 0×85010002
In the ISA Monitoring you would see a denied connection on your ActiveSync rule with this status:
12239 The server requires authorization to fulfill the request. Access to the Web server is denied. Contact the server administrator.
I tested with Windows Mobile Emulator from outside the firewall and was able to reproduce the error within hours (just letting it sit there).
I first thought this was the HTTP session timeout that changed with a Exchange 2003 service pack when Direct Push came out back in 2005. I remembered that setting and looked under the ISA Web Listener for ActiveSync on the Connections tab>Advanced>“connection timeout”. The wizard had correctly set it to 1800 seconds (30 minutes). No dice.
I poked around the web listener settings some more and noticed the timeout settings for forms authentication were set (this same web listener was used for OWA). ISA is supposed to be smart enough to not apply any of the forms auth settings to clients that don’t support it (falling back to basic auth as with ActiveSync).
Tom and the forums at isaserver.org confirmed my suspicion. The forms auth timeout was indeed affecting ActiveSync. To find it, look for the web listener of your ActiveSync rule, go to properties>Forms tab>Advanced> and make sure “apply session timeout to non-browser clients” is unchecked.
On trying to remove a old server from the directory (2003 server in a 2003 forest) I received this error
Failed to configure the service NETLOGON as requested “the wait operation timed out.”
The root problem was that this domain controller had a DNS entry to another domain controller that no longer existed. It was trying to contact it but couldn’t. Removing that entry and running dcpromo.exe again solved it.
