[wpkg-users] firefox and acrobat
Rainer Meier
r.meier at wpkg.org
Mon Apr 14 22:43:12 CEST 2008
Hi,
Tomasz Chmielewski wrote:
>> 2008-04-14 14:03:12, DEBUG : Initialized temporary local log file: C:\WINDOWS\TEMP\wpkg-logInit.log
>> 2008-04-14 14:03:12, DEBUG : Initializing new log file: C:\WINDOWS\TEMP\wpkg-dell002.log
>> 2008-04-14 14:03:12, DEBUG : Reboot-Cmd is standard.
>> 2008-04-14 14:03:13, DEBUG : WPKG 1.0 starting...
>> 2008-04-14 14:03:13, DEBUG : Base directory is '\\hq\wpkg\cur'.
>> 2008-04-14 14:03:13, DEBUG : Log level is 255
>> 2008-04-14 14:03:13, DEBUG : Trying to read XML file: \\hq\wpkg\cur\profiles.xml
>> 2008-04-14 14:04:20, DEBUG : Successfully loaded XML file: \\hq\wpkg\cur\profiles.xml
>
> It waits over 30 seconds to access the first file - looks like either:
>
> 1) this workstation is *very* slow
> 2) your profiles.xml file is *very* large (and all other XML files)
> 3) there is some problem accessing network shares (WINS, DNS resolution,
> other network problems etc.).
>
> If I'd have to bet here, I'd bet on 3).
ACK.
Recently I've seen similar behavior on a couple of Windows XP machines.
It was re-producable that connections to new hosts were "hanging" for
quite a long time. After the connection was established, then data
transfer was fast as usual. So it was difficult to debug since all
transfer-bandwith testers just tested the bandwith, and not something
like an "initial delay".
Test was easy:
- open cmd
- ping www.google.com
Then ping hung for half a minute to a minute and then response times
showed normal answer times ranging from 20 to 60ms.
I run WinsockFixXP on this machines which fixed the problem.
@Brian: Probably you can try that or just run the following commands on
your command line:
netsh winsock reset
netsh winsock reset catalog
netsh firewall reset
netsh firewall set icmpsetting 8
netsh firewall set service FILEANDPRINT ENABLE SUBNET
then reboot and check again.
br,
Rainer
More information about the wpkg-users
mailing list