- This topic is empty.
-
Posts
-
Hi,
I have WDM 4.5.1 (enterprise…fully licensed for 60 terms) installed on a Win XP machine in my environment with a total of 55 9150SE Terminals (512mb version).
Im trying to push out a new image to all the devices but for some reason I cannot image more than 2 devices at a time.
I can schedule as many as I want (although I have funny feeling I wont be able to do more than 10 at a time thanks to the imposed limit on WinXP Pro and inbound TCP connections).
Anyway – all the devices start the imaging process – PXE boots fine, starts imaging process and then all but 2 will fail – saying “WISard Failure – Not found”.
Any Ideas?
Thanks
Paul
I should also mention that the TFTP log says- “READ ERROR From 192.168.20.34 2700 – Closed Session”
So….things got much worse then….
I decided I had better get on and install the hotfixes onto WDM.
After doing so I can now no longer access my device list and receive an error along the lines of
GetClients Failed – Not Found
DevMgrColumnListings
SQL OLEDB ProviderI have no idea whats happened – But Im now royally screwed – as I am only 6 devices into a 55 device redeployment.
Looks like I may need to reinstall WDM onto a new Server (a W2k3 OS for that matter as well).
Any thoughts on what the error is and how to fix it would be most appreciated – (although I realise that not too many people will be looking at this forum on a sunday!)
Cheers
Paul
Hi Paul,
try reinstalling the HF again. Looks there went something wrong during the install. To do this, you have to delete the reg value from HKLMSWRapportHFvalue. HFValue could look like this HF04051027707.
Cheers
CGThe original error you saw is a Windows XP issue. You are right about the 10 connection limit but WDM is using more than one connection for imaging devices at the same time to one device. That’s why you can only image 2 devices at the same time.
Installing it on a Windows 2003 server would raise this.
Using the free workgroup edition of WDM is limited to 5 simultaneous connections. Enterprise is 99 or more. Don’t know exactly.CG
Hi Confgen,
Thanks for you help
I gave up on the XP WDM box and have rebuilt onto a w2k3 box – I hadnt many packages in the repository of the old XP machine so I just started from scratch with 4.5.2
Hopefully things will go a little better now!
Thanks again
Paul
I’m running WDM 4.5.2 Workgroup on Win XP Pro SP2 and I have the same problem as pauladam. I can’t seem to image more than 2 devices at a time, unfortunately I don’t really have the option of upgrading XP to Windows Server so I’m kind of stuck. Does anyone know of a workaround or way to overcome this concurrent connection limit? I know someone has mentioned that even though XP supports 10 concurrent connections, that WDM uses more than 1 connection to image a device (how many does it use? 5 each device?). However, i don’t see any indication from XP that it’s hitting it’s maximum conncetion limit (e.g. event id 4226 or something like that). All the Wyse documentation that I read says that XP should in theory support 5 concurrent connections. I know that WDM workgroup is limited to 5 connections at a time which is all we need here. TIA 🙂
Hi imstarunit,
I would certainly agree that there is no indication of XP’s connection limit being reached.
Ive a couple of suggestions though – do you have a server that you can run FTP on (Win 2k, Win 2k3) – you could host your repository on there and configure WDM to use this remote repository….might be a way of getting round the connection limit.
or…
Completely unsupported of course and with the usual caveats of “if it breaks it then its not my fault!” – Have a look here
http://blog.davidkaspar.com/archives/2005/04/windows-xp-sp2-and-event-id-4226.phpLooks like they are mentioning a patch that can increase XP’s connection limit?!?!?
Hpe that helps – but….like I say – never tried it and no warranties!
Cheers
paul
Hi Pauladam,
Many thanks for your response 🙂
That’s a good suggestion (to use another server as the WDM remote
repository)…never thought of this and will definitely see if this is a possibility.As for the the tcpip.sys patch, I already tried this and it didn’t work. I’ve basically tried all the IIS/reg tweaks and patches I could find on the web to overcome the crippled XP IIS implementation with no luck. I continue to get the same READ FAILURE with the 3rd device that tries to connect to the web/ftp server to get it’s image. This is where most of my frustration stems from…I just don’t understand exactly what is causing this 2 concurrent connection limit (e.g. is it the number of FTP connections? total # of half-open connections? a PXE limitation? etc.). It doesn’t look like XP is hitting its connection limit since I never get an ID 4226 and the fact that the patch did not work.
I guess I would just like to get a definitive answer from Wyse that Windows XP only supports 2 concurrent connections. Their documentation suggests that it can support up to 10 – as per the connection limit for XP Pro (as this is what my company has bought into). However, the responses from other users has suggested that XP only supports 2 connections so there is conflicting info here.
Anyhow….thanks again for your suggestion – it’s most appreciated.
Imstarunit
Hi,
although the suggestion of pauladam to use remote repositories could help. it is not an option with WDM Workgroup Edition. Remote Software Repositories are only available within WDM Enterprise which is chargeable.
CG
Hi Folks,
Ahh, the Windows XP SP2 TCP/IP streams limit, don’t we love it! I mentioned this in this artical:
http://www.freewysemonkeys.com/site/modules.php?name=News&file=article&sid=32
But check this out to resolve the issue:
http://www.lvllord.de/?lang=en&url=tools&PHPSESSID=c6db9cb08ce8b6364c505e84c35a46d1
This is why you should use Windows Server to manage lots of devices,
Cheers,
-TTAppreciate everyone’s feedback…
Confgen – thanks for the tip about WDM Enterprise being required for remote repositories. I skimmed over some of the WDM admin guides to see if using an existing FTP server is a viable approach. So, does this mean that I need to install WDM Enterprise on the XP Pro machine
only? Or does the FTP server also require an installation of WDM Enterprise. It wasn’t clear from what I read in the documentation…sounds like i just need to install WDM Enterprise on the XP guy as the master repository and then have then configure a remote repository to point to an FTP server that it will have read/write access to. Then configure the clients to go against this FTP server to get its updates and hopefully i should be able overcome the 2 connection limit of XP?Thinkthin – thanks for your suggestions about hitting the stream/connection limit of XP. This is what i’ve been thinking all along myself but I can’t seem to find any evidence that this is the case. Like I mentioned, I have already tried the lvllord patch and this is has not made a difference here. Am I missing something here? I’d love to know whether anyone has successfully gotten XP to suport more than 2 concurrent connections??? Otherwise, if this is just impossible without a completely hacked (and unsupported) XP config then I may be just be wasting my time and should push my company to move to a server OS.
Thanks again for everyone’s input 🙂
Hi,
You are spot on with Enterprise, you install it on a server and the remote repository is any ftp server with the rapport/tools/sa directory and images. You can use any ftp service, windows, freeware, Linux – hey mount it on a USB stick and use one of the terminals as a ftp server!
As for the streams issue I am surprised this did not solve it. Check the event logs on the XP Pro machine as it will have a error telling you if its the streams issue or the in built 10 concurrent connection limit of XP Pro. Make sure you have no other services running on the box as these will use up connections. I have managed to push 5 concurrent images at a time from XP Pro with WDM,
Cheers,
-TTSounds like I’m definitely missing something then. The fact that you were able to image 5 at a time with XP Pro really surprises me…I wonder what is wrong with my setup? I’ve completely re-installed a few times…a fresh install of XP Pro with SP2, applied all MS critical patches and updates, then installed WDM (tried both 4.5.1 and 4.5.2 and WDM Enterprise as well) and nothing else on the box. Left everything more or less at the defaults…and the most I can image at a time is 2 devices. The 3rd device, boots into PXE, gets an IP, and then is always unable to connect to the HTTP/FTP server. It tries numerous times ‘searching for interface’ and getting a bunch of “READ FAILURE” and rebooting before actually giving up. There are no events in the events log that indicate im hitting a stream or connection limit. Is there something i need to tweak or adjust to ensure I can support more than 2 devices connecting?
- You must be logged in to reply to this topic.