With all the issues around WMDC, I figured I would try to put my 2
cents to solve some of the issues some people may be seeing, so here
goes, feel free to post about other items that may work, or those that
I have suggested that do not work:

Connectivity (The lights are on but no one is home...)

Issue: connects Windows Mobile device to Vista PC, drivers install,
but WMDC does not initiate. May have a newly purchased machine with
Vista pre-loaded.

Resolution:
1) Check Device Manager - Microsoft Windows Mobile Remote Adapter
driver.
a. Go to Device Manager
b. Look under "Network Adapters"
c. Check properties - Driver

Incorrect Driver:
Version: 6.0.6000.16386
Date: 6/21/2006

Correct Driver:
Version: 6.1.6783.0 (or later)
Date: 1/24/2007 (or later)

The incorrect driver version can be updated by going to the driver
tab, then select "Update Driver" this should initiate a connection
with the internet and download the newer driver version. This could
be
due to the fact that Vista RTM'd before WMDC RTM'd.

After the update, you may need to unplug, then re-plug the device into
the USB ports, then manually select ActiveSync on the phone to
initiate the WMDC process. Once initiated the EULA for the WMDC will
display and the user will need to accept the EULA before the WMDC will
download and be functional.

Firewall

Issue: WMDC is available, can be initiated by going to the Control
Panel, then opening "Windows Mobile Device Center", however the device
will not connect to the WMDC (may or may not be able to be initiated
since the WMDC is downloaded on first connect). The quickest way to
determine if the firewall is interfering with the WMDC is to
completely disable the Firewall/Anti-Virus software to see if
connection functionality is achieved.

Resolution:

The following ports need to be open in order for the WMDC to operate
properly (nearly identical to AS version 4.x)

- port990: open inbound TCP
- port999: open inbound TCP
- port5678: open inbound TCP
- port5679: open outbound UDP
- port5721: open inbound TCP
- port26675: open inbound TCP

The following processes should be allowed if there are issues with
firewall/anti-virus software.

- C:\Windows\WindowsMobile\wmdc.exe
- C:\Windows\WindowsMobile\wmdHost.exe
- C:\Windows\WindowsMobile\wmdsyncman.dll

Functionality

Issue: can only copy/browse files on the device. (pre-WM2003)

Resolution: WMDC only supports sync'ing for devices that are Windows
Mobile 2003 and higher, previously devices may work, but only for file
access.

Services

When using a Windows Mobile 2003 to connect to the Windows Mobile
Device Center there is a specific service that must be running.
Services running are listed in the Control Panel under Classic View,
then Administrated Tools, Services. This is also the mode used if
your device has the ability to "Disabled Advanced networking
functionality"

Windows Mobile 2003 - based device connectivity

Startup should be set to Automatic (Delayed Start or Automatic), if
this service is not enabled then a Windows Mobile 2003 will not be
able to be connected to WMDC. The service name for this is WcesComm.

Windows Mobile 5 devices connect to the WMDC using a different service
than the WM2003 based devices.

Windows Mobile-based device connectivity

Without this service enabled Windows Mobile devices will not be able
to connect to the WMDC. The dependency for this service is the
Windows Mobile 2003 - based connectivity. The service name is
RapiMgr.

Feel free to use this info, however you wish...please post results...

-JasperM

"JasperM" <jasper.morse******.com> wrote in message
news:1175094371.212253.25880@n59g2000hsh.googlegro ups.com...
> With all the issues around WMDC, I figured I would try to put my 2
> cents to solve some of the issues some people may be seeing, so here
> goes, feel free to post about other items that may work, or those that
> I have suggested that do not work:

<snip>...

Nice, succinct solutions.

We are going to reserve you a seat at the front of the class. Thanks!

Tried to update the drivers as you explained -- shows I have the old driver,
but when I attempted to update-online, was 'told' I had the most up-to-date
drivers. Is there a way to download the newer drivers manually...? Thanks

