501 Header Values Specify a Method That is Not Implemented - activesync test

501 Header Values Specify a Method That is Not Implemented

     

It is possible to test activesync connectivity and availability on an Exchange 2007 or 2010 server without a smartphone. The FASTEST way to test for access to activesync on an Exchange server without a smartphone is to enter the the activesync URL into your browser's address bar and connect to it. The message you receive will look like the one in this post but that is NORMAL. The reason we get that message, as erroneous as it looks, it because it's a browser not a smartphone. The smartphone not only connects to the activesync URL but it also passes login information which we do not when manually entering the URL address into our browser.

The URL to test activesync on an exchange 2007 or 2010 server without a smartphone is :

https: //yourdoamin.com/Microsoft-Activesync-Server.

The the text in the URL is CaSe sensitive.

501 header values specify a method that is not implemented. When receiving this "error" message during an active sync test without a smartphone, it is normal. Test activesync using a URL from a computer via a browser.

This page is normal for when connecting to an exchange 2007 server with SP1 or Exchange 2010 using a browser with the active sync URL as the address. The message between Exchange 2007 and Exchange 2010 differs much because of the differences in the IIS versions. It's only an appearance difference for an exchange 2007 server on windows 2003 or windows 2008 server .

Also, on different Windows Server versions, for example Windows 2003 Server the IIS version differs enough and the error codes also different so that's what's going to generate a different looking 501 error in the browser. with Microsoft Exchange 2007 on Microsoft Windows 2003, the message reads 501/505 not implemented or not supported. The image above is Microsoft Exchange 2007 on windows server 2008. Microsoft Exchange 2010 on Windows 2008 or 2008 R2 will be the same because remember, it's IIS that's actually presenting the error code and page to the browser not Exchange.

http://www.blogger.com/img/blank.gif http://onlineremotesupportsoftware.blogspot.com/ http://www.blogger.com/img/blank.gif 

501 Header values specify a method that is not implemented

Enhance and Improve your Support Service

Provide improved  remote technical support to clients and users, even family and friends.  Whether you're  a member of a large MSP network operations center team or a single  person business servicing and accessing desktops from a small office or home office, 4RemoteSupport software for online desktop support  improves service levels for all business sizes.  It is common for MSP and  individual IT support service providers to provide remote desktop access support utilizing multiple desktop screen sharing software. Remote control access software that requires software such as an  agent installed on the remote desktops for  future re-connections tend to cost more than online desktop support software used only when required.  remote desktop software that's agent based, requires installation and leaves a service running. These types of online desktop support software services usually incurs a charge per each remote desktop. Non-agent remote desktop client applications  permits online remote desktop connections when needed and connections are usually initiated by the user on the remote desktop. Most providers will have and use both types support tools appropriate for different scenarios. 4RemoteSupport online desktop support software does not require pre-installation nor require plugin software or framework services like .NET preinstalled. It works with all popular browsers. No browser extensions or plugins needed. 

Configure SSH on ESXi 4.0 Host

Steps to configure SSH on ESXi 4.0 Host.

From the main screen on the ESXi host press Alt + F1.

At the next screen type:

unsupported

and enter the root password when prompted.

Use a text editor to uncomment (remove the hash symbol #) from the beggining of the following line in the file /etc/inetd.conf. Then save the changes:
# ssh stream tcp nowait root /sbin/dropbearmulti dropbear -l

Resatrt the process called inetd by running:

#cat /var/run/inetd.pid
#kill -HUP


Verify the ESXi host is accessible by SSH. To do this from the SSH client, log into the ESX host:

~ # dbclient root@server
The output will be similar to: