Sorry Alan. Replied to Luke - but didn't include that to the tutor list as a whole! We are running Windows XP. The students log in to a network server that allows them access to their user accounts as well as various group folders. We have 4 rooms full of computers - but Python is installed on each workstation in this room only ie, it is "active" in this room only. It is not on the network and no other computer rooms have access to it. The students in this room save their Python files to a networked "user" account - as they do with all their other files. Two failures have occurred. The first has been intermittent and to individual students only at rare times. A student will attempt to start IDLE - and nothing will happen. Sometimes, changing that student's log in user name will solve the problem, and he then has access to Python again. The 2nd is more pervasive, and that is, whenever I have the class working with Python - the entire school network becomes inoperable, and the system administrator needs to reboot it again. Because we have been working on Python each time this has happened, Python is being blamed for the system failure. Inoperable - no one is able to open any files in any program, save any work they have been working on, open files - or even log in if they haven't already. The whole system is " frozen", from the office to every other computer in the school. Now I am inclined to think it is not a Python problem at all. Python is locally and individually installed on computers in this room only. It has no network access at all - apart from files being saved in networked user accounts. What I would like to know is if anyone else has had a similar problem - and it has been proven that Python is the cause? If so - how was the problem solved? Be grateful for any advice - and hope I have made the situation clearer now. Diana > Alan Gauld wrote: > > Diana, > > It is almost certainly not a Python problem but related to how > you have the network set up. As Luke was trying to point out, > we mifght be able to help out but your description of the > network setup wasn't clear. > > We need more precise information about things like: > what OS you are using? > Are you using Domains/NIS/NDS etc? > Do you have shared drives, VNC, windows terminal server? > How do you define a 'lab'? > What do you mean by python being 'active'? > And what exactly happens when a failure occurs? > > None of these things are standardised in anmy way. > > Alan G > > > > ----- Original Message ----- > From: "Diana Hawksworth" > To: "Tom Schinckel" ; > Sent: Monday, August 14, 2006 7:55 AM > Subject: Re: [Tutor] Python on network problems > > > > Thanks Tom. I installed the latest version on Friday - but today > > the system went down again. I am inclined to think it is not a > > Python problem at all. Just need someone who also has it installed > > on a network to know if they have had any problems!! > > Diana > > > > ----- Original Message ----- > > From: "Tom Schinckel" > > To: > > Sent: Monday, August 14, 2006 4:28 PM > > Subject: Re: [Tutor] Python on network problems > > > > > >> Diana Hawksworth wrote: > >>> Dear List, > >>> > >>> I have Python installed on 1 of 4 labs at my High School. The lab > >>> is connected to a whole school network. Students login through > >>> the network - but Python is active in this lab only. > >>> > >>> Sometimes I have a student who simply cannot access Python, even > >>> though he has been working on it for a number of months now. > >>> Usually a change in username will solve the problem - but I would > >>> like to know what is causing this to happen. > >>> > >>> The second problem is much more severe. Seems for the past three > >>> weeks now, the entire system will crash. It happens when we are > >>> working on Python - so the assumption is that the program is to > >>> blame. I cannot see that it is - but it certainly is upsetting > >>> when it happens. Has anyone had a similar accurrence with Python > >>> and networks? If so - what have you done about it. If not - then > >>> any clues about what could be happening so that I can get the > >>> system administrator off my back - and get the system working > >>> again!! > >>> > >>> Thanks for any suggestions. > >>> > >>> Diana > >>> _______________________________________________ > >>> Tutor maillist - Tutor@python.org > >>> http://mail.python.org/mailman/listinfo/tutor > >>> > >>> > >> It sounds a tad out of my depth, but when I first installed Python, > >> IDLE crashed, all the time. > >> > >> Try the age old software fix: reinstall. > >> > >> Cheers > >> > >> Tom > >> > > > > > > > >