I just installed the Finster cab for WM6's Remote Desktop on WM5. I have an 8125. I can connect to XP desktops just fine. I can connect to Vista desktops fine as long as they do not have "require network level authentication" enabled. I get "An internal error has occurred" if that is enabled. Last, I can't connect to any of my 2003 R2 servers. The 2003 R2 servers are set up to all require TLS mutual authentication for maximum security (corporate requirement).
Two questions...
1. Is this simply a WM5 thing? For instance, the internal equivelent of "schannel" just doesn't support the necessary TLS 1.0 requirement for those features? (or something like that) If I got a WM6 device (or installed one of those WM6 ROMs on my good ol' Wizard), this would work?
2. If this does occur on WM5 and WM6 devices both, how does one fix this? If at all?
Thanks.
EDIT: The phone does have the necessary root CA installed to authenticate the remote servers via SSL/TLS. I sync to Exchange over the air over SSL to the same server I'm attempting to remote into.
Related
Hello!
I have a Universal in german from T-Mobile Austria and a BlueAngel also from T-Mobile Austria. As we all know the Universal has the new OS Windows Mobile 5.0, the BlueAngel has Windows Mobile 2003.
So and there is a BIG difference between these two OS (OR A BIG BUG, I don't know).
The problem is: With the file-explorer (or Total Commander 2.0, which i prefer) you can connect with WLAN to a share on a computer. Enter the UNC-path under path in the file-explorer, the device asks for a login and it works. So it is unter Windows Mobile 2003 with the BlueAngel. And it doesn't matter to which computer I will connect: to my server with Windows Server 2003 or to my workstation with Windows XP. I enter my domain account and it works.
On the Universal it doesn't work when I will connect to my server with Windows Server 2003. It's absolutely impossible to connect to a share on my server. BUT I CAN connect to a share an my workstation with Windows XP WITH MY DOMAIN ACCOUNT. So what I see in the moment: The NTLM-authentication works because I can connect to any Windows XP with a domain account, but the connection to a share on a server with Windows Server 2003 fails. And this only with the Universal, because in the same time with my BlueAngel it works.
My question is: Has somebody the same ugly problem or maybe I do somethimg wrong, I don't know.
And that's the reason why I can't change my device in this moment and why I love my BlueAngel.
Best regards, Peter
i to have this issue, i can map to xp shares no probs but win2003server shares just loops on the password screen.
big issue for me this
w2k3 issues
Click to expand...
Click to collapse
I had the same issues on w2k3-server before installing the latest updates.
After new W2K3 installation and newest updates: no problems.
The problem could be active directory.
Have a look to "NetBIOS over IP" at IP-settings. Resco Explorer can't map UNCs, only NetBIOS-names, it's my monitoring.
Greetings, Gerd Dubrand
that dosent fix the problem, just tried it, it worked fine on my BA but not on JJ.
I also cannot connect to my Win2003 server via jasjar, but I can connect to my win2000 advanced server. Win2003 server is sbs2003 with all updates applied. Can connect to both via my pda2k. Interesting?
IS the server a DC? you may need to disable the 'Microsoft network server: Digitally sign communications (always)' setting the default DC GPO - http://support.microsoft.com/kb/823659. This is enabled by default for DC's and acan cuase issues when talking to downlevel clients (I've had this problem with samba clients.
It mayalso be set in the local secuirty policy.
But then again this might not be anything to do with it...
Anything in the logs on the server?
GOOD IDEA, TINTOY!!!
Thank you for your samba server and your idea, tintoy. Your hint works!
For all others aigan the solution:
On a Windows Server 2003 domain controller you have to disable 'Microsoft network server: Digitally sign communications (always)'. I haven't this done by Active Directory, i have this done by 'Security settings for domain controller' -> 'Security Options' in 'Management'.
Note: Please excuse when I don't have used the correct names, because I have only a german version of the Windows Server 2003 and I don't know the exact names of the program groups of the english version. But I hope you know, what I mean.
Thank you aigan tintoy, this problem is solved!
See you all again here,
Peter
I confirm this,
network server: Digitally sign communications (always)
change to disabled in the Default Domain Controller Security Settings.
This has just made my day. odd how wm5 is apparently newer but dosent quite work out the box like wm2003 did
np ;-)
Exchange 2003 not connect with mobile 6.1
Someone can write a detailed description ? I have the same problem.
Thanks
Having spent the past day or so struggling to get my shiny new HTC Wizard syncing correctly with Exchange 2003 I thought I would post the solution...
This only applies to those of you using ActiveSync to communicate from a WM5 (and possibly earlier?) with an Exchange 2003 server with SP2. SP2 looks handy for mobile users as it introduces HTTP direct push (well, it will shortly..) among st other features - this is the reason that I chose to install it.
Once installed, it allows a range of Mobile Access settings that include direct push (only actually available once MSFP devices - or patches - become available... Q2 seems to be the best estimate) as well as some interesting security features that allow a remote wipe of sensitive data, should a WM5 device be stolen/lost.
One of these security settings is to require a password on the handled device - a great idea... DON'T SET IT!! None of these security settings work with non MSFP devices - they throw a general server access error 85010004. So the server setting to check, on your Exchange 2003 SP2 server is:
(DOMAIN) > Global Settings > Mobile Devices
Click the "Device Security..." button
Make sure that the "Enforce password on device" checkbox is cleared - at lest until you have MSFP devices around
After that you can correct any other 85010004 or 85010014 errors using the advice from the Microsoft KnowledgeBase (have fun!). This SP2 problem isn't listed there yet (I got it, eventually, from a MS partner tech support site).
Hi Guy,
Have you been able to get Push to work? I installed the Exchange service Pack and enabled HTTP push. My WM5 wizard does a manual sync fine via GPRS, but when I check off realtime receipt, it keeps asking me for the phone's SMS number...
Have you encoutered this prob? I wonder if it makes a dif if my Phone OS is French while Exchange server is in English
Thanks
footang
Without the MSFP (which should be available VERY soon?) you have to rely on Exchange Server doing a 'fake push' using SMS... it sends an SMS to your device to tell the device to connect (over GPRS) to pick up new mail. This is NOT a proper push solution...
My understanding is that MSFP updates both the WM5 device AND the Exchange Server, enabling the server to implement true push... I'm seriously considering moving my Exchange to a hosted provider (probably Cobweb) as I have plenty of minor issues running Exchange 2003 on a small SBS server... Cobweb tell me they will have MSFP live this month.
I will let you know how I get on...
Guy,
I installed the latest QTEK Rom and push works great. The only prob is that it doesnt vibrate when the phone is in standby mode to let you know an email arrived.
cheers
I have always been able to succesfully connect to the exchange server via activesync, whether it be via GPRS or USB. Now I can't, I keep getting the http_500 error.
I have checked and I can log into the exchange server via OWA in either http or https. Have changed my phone to use SSL, not to use SSL, nothing, same error.
Looked at Microsoft's explanation of having a duplicate smpt address, but it can't be, as the server is running Exchange 2003 SP2, so I can't configure or look at the server. I also can't ask IT, as they don't know I have access and even if you ask, they won't know, as mobile devices are not yet supported.
1 - The Exchange Server has to be configured to allow Mobile Devices to connect.
2 - The Exchange server has to be configured to allow push mail
3 - I think you need to install a certificate on the PPC (using enroller, or just copy/paste the **.cer file and open it)
Maybe you don't need the certificate when NOT using SSL, but I think I remember I couldn't get it to work without... So I installed my certificate on my PPC and HAD TO use SSL to get it to work.
However, ...If you cannot even check whether your Sysops allow pushmail/ActiveSync, you are in dire straits.... You have to know that info.
I have a Sprint Mogul, which obviously lacks Remote Desktop. So I downloaded the WM6RDP.cab. I then tried connecting to my Vista laptop. Horray - it worked! Then I tried connecting to one of my servers. This server requires TLS to connect (this is the security feature introduced with Server 2003 SP1 that prevents man-in-the-middle attacks by encapsulating all RDP traffic within TLS 1.0 - Vista supports it also, but it's disabled by default). I tried connecting and got "An internal error has occurred." Is TLS supported at all on Remote Desktop for WM6, or is this some problem introduced because I installed RDP after the fact? Sigh, this is truly frustrating.
Hi,
I have a HTC TyTN ll and I am having problems synchronising my work email.
The server at work has exchange 2003 SP2 and Activesync. We also have both OWA and OMA and I can access these succesfully through the PDA.
The OWA/OMA both use SSL and have a instantssl certificate installed which I have downloaded and installed onto my device.
My credentials are correct, I have recreated the data source and resetted device but..
During snychronisation on the PDA I get the following error:
"ActiveSync encountered a problem on the server" Support Code: 0x85010014.
Following a google I found that this is as a result of having the SSL port 443 defined in IIS for the webmail site. Now if I remove this port I get the message "waiting for network". I have read this is temporary, but I have tried for the past few days and it still doesnt get past this stage. I am using our wireless and the GPRS as provided by orange to connect.
Also removing the port 443 has concequences on anyone else accessing the OWA as it does not work.
Do any of you guys know any ideas on how I can get the PDA to synchronise?
Will I have to first create an activesync partnership with the server?
Many Thanks in Advance
I now recieve the following error on the server:
Exchange Server 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=817379). For information about how to properly configure IIS to support Kerberos and NTLM authentication, see Microsoft Knowledge Base article 215383, "How To Configure IIS to Support Both Kerberos and NTLM Authentication" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=215383). This issue may occur after installing Windows SharePoint Services on a server running Exchange Server 2003. For information about how to properly configure a server to run both Windows SharePoint Services and Exchange Server 2003, see Microsoft Knowledge Base article 823265, "You receive a "Page not found" error message when you use Outlook Web Access (OWA) to browse the Exchange Server 2003 client after you install Windows SharePoint Services" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=823265).
Exchange is installed on an SBS 2003 and I dont believe the microsoft kb is useful for this. Even if it is, I can work around this by removing ssl. However at this point I dont get any errors on the server and all I get from the HTC is "waiting for network". As mentioned earliar.
Any suggestions would be highly appreciated.
Thanks