Systemadministration FK14 schrieb: >> >> Some more debugging ideas. >> >> As a pre-command use cmd.exe. Also, enable WPKG Client GUI for >> debugging (WPKG user interface -> Show) - without it, you won't see >> any windows. >> >> Reboot, and when cmd.exe window starts, try to connect to that >> webserver and fetch that file using telnet, i.e. (start telnet, and >> type "GET /some_file.xml HTTP/1.0"): >> >> >> # telnet 192.168.10.1 80 >> Trying 192.168.10.1... >> Connected to router (192.168.10.1). >> Escape character is '^]'. >> GET /some_file.xml HTTP/1.0 >> >> HTTP/1.1 200 OK >> Date: Fri, 18 Jan 2008 15:22:47 GMT >> Server: Apache/2.2.3 (Debian) >> (...) >> > Entering "cmd.exe" as pre-command was an excellent hint, thanks for that > in advance. > results: the telnet command works and gets the packages via http. > unfortunately the cscript/wpkg.js combination did not work from the same > shell. (see attached screen capture) > i installed wireshark and even no packages were sent to http server when > executing cscript .... I got it:
there was a hidden deprecated proxy server set in the "LocalService" Profile. It seems that telnet is not affected by this setting but cscript does. I noticed that by running xpnetdiag.exe (KB914440) from the "LocalService" shell. Know the only remaining problem is to remove that entry from the LocalService profile on a whole bunch of workstations, but i think i will manage this. :-) Thanks for your support, Christian ------------------------------------------------------------------------- Do you use WPKG? Tell us how! >> http://wpkg.org/Testimonials _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users