Remote Automation using Visual Foxpro

Hi...

Is there anybody found a way to overcome the "RestrictRemoteClients" setting
on Windows XP SP2 (of course without set it to 0) ?

But I believe (correct me if I am wrong), this shall be solve by Microsoft
because there is no command under Foxpro which can control the RPC call. All
the RPC call is done by Foxpro.

Does Microsoft plan a SP for Visual Foxpro 8 to solve this issue or it has
been incorporated to Visual Foxpro 9 ?

Thanks in advance ....

Rudy

Stefan
Wed Jan 12 04:54:37 CST 2005

> Does Microsoft plan a SP for Visual Foxpro 8 to solve this issue or it has
> been incorporated to Visual Foxpro 9 ?

As a personal guess I'd say there are probably no plans to enable
VFP to circumvent the new WinXP SP2 security enhancments.
See also these links (some may get line-wrapped by your news reader):

http://blogs.msdn.com/vsdata/archive/2004/08/18/216378.aspx

http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx

http://support.microsoft.com/default.aspx?scid=kb;en-us;841893

http://www.microsoft.com/downloads/details.aspx?FamilyId=9300BECF-2DEE-4772-ADD9-AD0EAF89C4A7&displaylang=en

http://groups.google.com/groups?hl=de&lr=&threadm=u3fZCQw2EHA.3120%40TK2MSFTNGP12.phx.gbl&rnum=1&prev=/groups%3Fhl%3Dde%26lr%3D%26selm%3Du3fZCQw2EHA.3120%2540TK2MSFTNGP12.phx.gbl


hth
-Stefan

"erha" <rudy@guardmydata.com> schrieb im Newsbeitrag
news:eR9r1oF%23EHA.4028@TK2MSFTNGP15.phx.gbl...
> Hi...
>
> Is there anybody found a way to overcome the "RestrictRemoteClients" setting
> on Windows XP SP2 (of course without set it to 0) ?
>
> But I believe (correct me if I am wrong), this shall be solve by Microsoft
> because there is no command under Foxpro which can control the RPC call. All
> the RPC call is done by Foxpro.
>
> Does Microsoft plan a SP for Visual Foxpro 8 to solve this issue or it has
> been incorporated to Visual Foxpro 9 ?
>
> Thanks in advance ....
>
> Rudy
>
>

erha
Wed Jan 12 20:45:54 CST 2005

Hi Stefan,

Thanks for your response.

But it is very hard to convince a customer to allow us to change the policy
setting (RestrictRemoteClients) since the Microsoft itself has recommended
this.

IMHO, the Microsoft Visual Foxpro team shall of course update the VFP to
overcome this. Perhaps on the Visual Foxpro 9, since is not yet released.


Rudy

----- Original Message -----
From: "Stefan Wuebbe" <stefan.wuebbe@gmx.de>
Newsgroups: microsoft.public.fox.programmer.exchange
Sent: Wednesday, January 12, 2005 6:54 PM
Subject: Re: Remote Automation using Visual Foxpro


> > Does Microsoft plan a SP for Visual Foxpro 8 to solve this issue or it
has
> > been incorporated to Visual Foxpro 9 ?
>
> As a personal guess I'd say there are probably no plans to enable
> VFP to circumvent the new WinXP SP2 security enhancments.
> See also these links (some may get line-wrapped by your news reader):
>
> http://blogs.msdn.com/vsdata/archive/2004/08/18/216378.aspx
>
>
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;841893
>
>
http://www.microsoft.com/downloads/details.aspx?FamilyId=9300BECF-2DEE-4772-
ADD9-AD0EAF89C4A7&displaylang=en
>
>
http://groups.google.com/groups?hl=de&lr=&threadm=u3fZCQw2EHA.3120%40TK2MSFT
NGP12.phx.gbl&rnum=1&prev=/groups%3Fhl%3Dde%26lr%3D%26selm%3Du3fZCQw2EHA.312
0%2540TK2MSFTNGP12.phx.gbl
>
>
> hth
> -Stefan
>
> "erha" <rudy@guardmydata.com> schrieb im Newsbeitrag
> news:eR9r1oF%23EHA.4028@TK2MSFTNGP15.phx.gbl...
> > Hi...
> >
> > Is there anybody found a way to overcome the "RestrictRemoteClients"
setting
> > on Windows XP SP2 (of course without set it to 0) ?
> >
> > But I believe (correct me if I am wrong), this shall be solve by
Microsoft
> > because there is no command under Foxpro which can control the RPC call.
All
> > the RPC call is done by Foxpro.
> >
> > Does Microsoft plan a SP for Visual Foxpro 8 to solve this issue or it
has
> > been incorporated to Visual Foxpro 9 ?
> >
> > Thanks in advance ....
> >
> > Rudy
> >
> >
>

