Error 67 with login script - too fast?


Go Back   Computer Help Articles > Windows XP Network Web
User Name
Password
FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 01-05-2006, 04:10 AM
CoffeeMan
 
Posts: n/a
Default Error 67 with login script - too fast?

The login script I use works well in my peer-to-peer environment, except
when I want it to be executed at startup.

My computer has automatic loging into main account (using TweakUI) and the
login script is executed at startup but can't map any share drive (Error
67). I tried both share names and IP with NET USE command. Weirdly enough,
the SAME script launched manually just a few seconds after startup works
well.

- If I login into Windows with a logon screen (classic or XP-Style), the
script will works because Windows will have finished to startup in
background. If Windows autologon using TweakUI, the script won't work, like
if it was running few seconds to early. Lauching it manually after startup
and the script will work.

- Same behavior with Prefetch. If the prefetch directory is empty, the
script will work. If the prefetch is not empty, Windows starts faster and
the script won't work when launched the first time. I have to launched it
manually

The only solution I found is to "wake up" the LAN by pinging it quite a few
times, but then the login delay is tedious.

Here is the script:

@echo off
Title Connection
echo Connection en cours
Ping serveur -n 1 | find " TTL="
if errorlevel 1 goto WakeIt
goto NoWake

:WakeIt
Title Connection **
ping localhost -n 20
Ping serveur -n 1

:NoWake
net use R: "\\serveur\data" /persistent:No
net use S: "\\serveur\lib" /persistent:No
net use T: "\\serveur\musique" /persistent:No

Ping bureau -n 1 | find " TTL="
if errorlevel 1 goto NoBureau
net use U: "\\bureau\data" /persistent:no
net use V: "\\bureau\lib" /persistent:no
:Nobureau

Ping famille -n 1 | find " TTL="
if errorlevel 1 goto NoFamille
net use w: "\\famille\lib" /persistent:no
:Nofamille


* * *

My guess is that this error 67 is related to master browsing delay.

Anyway suggestion to solve this?
Reply With Quote
  #2  
Old 01-05-2006, 04:10 AM
GTS
 
Posts: n/a
Default Re: Error 67 with login script - too fast?

Group Policy Editor (gpedit.msc) - Computer Configuration --> Administrative
Templates --> System --> Logon. Set the policy that says "Always wait for
the network at computer startup and logon".
(Note this usually will not work with wireless connections.)
--

"CoffeeMan" <CoffeeMan@nowhere.com> wrote in message
news:Xns972D48F33E4CCoffeeMan@207.46.248.16...
> The login script I use works well in my peer-to-peer environment, except
> when I want it to be executed at startup.
>
> My computer has automatic loging into main account (using TweakUI) and the
> login script is executed at startup but can't map any share drive (Error
> 67). I tried both share names and IP with NET USE command. Weirdly enough,
> the SAME script launched manually just a few seconds after startup works
> well.
>
> - If I login into Windows with a logon screen (classic or XP-Style), the
> script will works because Windows will have finished to startup in
> background. If Windows autologon using TweakUI, the script won't work,
> like
> if it was running few seconds to early. Lauching it manually after startup
> and the script will work.
>
> - Same behavior with Prefetch. If the prefetch directory is empty, the
> script will work. If the prefetch is not empty, Windows starts faster and
> the script won't work when launched the first time. I have to launched it
> manually
>
> The only solution I found is to "wake up" the LAN by pinging it quite a
> few
> times, but then the login delay is tedious.
>
> Here is the script:
>
> @echo off
> Title Connection
> echo Connection en cours
> Ping serveur -n 1 | find " TTL="
> if errorlevel 1 goto WakeIt
> goto NoWake
>
> :WakeIt
> Title Connection **
> ping localhost -n 20
> Ping serveur -n 1
>
> :NoWake
> net use R: "\\serveur\data" /persistent:No
> net use S: "\\serveur\lib" /persistent:No
> net use T: "\\serveur\musique" /persistent:No
>
> Ping bureau -n 1 | find " TTL="
> if errorlevel 1 goto NoBureau
> net use U: "\\bureau\data" /persistent:no
> net use V: "\\bureau\lib" /persistent:no
> :Nobureau
>
> Ping famille -n 1 | find " TTL="
> if errorlevel 1 goto NoFamille
> net use w: "\\famille\lib" /persistent:no
> :Nofamille
>
>
> * * *
>
> My guess is that this error 67 is related to master browsing delay.
>
> Anyway suggestion to solve this?



Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Windows XP Login Question FF Windows XP Configuration Manage 1 01-05-2006 07:29 AM
Smart Card Login + Certificate Login to AD -> Lost smart card JY Windows XP Security Admin 0 01-05-2006 05:04 AM
Login under domain Jeffenie Windows XP Security Admin 7 01-05-2006 04:17 AM
SP2 Firewall mods via Login Script LVDave Windows XP Security Admin 2 01-05-2006 04:17 AM
I need to run my own script AFTER network login script dmontaldo Windows XP New Users 1 01-05-2006 03:55 AM


All times are GMT. The time now is 12:54 PM.


Powered by vBulletin Version 3.5.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd. SEO by vBSEO 2.3.2 © 2005, Crawlability, Inc.

Error 67 with login script - too fast?