"JasperM" <jasper.morse******.com> wrote in message
news:1175094371.212253.25880@n59g2000hsh.googlegro ups.com...
> With all the issues around WMDC, I figured I would try to put my 2
> cents to solve some of the issues some people may be seeing, so here
> goes, feel free to post about other items that may work, or those that
> I have suggested that do not work:
>
> Connectivity (The lights are on but no one is home...)
>
> Issue: connects Windows Mobile device to Vista PC, drivers install,
> but WMDC does not initiate. May have a newly purchased machine with
> Vista pre-loaded.
>
> Resolution:
> 1) Check Device Manager - Microsoft Windows Mobile Remote Adapter
> driver.
> a. Go to Device Manager
> b. Look under "Network Adapters"
> c. Check properties - Driver
>
> Incorrect Driver:
> Version: 6.0.6000.16386
> Date: 6/21/2006
>
> Correct Driver:
> Version: 6.1.6783.0 (or later)
> Date: 1/24/2007 (or later)
>
> The incorrect driver version can be updated by going to the driver
> tab, then select "Update Driver" this should initiate a connection
> with the internet and download the newer driver version. This could
> be
> due to the fact that Vista RTM'd before WMDC RTM'd.
>
> After the update, you may need to unplug, then re-plug the device into
> the USB ports, then manually select ActiveSync on the phone to
> initiate the WMDC process. Once initiated the EULA for the WMDC will
> display and the user will need to accept the EULA before the WMDC will
> download and be functional.
>
> Firewall
>
> Issue: WMDC is available, can be initiated by going to the Control
> Panel, then opening "Windows Mobile Device Center", however the device
> will not connect to the WMDC (may or may not be able to be initiated
> since the WMDC is downloaded on first connect). The quickest way to
> determine if the firewall is interfering with the WMDC is to
> completely disable the Firewall/Anti-Virus software to see if
> connection functionality is achieved.
>
> Resolution:
>
> The following ports need to be open in order for the WMDC to operate
> properly (nearly identical to AS version 4.x)
>
> - port990: open inbound TCP
> - port999: open inbound TCP
> - port5678: open inbound TCP
> - port5679: open outbound UDP
> - port5721: open inbound TCP
> - port26675: open inbound TCP
>
> The following processes should be allowed if there are issues with
> firewall/anti-virus software.
>
> - C:\Windows\WindowsMobile\wmdc.exe
> - C:\Windows\WindowsMobile\wmdHost.exe
> - C:\Windows\WindowsMobile\wmdsyncman.dll
>
> Functionality
>
> Issue: can only copy/browse files on the device. (pre-WM2003)
>
> Resolution: WMDC only supports sync'ing for devices that are Windows
> Mobile 2003 and higher, previously devices may work, but only for file
> access.
>
> Services
>
> When using a Windows Mobile 2003 to connect to the Windows Mobile
> Device Center there is a specific service that must be running.
> Services running are listed in the Control Panel under Classic View,
> then Administrated Tools, Services. This is also the mode used if
> your device has the ability to "Disabled Advanced networking
> functionality"
>
> Windows Mobile 2003 - based device connectivity
>
> Startup should be set to Automatic (Delayed Start or Automatic), if
> this service is not enabled then a Windows Mobile 2003 will not be
> able to be connected to WMDC. The service name for this is WcesComm.
>
> Windows Mobile 5 devices connect to the WMDC using a different service
> than the WM2003 based devices.
>
> Windows Mobile-based device connectivity
>
> Without this service enabled Windows Mobile devices will not be able
> to connect to the WMDC. The dependency for this service is the
> Windows Mobile 2003 - based connectivity. The service name is
> RapiMgr.
>
> Feel free to use this info, however you wish...please post results...
>
> -JasperM
>

"Chester" <nojunkmail@pretendmail.com> wrote in message
news:4205215C-F20D-497A-A997-9BBB678693AB@microsoft.com...
> Tried to update the drivers as you explained -- shows I have the old
> driver, but when I attempted to update-online, was 'told' I had the most
> up-to-date drivers. Is there a way to download the newer drivers
> manually...? Thanks

