Protocol Error Unidentifiable Command Specified
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Verify IMAP/POP3 connection to Microsoft Exchange Server 5.5 up vote 1 down vote favorite I wanted to fully explore IMAP connections from the command line, if I can connect via Thunderbird, then I should be able to via telnet?! Microsoft detail IMAP login as :- LOGIN NTDOMAIN/NTACCOUNT/ALIAS PASSWORD The settings in my Thunderbird are :-
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: IMAP Credentials to Exchange Exchange Server > Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients Question 0 Sign in to vote Hi all, I'm trying to migrate an Exchange 2003 box to Office 365 via IMAP. I enabled the IMAP service and ran Test-MigrationServerAvailability -IMAP -Port 143 successfully. However, I'm getting authentication issues. After Telneting into the server I http://serverfault.com/questions/334726/verify-imap-pop3-connection-to-microsoft-exchange-server-5-5 have ran the login commands with every possible credential combination I have seen IMAP responds to: login contoso\user Password --> "Unidentifiable command specified" a1 login contoso\user Password --> BAD Protocol Error: "Expected SPACE not found" The one that seems to be pointing to the right direction is: http://support.microsoft.com/kb/189326/en-au ?login contoso/user/mailbox Password --> a1 NO Logon https://social.technet.microsoft.com/Forums/office/en-US/33d0e3b4-1ceb-4be6-9c23-fb669cc7ae59/imap-credentials-to-exchange?forum=exchangesvrclients Failure: unknown user name or bad password Apparently, the convention is domain/user_name/mailbox_name Password --> But I'm having no love here :( Thanks guys Thursday, August 07, 2014 6:38 AM Reply | Quote Answers 0 Sign in to vote Thanks for your suggestion QuanGD however this is a small company and perform a staged migration is not an option for them. BTW: I managed to solve the problem. It was a silly overlook by me as the server is a very old box migrated from Server 2000 and didn't have the user logon name populated but only the (pre-Windows2000 name). Finally I managed to Telnet into it via 143and can migrate the data via IMAP. Thanks. Marked as answer by Mavis_HuangMicrosoft contingent staff, Moderator Thursday, August 14, 2014 4:44 AM Tuesday, August 12, 2014 2:32 AM Reply | Quote All replies 0 Sign in to vote Hi, I suggest upgrading Exchange 2010 from 2003 first, then migrate to Office 365. Also suggest ask O
inHidden fieldsSearch for groups or messages
a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Courses Vendor Services Groups Careers Store Headlines Website Testing Experts Exchange > Questions > creating a policy on watchguard x750e product Want to Advertise Here? Solved creating a policy on watchguard x750e product Posted on 2012-06-14 Software Firewalls 1 Verified Solution 2 Comments 697 Views Last Modified: 2012-07-03 i have created a policy to open port 143 however, it is giving the following error: * OK Microsoft Exchange Server 2003 IMAP4rev1 server version 6.5.7638.1 (.................) ready. HEAD BAD Protocol Error: "Unidentifiable command specified". User-Agent: BAD Protocol Error: "Unidentifiable command specified". Host: BAD Protocol Error: "Unidentifiable command specified". Accept: BAD Protocol Error: "Unknown command found". * BAD Protocol Error: "Tag not found in command". there must be something wrong with the policy that i created but i have no clue i created it using a static nat with to properties of any external and the ip address of the site, followed byt the port number and from properties any - external. any ideas? 0 Question by:LBC Facebook Twitter LinkedIn Google LVL 32 Best Solution bydpk_wal Please make sure you have indeed opened all ports needed for the service. Look at traffic monitor as it would give you some details if some ports are blocked by WG. Have a look at video to make sure Go to Solution 2 Comments LVL 32 Overall: Level 32 Software Firewalls 23 Message Accepted Solution by:dpk_wal2012-06-16 Please make sure you have indeed opened all ports needed for the service. Look at traffic monitor as it would give you some details if some ports are blocked by WG. Have a look at video to make sure that the policy is configured properly: http://www.watchguard.com/education/video/play.asp?vid=ff_fireware_ingress Please check and update. Thank you. 0 Message Author Closing Comment by:LBC2012-07-03 thanks for the information