Accessing python from a network share in windows 7

[aj]

I access python from a network share. This works fine on XP but on
windows 7 it throws the following error:

Python 2.6.1 (r261:67517, Dec 4 2008, 16:51:00) [MSC v.1500 32 bit
(Intel)] on
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import random
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "t:\win32\python-2.6.1\lib\random.py", line 871, in <module>
_inst = Random()
File "t:\win32\python-2.6.1\lib\random.py", line 96, in __init__
self.seed(x)
File "t:\win32\python-2.6.1\lib\random.py", line 110, in seed
a = long(_hexlify(_urandom(16)), 16)
WindowsError: [Error 127] The specified procedure could not be found

Is there some security policy that I need to enable/disable to use
python from a network on windows 7?

[MRAB]

Is it a problem with the share or with Windows 7? Does it work with
Windows 7 when running a local copy of Python?

[aj]

It works without any issue on win7 if I copy python to my local drive.
Also, accessing python from the same network share works fine on win
XP. So I am suspecting some security policy of win7 that is causing
problem while accessing it over a network share.

[r0g]

You might also want to ask on Microsoft Answers...

http://social.answers.microsoft.com/Forums/en-US/categories

Good luck,

Roger

[Anssi Saari]

aj <mailtome20...@gmail.com> writes:

Well, there was just a complaint about this sort of thing on a local
newsgroup here. Specifically, someone was trying to execute a Windows
program from a share and every time Windows 7 pops up a warning window
saying that the program is maybe from the evil interwebby and are you
really sure you actually want to run it. So probably that's the
command line version of same.

Solution is apparently specifying your server to be in the local
intranet, in IE's security settings. Apparently there is a non-working
autodetection for what is a local intranet, so specifying the server
IP address by hand in the advanced settigns is the working solution.

[aj]

On Jan 9, 3:55 am, Anssi Saari <a...@sci.fi> wrote:

Thanks for the suggestion Anssi. I added the server in the local
intranet settings for IE, but that did not make any difference.