Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WPKG GP not syncronizing at startup on laptop when undocked. #86

Open
GoogleCodeExporter opened this issue Apr 4, 2015 · 7 comments
Open

Comments

@GoogleCodeExporter
Copy link

Installed WPKG GP 0.15 on several test machines (workstations, VM & two 
laptops).

OS on all machines = Win 7 Enterprise x64

Have test package installing fine on all but one machine.

The machine in question is a HP 8650W laptop.

Running 'WpkgPipeClient Execute' successfully installs test package.
Running 'Wpkg-GP-Test' successfully installs test package.
Attaching Laptop to Docking station allows WPKG GP to run on startup.

Have tried:
1. Uninstalling/Reinstall wpkg gp & installing via silent install & manual 
install.
2. Uninstall/Reinstall with removing wpgk.xml from System32 dir.
3. Disabling DHCP media sense.
4. Enabling 'Always Wait for network...' local group policy.

None of the above resolve the issue when undocked.

Attached log file with verbosity = 3.

Original issue reported on code.google.com by [email protected] on 13 Mar 2012 at 7:50

Attachments:

@GoogleCodeExporter
Copy link
Author

I've exactly the same problems. WPKG-GP 0.15 runs fine on 20 machines but one.

My WPKGServie.log stops only on that machine at the same line as Jeremys do 
(see previous post from Jeremy)!

all machines:
- are stationary desktops and no laptops
- are on XP pro (x86) sp3
- from the same manufactor and the same type
- with 1GBit LAN - no WLAN

Network:
- no AD is used but a samba pdc
- the wpkg networkshare is not public and is restricted for an user called 
"wpkg"


"Running 'WpkgPipeClient Execute' successfully installs test package.
 Running 'Wpkg-GP-Test' successfully installs test package."

I've done the above tests, too. All is fine. I've also tried uninstall / 
install etc.

I've tried also some tests from here: 
http://support.microsoft.com/kb/313222/en-us (with no luck)

Original comment by [email protected] on 16 Mar 2012 at 11:19

Attachments:

@GoogleCodeExporter
Copy link
Author

The first issue would indicate networking issues. What kind of network card do 
you have in the HP?

And for the second issue, I would start to guess at the same. What kind of 
network card do you have?

Original comment by [email protected] on 29 Mar 2012 at 11:47

@GoogleCodeExporter
Copy link
Author

It's a onboard NForce Ethernet Controller. The Mainboard is an Asus A8N-VM CSN.

Name    [00000009] NVIDIA nForce 10/100/1000 Mbps Ethernet
Adaptertyp  Ethernet 802.3
Produkttyp  NVIDIA nForce 10/100/1000 Mbps Ethernet
Installed   Yes
PNP-Device  {1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0269\4&132FE135&1&00
Last ...    30.03.2012 06:31
Index   9
Servicename NVENETFD
Driver  c:\windows\system32\drivers\nvenetfd.sys (1.00.02.06789, 53,50 KB 
(54.784 Bytes), 01.08.2008 10:36)

Original comment by [email protected] on 30 Mar 2012 at 10:38

@GoogleCodeExporter
Copy link
Author

Hi, could you try to some newer drivers for the NIC? My guess would be that the 
NIC reports it's up at startup, yet it isn't.

Maybe a firmware update would help as well?

Original comment by [email protected] on 4 Apr 2012 at 2:14

@GoogleCodeExporter
Copy link
Author

Sorry for the delay in responding concerning the HP.

The NIC is a Intel 82579LM card.

It appears that HP has a driver version that came out in Feb, and Intel has a 
newer version released in March.

I'll try both to see if either make any difference.

Original comment by [email protected] on 5 Apr 2012 at 1:07

@GoogleCodeExporter
Copy link
Author

Updated drivers per previous comment on the HP 8660W and still no luck.

Again, just to re-iterate, WPGK-GP runs correctly on reboot when the laptop is 
docked, but does not when un-docked (which seems odd to me).

Suggestions?

Original comment by [email protected] on 5 Apr 2012 at 3:02

@GoogleCodeExporter
Copy link
Author

Implemented "Startup policy processing wait time" set to 30 seconds seems to be 
helping resolve this issue. I can now move forward to broader testing and 
report if this is fully resolved or not.

Original comment by [email protected] on 11 Sep 2012 at 5:23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant