SE won't launch unless I'm logged into work domain

[johnlacko]

If I am at work logged in to our domain then when I click on SE it lauches. If I am disconected from our domain then when I click on SE it just sits there on the splash page. My workarounds: 1:VPN connect to our server then launch SE 2:use the "Clean SpeedEdit Configuration" batch file . Anyone else having this issue?????

[Gordon]

Is this a new behaviour or has this been a problem since SE was installed? It could have been unnoticed for quite a while, if your computer is normally connected to the domain.

However, it could also be because a file has been accessed over the domain by using a network drive and SE is looking for it when it launches. If this is the case then when you get SE going, clear the project so it is empty and then exit SE. Next time SE starts it should be okay without the domain connection.

[rbartlett]

Long pauses are not uncommon with starting up a raft of apps that attempt to scan your local drives. Trouble is many apps assume that a drive letter assignment is permanent and local (or at the worst, present as nearline storage).

If you do have drive letters you might try disconnecting them from Windows Explorer. They should be reconnectable later when you have to go back to corporate duties.

What I do is try to never map drive letters. Not always possible if you have company login scripts that directly reference a standard set of device letters but you could always have two hardware profiles defined (via Control Panel | System | Hardware | Hardware Profiles ) and select these at boot time.

As I don't map drive letters I have to go to the trouble of remembering the 'shares'. That is when having an IT department who names a server 'Stan' or 'Francine' and a container as 'finance' or 'artwork' can be helpful. You'll need the VPN up to see them for the first time and I'd recommend using the first-time password caching option in case you or your PC aren't fully fledged members of the domain-policy/forest. To access by the share name you have to put in the downward slash twice before every stem. \\Stan\finance or \\Francine\artwork. If those don't resolve you can (depending on IT policy enforcement) use \\10.1.2.3\finance or \\10.1.2.4\artwork where those dotted numbers equate to the IP addresses of the servers that ought to resolve by name but might just not due to the VPN technology in force.

There could be other reasons too, but the mapped drive problem is common. I think Mac Finder can have similar issues so it isn't quite a Microsoft-only pain. Of course your other apps may be able to handle this or might timeout more readily than SpeedEDIT.

If it isn't this then there might be something you've got set in preferences or in the last projects you opened (or their redo-stacks) that might have an affinity with your VPN connectivity (despite it being inaccessible quite often).

[johnlacko]

Thanks for the posts. I am the IT admin and do have about 5 or so mapped drives...so that could be the problem. I'll try to let it start up...I never really waited it out more than couple minutes. I did try clearing the project so it didn't reference anything...save it...close SE...disconnect from domain and it doesn't start (but like i said earlier I never really waited more than a couple minutes).

[Gordon]

If SE closed properly with an empty project and the filebin (if open) set to a local directory, then I would have expected it to start right away the next time.

[KiloWatkins]

I've been reading/watching this thread with interest. imho, besides what Richard and Gordon have posted, the SE Product Reg is on the server. Install SE on a mapped drive that is C: on another PC seen from the server.

I installed SE on a system, lets call 3rd drive. I then cloned that C: to make an OS/programs backup. When I boot to the backup it finds SE on the 3rd drive.

Sorry if you need a decoder ring....lol.....I/O joke.

[Gordon]

John;
I too was thinking that there might be some install issue on a network drive similar to what Kilo has suggested but couldn't come up with a scenerio where SE would start to launch and hang rather than complain about not finding a library or some such. Could happen, but I would expect SE to time out after 1 - 5 minutes and then complain.

Was the SE computer logged into the network for the first install? If so, it may be faster to uninstall SE, disconnect form the network, (including unplugging network cable just to be sure MS doesn't automatically make a connection), and then re-install SE. This would either fix the problem or it may help us narrow the problem down.