Re: Pocket PC 2003 - Can access OMA etc, but cannot sync with ActiveSync
From: Stuart Mackie [MCP, MSP] (newsgroups_at_--REMOVE_THIS-NO_SPAM--stu.uk.com)
Date: 11/10/04
- Next message: Mephizell: "Clients cannot login to domain from remote subnet"
- Previous message: Marina Roos [SBS-MVP]: "Re: Missing something with RWW?"
- In reply to: Stuart Mackie [MCP, MSP]: "Re: Pocket PC 2003 - Can access OMA etc, but cannot sync with ActiveSync"
- Next in thread: Wayne Small [SBS-MVP]: "Re: Pocket PC 2003 - Can access OMA etc, but cannot sync with ActiveSync"
- Reply: Wayne Small [SBS-MVP]: "Re: Pocket PC 2003 - Can access OMA etc, but cannot sync with ActiveSync"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 10 Nov 2004 02:09:21 -0000
Spoke too soon, I think I've found the problem. On realising the cert being
used by IIS indicated publishing.stu.local I altered the PDA sync server
from server.domain.local to publishing.stu.local and it worked with SSL
enabled. Change it back to server.domain.local and it fails straight away.
So my final question is :) why SBS2k3 is producing the cert
publishing.stu.local when I can see I typed stu.domain.local, and what can I
do to fix it :)
-- Hth, Stuart Mackie [MCP, MSP] www.stu.uk.com "Stuart Mackie [MCP, MSP]" <newsgroups@--REMOVE_THIS-NO_SPAM--stu.uk.com> wrote in message news:%237rfwasxEHA.1188@tk2msftngp13.phx.gbl... > Hi Wayne. Unfortunately I'm still getting the SSL certificate error. I > followed your instructions as much as possible. I uninstalled current > ActiveSync, re-deployed using SBS then the PDA moaned about old version of > activesync so had to upgrade the workstation (to version 3.7.1). After a > few resets I paired PDA with workstation using activesync so the PDA could > be seen then executed Configure Mobile Device. After running the > Configure program I checked the PDA for certs and it had installed two > certs, one of which is the SSL cert and the other I'm not totally sure on. > I then opened the Activesync configuration and added my username, password > etc and tried to sync. Unfortunately I then got the dreaded Internet_38 > SSL cert incorrect error. > > The only bit I may be going wrong is the FQDN for the cert. I'm using > 'server.domain.local' since the PDA is connecting from the internal side > of the network. I've checked and the SSL cert being used for > server.domain.local when opening https://server.domain.local, and it is > the same cert installed on the PDA. > > The only bit that puzzles me is the actual cert listed in IIS. If I view > the certificate IIS is using the certificate issued to and issued by > publishing.stu.local which doesn't make sense. If I check the date on > this particular cert it is listed as today, i.e the new one I created > earlier, but if the cert is assigned to publishing.stu.local it won't > validate as server.domain.local. Is it possible IIS isn't accepting the > new certificate and subsequently requires me to manually force it to use > another ? > > -- > Thanks, > Stuart Mackie [MCP, MSP] > www.stu.uk.com > > > "Stuart Mackie [MCP, MSP]" <newsgroups@--REMOVE_THIS-NO_SPAM--stu.uk.com> > wrote in message news:%23h1f99oxEHA.3844@TK2MSFTNGP12.phx.gbl... >> Hi Wayne. Thanks for taking the time to write the instructions up for >> me. I will have a go with them shortly since I have done it differently >> which is probably why I'm having the cert problems :) >> >> I have two question regarding the naming of the certificate (part 1.). >> The server (server.domain.local) is visible to the internet for SMTP >> (mail.stu.uk.com). External access is done via VPN (including PDAs). >> Subsequently although external users will be outside the network when >> they connect, their VPN connection will bring them through a second >> firewall and they will appear as internal workstations on the internal >> side of ISA server etc. Does this affect the choice of certificate >> domain name since only access is allowed internally and not externally ? >> At the minute I've used server.domain.local which is probably where I'm >> going wrong. Users access the server via https://server or >> https://server.domain.local/ >> >> On viewing the certificate I've created so far using CEICW, it is listed >> in the Certificate MMC as publishing.stu.local. Although I may have used >> the wrong domain name, is this how the certificate should be listed ? >> >> -- >> Thanks again, >> Stuart Mackie [MCP, MSP] >> www.stu.uk.com >> >> >> "Wayne Small [SBS-MVP]" <wayne@correct.com.au> wrote in message >> news:%233kKz1oxEHA.3080@TK2MSFTNGP14.phx.gbl... >>> Stuart, >>> >>> Having read the thread, it sounds like you've not used the "Configure >>> Mobile Device" option to configure the device itself. This normally >>> handles most of the issues that you see here. I would suggest you do the >>> following; 1. Rerun the CEICW (Connect to Internet) wizard on the SBS >>> server and ensure that the domain name you enter is one that is >>> accessible from the Internet - ie mail.stu.uk.com. This is a MUST. >>> >>> 2. Run the Assing Applications to the Client computer wizard, and follow >>> through to the point where you can tick the "Install ActiveSync 3.7" >>> onto the computer. >>> >>> 3. Reboot the client computer and allow ActiveSync to install 4. On the >>> client computer - run the "Configure Mobile Device" option to configure >>> the mobile device with the certificates etc. >>> >>> 5. On the client computer - go to Activesync and Tools > Options > Rules >>> tab and ensure that the Passthrough option at the bottom is set to "The >>> Internet". >>> >>> Then try to perform a sync with the server via the USB cradle. >>> >>> Let me know how this goes. >>> >>> Regards, >>> >>> Wayne Small [SBS-MVP] >>> >>> MCSE+I MCSE 2000 >>> >>> Technical Director - Correct Solutions Pty Ltd For all the answers on >>> Microsoft's Small Business Server- check out www.sbsfaq.com >>> >>> "Stuart Mackie [MCP, MSP]" >>> <newsgroups@--REMOVE_THIS-NO_SPAM--stu.uk.com> wrote in message >>> news:uTWqBwGxEHA.2196@TK2MSFTNGP14.phx.gbl... >>>> Hi. I am having problems getting a new i-mate PDA2k pocket pc 2003 to >>>> sync with Exchange 2003. I initially had problems with the error "Item >>>> no longer exists.The item you are attempting to access may have been >>>> deleted or moved." I realised the local path was wrong for >>>> exchange-oma folder and after fixing this was able to access OMA from >>>> internal workstations, and the PDA connected through USB to a >>>> workstation which satisfies it has connectivity to the server. >>>> >>>> The problem I'm having now is I still cannot get ActiveSync to work >>>> against Exchange. Everything seems configured correctly but I continue >>>> to get the ActiveSync error INTERNET_55. >>>> >>>> There is nothing obvious in the event log and I will start looking >>>> through the Exchange and IIS logs tomorrow to try and work out what is >>>> going wrong. Has anyone had a similar problem, or able to suggest what >>>> would cause this ? >>>> >>>> -- >>>> Thanks, >>>> Stuart Mackie [MCP, MSP] >>>> www.stu.uk.com >>>> >>>> >>> >>> >> >> > >
- Next message: Mephizell: "Clients cannot login to domain from remote subnet"
- Previous message: Marina Roos [SBS-MVP]: "Re: Missing something with RWW?"
- In reply to: Stuart Mackie [MCP, MSP]: "Re: Pocket PC 2003 - Can access OMA etc, but cannot sync with ActiveSync"
- Next in thread: Wayne Small [SBS-MVP]: "Re: Pocket PC 2003 - Can access OMA etc, but cannot sync with ActiveSync"
- Reply: Wayne Small [SBS-MVP]: "Re: Pocket PC 2003 - Can access OMA etc, but cannot sync with ActiveSync"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
