Problems with Windows Server 2003

[Cocco82]

Hi guys,

i have a LAN with a Windows Server 2003 as main computer that shares
an hard drive with letter F: from which all the other computers (Win
XP Pro SP2) execute the programs i need for my work.

Now i need to write a program myself, and i have compiled it with
Visual Basic 2005.
If i work directly on the Server 2003, that's ok, but if i work from a
terminal and i launch the program from the drive F:, it hang up and
claims errors in mscorlib.dll, Security.Permis sion.something and so
many other.

If i instead execute the program from the drive G: (a drive shared by
a Win Xp computer) it's all right.

The program should be establish some TCP connections to internet,
using System.Net.Sock ets.


Can anyone help me please?

Thanks in advice.

[rowe_newsgroups]

Re: Problems with Windows Server 2003

On Jul 31, 10:33 pm, Cocco82 <cocc...@cocco8 2.netwrote:

Hi guys,
>
i have a LAN with a Windows Server 2003 as main computer that shares
an hard drive with letter F: from which all the other computers (Win
XP Pro SP2) execute the programs i need for my work.
>
Now i need to write a program myself, and i have compiled it with
Visual Basic 2005.
If i work directly on the Server 2003, that's ok, but if i work from a
terminal and i launch the program from the drive F:, it hang up and
claims errors in mscorlib.dll, Security.Permis sion.something and so
many other.
>
If i instead execute the program from the drive G: (a drive shared by
a Win Xp computer) it's all right.
>
The program should be establish some TCP connections to internet,
using System.Net.Sock ets.
>
Can anyone help me please?
>
Thanks in advice.

..Net programs run from a intranet have extremely limited rights - you
can elevate them use the .Net configuration wizard. Here's a similar
link that I walked another user through the process:

http://groups.google.com/group/microsoft.public.dotnet.languages.vb/browse_thread/thread/d7d16055ca80b9a1/2a52938c6f746bc7?lnk=st&q=permission&rnum=1&hl=en#2a52938c6f746bc7

Alternatively, I would recommend you use ClickOnce deployment to
publish / run your application. This will copy the project to your
local drive (with full permissions) - it also has built in features to
check for prerequisites and updates. You should search MSDN for more
information on ClickOnce if you're interested.

Thanks,

Seth Rowe