I had an employee with the following problem. They were unable to VPN and were receiving the errors in the Title. They were also unable to connect to some wireless AP at customer's site. Here is what I did. One i stopped Eset from Scanning the C:\windows\system32 directory. This allowed the Windows Remote Management Access service to start. I then looked at HKEY_LOCAL_MACHINE\System\Services\RASMAN\PPP\EAP and noticed that Symantec had entry in 13,25, but not 26. I read somewhere to delete all entries except these 3 because they are windows default entries. Since Symnatec (Symantec was installed on this computer, but removed) had entries in I decided to delete 13 and 25. I deleted them and then rebooted hoping they would self populate, but they did not.
I then exported these registry entries from another Vista computer and then imported them. The problem was now fixed.
Thursday, June 3, 2010
Tuesday, February 16, 2010
I was struggling trying to get Outlook 2007 to connect to my Exchange 2003 server...
Here is what I did.
I was trying to add a new user, but I continued to get a message that Exchange was unavailable or offline. Yet, no one else was complaining and I could connect using OWA. So I figured it was a problem with the client computer.
Where it prompts to put in the Exchange Server name I put in the Domain Controller name instead. This quickly resolved to the name of the exchange server and then I was connected. I was able to finish setting up the new user. So I could resolve the name by going to the DC instead of the exchange server. Time to look at the services on the exchange server. I noticed that the Microsoft Exchange System Attendant had stop running. This is needed to resolve Active Directory information. So if you run into this problem make sure this services is running.
I was trying to add a new user, but I continued to get a message that Exchange was unavailable or offline. Yet, no one else was complaining and I could connect using OWA. So I figured it was a problem with the client computer.
Where it prompts to put in the Exchange Server name I put in the Domain Controller name instead. This quickly resolved to the name of the exchange server and then I was connected. I was able to finish setting up the new user. So I could resolve the name by going to the DC instead of the exchange server. Time to look at the services on the exchange server. I noticed that the Microsoft Exchange System Attendant had stop running. This is needed to resolve Active Directory information. So if you run into this problem make sure this services is running.
Subscribe to:
Posts (Atom)