Dial up networking with SierraWireless 555

[Guest]

Hi,

I'm running XPe SP2 with the networking application compatibility component
and cannot get the DUN connections to work.

-If I use the SierraWireless Client software I can connect.
-If I use the DUN connection from the "network connections" control panel
and try to connect I get "All Devices Connected error 50: The request is not
supported."

In XP Pro on the same hardware both operations connect successfully.

Does anyone know of some subtle component I need to add to the image or
whether there is a problem with XPe SP2?

I have resorted to adding all of the macro components to my image including
the built in SierraWireless 300 CDPD card that came with XPe in the hopes
that the component would have the missing dependency and bring it in.
Unfortunately nothing has worked.

Thanks,
Ed.

 

[KM]

Ed,

I am not sure about the SierraWireless Client software but for DUN you can start and add the components mentioned in this thread:
http://groups-beta.google.com/group/microsoft.public.windowsxp.embedded/msg/d136d198fe5739ae

 

[Guest]

Thanks for you reply. As it turned out I did have all of these components
but the component "Internet Authentication Service (IAS) and Remote Access
Common Files" had files and resources disabled in my image.

I beleive these were disabled in an attempt to optimise the footprint.
Nothing like inventing work for myself.

I wish there was a way to reset the components to there default settings.
Or to search for disabled elements of a component.

Thanks,
Ed.

 

[KM]

SilentCode,

Thanks for you reply. As it turned out I did have all of these components
but the component "Internet Authentication Service (IAS) and Remote Access
Common Files" had files and resources disabled in my image.

I beleive these were disabled in an attempt to optimise the footprint.
Nothing like inventing work for myself.

I wish there was a way to reset the components to there default settings.
Or to search for disabled elements of a component.

On SP1 there was a "bug" that if you upgrade a component (to next revision or next version or next SP) TD lost the component
settings you set up manually (including disabled resources).
This was fixed for SP2 RTM, though.