Archived from groups: microsoft.public.windowsxp.work_remotely (
More info?)
Right, and if it is not, one common cause of that symptom is failure to
re-apply the current SP to a machine after reinstalling the OS.
"Jeffrey Randow (MVP)" <jeffreyr-support@remotenetworktechnology.com> wrote
in message news:0f6ar0hnot7kqaf2sjm755ttarppb5u1m2@4ax.com...
> Make sure that the Remote Access Connection Manager service isn't
> disabled and start it if isn't running...
> ---
> Jeffrey Randow (Windows Networking MVP)
> jeffreyr-support@remotenetworktechnology.com
>
> Please post all responses to the newsgroups for the benefit
> of all USENET users. Messages sent via email may or may not
> be answered depending on time availability....
>
> Remote Networking Technology Support Site -
>
http://www.remotenetworktechnology.com
> Windows Network Technology Community -
>
http://www.microsoft.com/windowsserver2003/community/centers/networking/default.mspx
> Windows Home Networking Community -
>
http://www.microsoft.com/windowsxp/expertzone/communities/wireless.mspx
>
> On Sun, 5 Dec 2004 17:06:29 -0500, "Bill Sanderson"
> <Bill_Sanderson@msn.com.plugh.org> wrote:
>
>>Nope- -even a standalone XP Home machine can have an incoming VPN or
>>dialup
>>connection, etc.
>>
>>Go to Control Panel, Network Connections, and then "Create a new
>>connection", next, Set up an advanced, connection.
>>
>>You should see "Accept incoming connections."
>>
>>Is it not there? Is it grayed out?
>>
>>"cscsonline" <cscsonline@discussions.microsoft.com> wrote in message
>>news:5428DC6B-2BEF-45FD-98FA-A494C9A72358@microsoft.com...
>>> I'm a Consultant who wants to work on one of my client's WXP Pro
>>> desktops
>>> from home. However, when I go to the client's desktop to Network
>>> Connections
>>> and then Incoming Connections, Incoming Connections is not there. Is
>>> this
>>> because the client's computer has to be part of a domain before this
>>> shows
>>> up. It is just part of Workgroup at present.
>>> Thanks for any help.
>>
>