Try "to uninstall the driver (Advanced)" from the list, disconnect your
device after and reboot the PC.
Next time you connect the device, Vista will install the driver from the
scratch and you can select to have a check online if there is a newer driver
available already.

--
Cheers ~ Arne Hess - Microsoft MVP Mobile Devices

Publisher & Editor in Chief "the::unwired"
http://www.theunwired.net

Publisher & Editor in Chief "the::placeshift" (NEW & BETA)
http://www.theplaceshift.net

On Mar 28, 6:49 pm, "Chester" <nojunkm...@pretendmail.com> wrote:
> Tried to update the drivers as you explained -- shows I have the old driver,
> but when I attempted to update-online, was 'told' I had the most up-to-date
> drivers. Is there a way to download the newer drivers manually...? Thanks
>
> "JasperM" <jasper.mo...******.com> wrote in message
>
> news:1175094371.212253.25880@n59g2000hsh.googlegro ups.com...
>
> > With all the issues around WMDC, I figured I would try to put my 2
> > cents to solve some of the issues some people may be seeing, so here
> > goes, feel free to post about other items that may work, or those that
> > I have suggested that do not work:
>
> > Connectivity (The lights are on but no one is home...)
>
> > Issue: connects Windows Mobile device to Vista PC, drivers install,
> > but WMDC does not initiate. May have a newly purchased machine with
> > Vista pre-loaded.
>
> > Resolution:
> > 1) Check Device Manager - Microsoft Windows Mobile Remote Adapter
> > driver.
> > a. Go to Device Manager
> > b. Look under "Network Adapters"
> > c. Check properties - Driver
>
> > Incorrect Driver:
> > Version: 6.0.6000.16386
> > Date: 6/21/2006
>
> > Correct Driver:
> > Version: 6.1.6783.0 (or later)
> > Date: 1/24/2007 (or later)
>
> > The incorrect driver version can be updated by going to the driver
> > tab, then select "Update Driver" this should initiate a connection
> > with the internet and download the newer driver version. This could
> > be
> > due to the fact that Vista RTM'd before WMDC RTM'd.
>
> > After the update, you may need to unplug, then re-plug the device into
> > the USB ports, then manually select ActiveSync on the phone to
> > initiate the WMDC process. Once initiated the EULA for the WMDC will
> > display and the user will need to accept the EULA before the WMDC will
> > download and be functional.
>
> > Firewall
>
> > Issue: WMDC is available, can be initiated by going to the Control
> > Panel, then opening "Windows Mobile Device Center", however the device
> > will not connect to the WMDC (may or may not be able to be initiated
> > since the WMDC is downloaded on first connect). The quickest way to
> > determine if the firewall is interfering with the WMDC is to
> > completely disable the Firewall/Anti-Virus software to see if
> > connection functionality is achieved.
>
> > Resolution:
>
> > The following ports need to be open in order for the WMDC to operate
> > properly (nearly identical to AS version 4.x)
>
> > - port990: open inbound TCP
> > - port999: open inbound TCP
> > - port5678: open inbound TCP
> > - port5679: open outbound UDP
> > - port5721: open inbound TCP
> > - port26675: open inbound TCP
>
> > The following processes should be allowed if there are issues with
> > firewall/anti-virus software.
>
> > - C:\Windows\WindowsMobile\wmdc.exe
> > - C:\Windows\WindowsMobile\wmdHost.exe
> > - C:\Windows\WindowsMobile\wmdsyncman.dll
>
> > Functionality
>
> > Issue: can only copy/browse files on the device. (pre-WM2003)
>
> > Resolution: WMDC only supports sync'ing for devices that are Windows
> > Mobile 2003 and higher, previously devices may work, but only for file
> > access.
>
> > Services
>
> > When using a Windows Mobile 2003 to connect to the Windows Mobile
> > Device Center there is a specific service that must be running.
> > Services running are listed in the Control Panel under Classic View,
> > then Administrated Tools, Services. This is also the mode used if
> > your device has the ability to "Disabled Advanced networking
> > functionality"
>
> > Windows Mobile 2003 - based device connectivity
>
> > Startup should be set to Automatic (Delayed Start or Automatic), if
> > this service is not enabled then a Windows Mobile 2003 will not be
> > able to be connected to WMDC. The service name for this is WcesComm.
>
> > Windows Mobile 5 devices connect to the WMDC using a different service
> > than the WM2003 based devices.
>
> > Windows Mobile-based device connectivity
>
> > Without this service enabled Windows Mobile devices will not be able
> > to connect to the WMDC. The dependency for this service is the
> > Windows Mobile 2003 - based connectivity. The service name is
> > RapiMgr.
>
> > Feel free to use this info, however you wish...please post results...
>
> > -JasperM

