[W2003] Loading OCX -> Windows firewall pops up

  • Thread starter Thread starter Gilles Ganault
  • Start date Start date
G

Gilles Ganault

Hello

I'm stuck trying to get a Visual Basic Classic program to load
an OCX on a Windows 2003 Server on which I'm working with non-admin
rights through Terminal Services: In the Form_Load() even, I'm trying
to use the MSWinsock OCX control, but the firewall pops up telling me
I don't have the required rights for this.

When commenting out the Winsock1.* lines, no pop-up. The program works
fine on a host on which I'm connected as admin.

I'm a bit stuck at where to look for an answer:
- firewall
- user rights
- user profiles
- NTFS user rights
- Terminal Services

Thanks for any tip.
 
"Gilles Ganault" <nospam@nospam.com> wrote in message
news:or81d3h9q772pbc67n87nep2motp6b85ek@4ax.com...
> Hello
>
> I'm stuck trying to get a Visual Basic Classic program to load
> an OCX on a Windows 2003 Server on which I'm working with non-admin
> rights through Terminal Services: In the Form_Load() even, I'm trying
> to use the MSWinsock OCX control, but the firewall pops up telling me
> I don't have the required rights for this.
>
> When commenting out the Winsock1.* lines, no pop-up. The program works
> fine on a host on which I'm connected as admin.
>
> I'm a bit stuck at where to look for an answer:
> - firewall
> - user rights
> - user profiles
> - NTFS user rights
> - Terminal Services
>


But your program runs, right? This seems to me like more of a Windows issue
than a VB one. Try asking in a Windows newsgroup. I think you'll probably
stand a better chance of getting assistance.

--
Mike
Microsoft MVP Visual Basic
 
On Sat, 25 Aug 2007 19:39:30 -0400, "MikeD" <nobody@nowhere.edu>
wrote:
>But your program runs, right? This seems to me like more of a Windows issue
>than a VB one.

Right, it was W2003's firewall: for a program to be allowed to open a
socket, it must be added in the firewall's list of authorized apps.

Thanks.
 
"Gilles Ganault" <nospam@nospam.com> wrote in message
news:an53d3trd4ramosrvjapgb76sbecc0hvtq@4ax.com...
> On Sat, 25 Aug 2007 19:39:30 -0400, "MikeD" <nobody@nowhere.edu>
> wrote:
>>But your program runs, right? This seems to me like more of a Windows
>>issue
>>than a VB one.
>
> Right, it was W2003's firewall: for a program to be allowed to open a
> socket, it must be added in the firewall's list of authorized apps.
>
> Thanks.

I suppose that makes sense.

--
Mike
Microsoft MVP Visual Basic
 
Back
Top