Dan
Thu Jan 13 11:50:29 CST 2005

No application at Microsoft will be be updated to circumvent intentionally
placed security restrictions.

VFP9 released before Christmas.

Dan

erha wrote:
> Hi Stefan,
>
> Thanks for your response.
>
> But it is very hard to convince a customer to allow us to change the
> policy setting (RestrictRemoteClients) since the Microsoft itself has
> recommended this.
>
> IMHO, the Microsoft Visual Foxpro team shall of course update the VFP
> to overcome this. Perhaps on the Visual Foxpro 9, since is not yet
> released.
>
>
> Rudy
>
> ----- Original Message -----
> From: "Stefan Wuebbe" <stefan.wuebbe@gmx.de>
> Newsgroups: microsoft.public.fox.programmer.exchange
> Sent: Wednesday, January 12, 2005 6:54 PM
> Subject: Re: Remote Automation using Visual Foxpro
>
>
>>> Does Microsoft plan a SP for Visual Foxpro 8 to solve this issue or
>>> it has been incorporated to Visual Foxpro 9 ?
>>
>> As a personal guess I'd say there are probably no plans to enable
>> VFP to circumvent the new WinXP SP2 security enhancments.
>> See also these links (some may get line-wrapped by your news reader):
>>
>> http://blogs.msdn.com/vsdata/archive/2004/08/18/216378.aspx
>>
>>
>
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx
>>
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;841893
>>
>>
>
http://www.microsoft.com/downloads/details.aspx?FamilyId=9300BECF-2DEE-4772-
> ADD9-AD0EAF89C4A7&displaylang=en
>>
>>
>
http://groups.google.com/groups?hl=de&lr=&threadm=u3fZCQw2EHA.3120%40TK2MSFT
>
NGP12.phx.gbl&rnum=1&prev=/groups%3Fhl%3Dde%26lr%3D%26selm%3Du3fZCQw2EHA.312
> 0%2540TK2MSFTNGP12.phx.gbl
>>
>>
>> hth
>> -Stefan
>>
>> "erha" <rudy@guardmydata.com> schrieb im Newsbeitrag
>> news:eR9r1oF%23EHA.4028@TK2MSFTNGP15.phx.gbl...
>>> Hi...
>>>
>>> Is there anybody found a way to overcome the
>>> "RestrictRemoteClients" setting on Windows XP SP2 (of course
>>> without set it to 0) ?
>>>
>>> But I believe (correct me if I am wrong), this shall be solve by
>>> Microsoft because there is no command under Foxpro which can
>>> control the RPC call. All the RPC call is done by Foxpro.
>>>
>>> Does Microsoft plan a SP for Visual Foxpro 8 to solve this issue or
>>> it has been incorporated to Visual Foxpro 9 ?
>>>
>>> Thanks in advance ....
>>>
>>> Rudy

Stefan
Sun Jan 16 03:41:32 CST 2005

Hi Rudy,

"erha" <rudy@guardmydata.com> schrieb im Newsbeitrag
news:%230HI%23nR%23EHA.2568@TK2MSFTNGP10.phx.gbl...
> Hi Stefan,
>
> Thanks for your response.
>
> But it is very hard to convince a customer to allow us to change the policy
> setting (RestrictRemoteClients) since the Microsoft itself has recommended
> this.

On the other hand, its only one dedicated server you'd have to configure
to accept incoming (DCOM/RPC) requests, all clients would be
untouched, right?

Microsoft's new security policy, as introduced with SP2 for WinXP,
did actually cause some turbulence, AFAIK.
VFP is only one of many products being affected.

FWIW, given that the entire "world wide web" changed from a former
kind of academic paradise to become a playground for script kiddies
first and now even for organized criminals - personally, I (was surprised
and) do appreciate the new approach, i.e. conceptional security
enhancements by reducing default feature "luxury".
As for DCOM in particular, it's a pity of course.


> IMHO, the Microsoft Visual Foxpro team shall of course update the VFP to
> overcome this. Perhaps on the Visual Foxpro 9, since is not yet released.

As Dan pointed out, VFP9 is "released to manufacturing", already
available for MSDN subscribers now, boxes in the shops soon.