Which distro of Vista do you have? Also, on the driver tab you used
the "Update Driver" button correct, from inside of Device Manger? It
should have then established a network link to download the driver
from MS...in short, no I don't believe there is a way to manually
download that specific driver.

-JasperM

The RTM version, and yes, attempted to update per the instructions in the
post.

"JasperM" <jasper.morse******.com> wrote in message
news:1175176706.632844.68090@n76g2000hsh.googlegro ups.com...
> On Mar 28, 6:49 pm, "Chester" <nojunkm...@pretendmail.com> wrote:
>> Tried to update the drivers as you explained -- shows I have the old
>> driver,
>> but when I attempted to update-online, was 'told' I had the most
>> up-to-date
>> drivers. Is there a way to download the newer drivers manually...?
>> Thanks
>>
>> "JasperM" <jasper.mo...******.com> wrote in message
>>
>> news:1175094371.212253.25880@n59g2000hsh.googlegro ups.com...
>>
>> > With all the issues around WMDC, I figured I would try to put my 2
>> > cents to solve some of the issues some people may be seeing, so here
>> > goes, feel free to post about other items that may work, or those that
>> > I have suggested that do not work:
>>
>> > Connectivity (The lights are on but no one is home...)
>>
>> > Issue: connects Windows Mobile device to Vista PC, drivers install,
>> > but WMDC does not initiate. May have a newly purchased machine with
>> > Vista pre-loaded.
>>
>> > Resolution:
>> > 1) Check Device Manager - Microsoft Windows Mobile Remote Adapter
>> > driver.
>> > a. Go to Device Manager
>> > b. Look under "Network Adapters"
>> > c. Check properties - Driver
>>
>> > Incorrect Driver:
>> > Version: 6.0.6000.16386
>> > Date: 6/21/2006
>>
>> > Correct Driver:
>> > Version: 6.1.6783.0 (or later)
>> > Date: 1/24/2007 (or later)
>>
>> > The incorrect driver version can be updated by going to the driver
>> > tab, then select "Update Driver" this should initiate a connection
>> > with the internet and download the newer driver version. This could
>> > be
>> > due to the fact that Vista RTM'd before WMDC RTM'd.
>>
>> > After the update, you may need to unplug, then re-plug the device into
>> > the USB ports, then manually select ActiveSync on the phone to
>> > initiate the WMDC process. Once initiated the EULA for the WMDC will
>> > display and the user will need to accept the EULA before the WMDC will
>> > download and be functional.
>>
>> > Firewall
>>
>> > Issue: WMDC is available, can be initiated by going to the Control
>> > Panel, then opening "Windows Mobile Device Center", however the device
>> > will not connect to the WMDC (may or may not be able to be initiated
>> > since the WMDC is downloaded on first connect). The quickest way to
>> > determine if the firewall is interfering with the WMDC is to
>> > completely disable the Firewall/Anti-Virus software to see if
>> > connection functionality is achieved.
>>
>> > Resolution:
>>
>> > The following ports need to be open in order for the WMDC to operate
>> > properly (nearly identical to AS version 4.x)
>>
>> > - port990: open inbound TCP
>> > - port999: open inbound TCP
>> > - port5678: open inbound TCP
>> > - port5679: open outbound UDP
>> > - port5721: open inbound TCP
>> > - port26675: open inbound TCP
>>
>> > The following processes should be allowed if there are issues with
>> > firewall/anti-virus software.
>>
>> > - C:\Windows\WindowsMobile\wmdc.exe
>> > - C:\Windows\WindowsMobile\wmdHost.exe
>> > - C:\Windows\WindowsMobile\wmdsyncman.dll
>>
>> > Functionality
>>
>> > Issue: can only copy/browse files on the device. (pre-WM2003)
>>
>> > Resolution: WMDC only supports sync'ing for devices that are Windows
>> > Mobile 2003 and higher, previously devices may work, but only for file
>> > access.
>>
>> > Services
>>
>> > When using a Windows Mobile 2003 to connect to the Windows Mobile
>> > Device Center there is a specific service that must be running.
>> > Services running are listed in the Control Panel under Classic View,
>> > then Administrated Tools, Services. This is also the mode used if
>> > your device has the ability to "Disabled Advanced networking
>> > functionality"
>>
>> > Windows Mobile 2003 - based device connectivity
>>
>> > Startup should be set to Automatic (Delayed Start or Automatic), if
>> > this service is not enabled then a Windows Mobile 2003 will not be
>> > able to be connected to WMDC. The service name for this is WcesComm.
>>
>> > Windows Mobile 5 devices connect to the WMDC using a different service
>> > than the WM2003 based devices.
>>
>> > Windows Mobile-based device connectivity
>>
>> > Without this service enabled Windows Mobile devices will not be able
>> > to connect to the WMDC. The dependency for this service is the
>> > Windows Mobile 2003 - based connectivity. The service name is
>> > RapiMgr.
>>
>> > Feel free to use this info, however you wish...please post results...
>>
>> > -JasperM
>
> Which distro of Vista do you have? Also, on the driver tab you used
> the "Update Driver" button correct, from inside of Device Manger? It
> should have then established a network link to download the driver
> from MS...in short, no I don't believe there is a way to manually
> download that specific driver.
>
> -JasperM
>

