At some point in the recent past I noticed that I could not browse the local network.
I had recently upgraded to SBS 2011 after the upgrade I was able to browse the network but not now.
I could still access all of the resources on the network, so it was not a permission problem.
Network Discovery was turned on in the Advanced Sharing Settings of all of the Windows 7 computers.
After googling and bingleing many people wrote that they turned on the Computer Browser service.
However in Windows 7 and Server 2008, the browser service is deprecated and no longer used.
Dom's Techie Blog pointed to the services that need to be running for Network Discovery to work.
All of mine were set to the correct settings and running except that Function Discovery Resource Publication was set to manual and not running. Everything I could find stated that it should be set to manual.
On a hunch I started the Function Discovery Resource Publication service on a few computers and I was able to browse to them on the network almost instantly. I am not sure why I am not able to browse with the services set to default but I created a new Global Policy to set the service to Automatic and applied it to all of the computers in the domain.
I can now browse all of the computers but I still do not have a valid cause for what happened. I am going to try to research this one some more and see what happens.
Tuesday, July 26, 2011
Monday, July 25, 2011
Exchange 2010 Activesync Issue
I upgraded my Exchange server from Exchange 2007 to Exchange 2010 as part of the migration to SBS 2011. After the upgrade I was making good progress ironing out issues until I tried to sync my android phone.
The native android email in Android 2.2 was failing with an unspecified error. I then tried Touchdown by Nitrodesk. It was also failing but they have nice logging built into their software and I was able to see the following:
Checking Certificate...
Checking ActiveSync with SSL...
Server is Microsoft-IIS/7.5
ActiveSync was found
ActiveSync Version :Versions:Microsoft-IIS/7.5,2.0,2.1,2.5,12.0,12.1,14.0,14.1
Trying activesync protocol -116...
ActiveSync provisioning returns HTTP:200
Error provisioning ActiveSync: Policy status is 0
Trying activesync protocol 2.5...
ActiveSync provisioning returns HTTP:200
ActiveSync provisioning success
The following policies have been requested :
The error refreshing folders was the key and NitroDesk support pointed me to the Nick MacKechnie blog. The main idea is that there is an issue with upgrading to Exchange 2010 and some of the permissions are not set correctly.
Another good Exchange troubleshooting tool I found is the Microsoft Exchange Remote Connectivity Analyzer . This tool pointed right to the HTTP 500 error I was getting which pointed me to a Technet Article that described essentially the same issue.
I followed the steps but in my case I had about 10 Exchange server entries so I selected the first one and chose "include inheritable permissions from parent". After the obligatory OK clicks I ran the Exchange checker again and it passed. Then I tried my Droid in both Touchdown and the Native app and everything worked.
The native android email in Android 2.2 was failing with an unspecified error. I then tried Touchdown by Nitrodesk. It was also failing but they have nice logging built into their software and I was able to see the following:
Checking Certificate...
Checking ActiveSync with SSL...
Server is Microsoft-IIS/7.5
ActiveSync was found
ActiveSync Version :Versions:Microsoft-IIS/7.5,2.0,2.1,2.5,12.0,12.1,14.0,14.1
Trying activesync protocol -116...
ActiveSync provisioning returns HTTP:200
Error provisioning ActiveSync: Policy status is 0
Trying activesync protocol 2.5...
ActiveSync provisioning returns HTTP:200
ActiveSync provisioning success
The following policies have been requested :
Refreshing AS folders
Error refreshing folders
Checking 2007 with SSL...Error refreshing folders
The error refreshing folders was the key and NitroDesk support pointed me to the Nick MacKechnie blog. The main idea is that there is an issue with upgrading to Exchange 2010 and some of the permissions are not set correctly.
Another good Exchange troubleshooting tool I found is the Microsoft Exchange Remote Connectivity Analyzer . This tool pointed right to the HTTP 500 error I was getting which pointed me to a Technet Article that described essentially the same issue.
I followed the steps but in my case I had about 10 Exchange server entries so I selected the first one and chose "include inheritable permissions from parent". After the obligatory OK clicks I ran the Exchange checker again and it passed. Then I tried my Droid in both Touchdown and the Native app and everything worked.
Labels:
Activesync,
Android,
Exchange,
Small Business Server 2011
Subscribe to:
Posts (Atom)