hth
-Stefan

erha
Sun Jan 16 20:59:03 CST 2005

Hi Stefan,

Too bad....

But once more, it will not easy to convince our customer especially on the
big company which have very tight security policy.

Perhaps VFP 9 SP1 will be released soon, and the changes is included.

Rudy


"Stefan Wuebbe" <stefan.wuebbe@gmx.de> wrote in message
news:Ofy0tB7#EHA.3368@TK2MSFTNGP10.phx.gbl...
> Hi Rudy,
>
> "erha" <rudy@guardmydata.com> schrieb im Newsbeitrag
> news:%230HI%23nR%23EHA.2568@TK2MSFTNGP10.phx.gbl...
> > Hi Stefan,
> >
> > Thanks for your response.
> >
> > But it is very hard to convince a customer to allow us to change the
policy
> > setting (RestrictRemoteClients) since the Microsoft itself has
recommended
> > this.
>
> On the other hand, its only one dedicated server you'd have to configure
> to accept incoming (DCOM/RPC) requests, all clients would be
> untouched, right?
>
> Microsoft's new security policy, as introduced with SP2 for WinXP,
> did actually cause some turbulence, AFAIK.
> VFP is only one of many products being affected.
>
> FWIW, given that the entire "world wide web" changed from a former
> kind of academic paradise to become a playground for script kiddies
> first and now even for organized criminals - personally, I (was surprised
> and) do appreciate the new approach, i.e. conceptional security
> enhancements by reducing default feature "luxury".
> As for DCOM in particular, it's a pity of course.
>
>
> > IMHO, the Microsoft Visual Foxpro team shall of course update the VFP to
> > overcome this. Perhaps on the Visual Foxpro 9, since is not yet
released.
>
> As Dan pointed out, VFP9 is "released to manufacturing", already
> available for MSDN subscribers now, boxes in the shops soon.
>
>
> hth
> -Stefan
>

Cyrus
Mon Jan 17 11:52:00 CST 2005

erha wrote:
> Hi Stefan,
>
> Too bad....
>
> But once more, it will not easy to convince our customer especially on the
> big company which have very tight security policy.
>
> Perhaps VFP 9 SP1 will be released soon, and the changes is included.
>
> Rudy
>
>
> "Stefan Wuebbe" <stefan.wuebbe@gmx.de> wrote in message
> news:Ofy0tB7#EHA.3368@TK2MSFTNGP10.phx.gbl...
>
>>Hi Rudy,
>>
>>"erha" <rudy@guardmydata.com> schrieb im Newsbeitrag
>>news:%230HI%23nR%23EHA.2568@TK2MSFTNGP10.phx.gbl...
>>
>>>Hi Stefan,
>>>
>>>Thanks for your response.
>>>
>>>But it is very hard to convince a customer to allow us to change the
>
> policy
>
>>>setting (RestrictRemoteClients) since the Microsoft itself has
>
> recommended
>
>>>this.
>>
>>On the other hand, its only one dedicated server you'd have to configure
>>to accept incoming (DCOM/RPC) requests, all clients would be
>>untouched, right?
>>
>>Microsoft's new security policy, as introduced with SP2 for WinXP,
>>did actually cause some turbulence, AFAIK.
>>VFP is only one of many products being affected.
>>
>>FWIW, given that the entire "world wide web" changed from a former
>>kind of academic paradise to become a playground for script kiddies
>>first and now even for organized criminals - personally, I (was surprised
>>and) do appreciate the new approach, i.e. conceptional security
>>enhancements by reducing default feature "luxury".
>>As for DCOM in particular, it's a pity of course.
>>
>>
>>
>>>IMHO, the Microsoft Visual Foxpro team shall of course update the VFP to
>>>overcome this. Perhaps on the Visual Foxpro 9, since is not yet
>
> released.
>
>>As Dan pointed out, VFP9 is "released to manufacturing", already
>>available for MSDN subscribers now, boxes in the shops soon.
>>
>>
>>hth
>>-Stefan
>>
>
>
>
I think the point is as everyone has been saying is that Microsoft is
not going to make VFP (or any other of their products) circumvent that
restriction. MS has gone to the idea of restricting anything that is
not needed for all installations (or at least most) and if you need
something they by default turn off/block you will have to do so. This
is because 90+% of machines don't need remote automation. You can pretty
much put money on it that VFP9 (or even VFP 10 for that matter) will not
circumvent that setting. If you need to use that functionality, then
you will have to change the settings to allow it.