On Mar 29, 3:28 pm, "Chester" <nojunkm...@pretendmail.com> wrote:
> The RTM version, and yes, attempted to update per the instructions in the
> post.
>
> "JasperM" <jasper.mo...******.com> wrote in message
>
> news:1175176706.632844.68090@n76g2000hsh.googlegro ups.com...
>
> > On Mar 28, 6:49 pm, "Chester" <nojunkm...@pretendmail.com> wrote:
> >> Tried to update the drivers as you explained -- shows I have the old
> >> driver,
> >> but when I attempted to update-online, was 'told' I had the most
> >> up-to-date
> >> drivers. Is there a way to download the newer drivers manually...?
> >> Thanks
>
> >> "JasperM" <jasper.mo...******.com> wrote in message
>
> >>news:1175094371.212253.25880@n59g2000hsh.googleg roups.com...
>
> >> > With all the issues around WMDC, I figured I would try to put my 2
> >> > cents to solve some of the issues some people may be seeing, so here
> >> > goes, feel free to post about other items that may work, or those that
> >> > I have suggested that do not work:
>
> >> > Connectivity (The lights are on but no one is home...)
>
> >> > Issue: connects Windows Mobile device to Vista PC, drivers install,
> >> > but WMDC does not initiate. May have a newly purchased machine with
> >> > Vista pre-loaded.
>
> >> > Resolution:
> >> > 1) Check Device Manager - Microsoft Windows Mobile Remote Adapter
> >> > driver.
> >> > a. Go to Device Manager
> >> > b. Look under "Network Adapters"
> >> > c. Check properties - Driver
>
> >> > Incorrect Driver:
> >> > Version: 6.0.6000.16386
> >> > Date: 6/21/2006
>
> >> > Correct Driver:
> >> > Version: 6.1.6783.0 (or later)
> >> > Date: 1/24/2007 (or later)
>
> >> > The incorrect driver version can be updated by going to the driver
> >> > tab, then select "Update Driver" this should initiate a connection
> >> > with the internet and download the newer driver version. This could
> >> > be
> >> > due to the fact that Vista RTM'd before WMDC RTM'd.
>
> >> > After the update, you may need to unplug, then re-plug the device into
> >> > the USB ports, then manually select ActiveSync on the phone to
> >> > initiate the WMDC process. Once initiated the EULA for the WMDC will
> >> > display and the user will need to accept the EULA before the WMDC will
> >> > download and be functional.
>
> >> > Firewall
>
> >> > Issue: WMDC is available, can be initiated by going to the Control
> >> > Panel, then opening "Windows Mobile Device Center", however the device
> >> > will not connect to the WMDC (may or may not be able to be initiated
> >> > since the WMDC is downloaded on first connect). The quickest way to
> >> > determine if the firewall is interfering with the WMDC is to
> >> > completely disable the Firewall/Anti-Virus software to see if
> >> > connection functionality is achieved.
>
> >> > Resolution:
>
> >> > The following ports need to be open in order for the WMDC to operate
> >> > properly (nearly identical to AS version 4.x)
>
> >> > - port990: open inbound TCP
> >> > - port999: open inbound TCP
> >> > - port5678: open inbound TCP
> >> > - port5679: open outbound UDP
> >> > - port5721: open inbound TCP
> >> > - port26675: open inbound TCP
>
> >> > The following processes should be allowed if there are issues with
> >> > firewall/anti-virus software.
>
> >> > - C:\Windows\WindowsMobile\wmdc.exe
> >> > - C:\Windows\WindowsMobile\wmdHost.exe
> >> > - C:\Windows\WindowsMobile\wmdsyncman.dll
>
> >> > Functionality
>
> >> > Issue: can only copy/browse files on the device. (pre-WM2003)
>
> >> > Resolution: WMDC only supports sync'ing for devices that are Windows
> >> > Mobile 2003 and higher, previously devices may work, but only for file
> >> > access.
>
> >> > Services
>
> >> > When using a Windows Mobile 2003 to connect to the Windows Mobile
> >> > Device Center there is a specific service that must be running.
> >> > Services running are listed in the Control Panel under Classic View,
> >> > then Administrated Tools, Services. This is also the mode used if
> >> > your device has the ability to "Disabled Advanced networking
> >> > functionality"
>
> >> > Windows Mobile 2003 - based device connectivity
>
> >> > Startup should be set to Automatic (Delayed Start or Automatic), if
> >> > this service is not enabled then a Windows Mobile 2003 will not be
> >> > able to be connected to WMDC. The service name for this is WcesComm.
>
> >> > Windows Mobile 5 devices connect to the WMDC using a different service
> >> > than the WM2003 based devices.
>
> >> > Windows Mobile-based device connectivity
>
> >> > Without this service enabled Windows Mobile devices will not be able
> >> > to connect to the WMDC. The dependency for this service is the
> >> > Windows Mobile 2003 - based connectivity. The service name is
> >> > RapiMgr.
>
> >> > Feel free to use this info, however you wish...please post results...
>
> >> > -JasperM
>
> > Which distro of Vista do you have? Also, on the driver tab you used
> > the "Update Driver" button correct, from inside of Device Manger? It
> > should have then established a network link to download the driver
> > from MS...in short, no I don't believe there is a way to manually
> > download that specific driver.
>
> > -JasperM

by distro, I meant, do you have Basic, Ultimate etc...I have used this
method on Vista Home Basic, and Ultimate. You have an internet
connection when you are attempting this correct?

-JasperM