- This topic is empty.
-
Posts
-
ThinkThin,
The test connection was sucessfull.
The location was set to a FQDN so i changed this back to the IP address of the rapport server. I have just pushed a new config to the machine to test but am not at the office so am working blind. I will advise as soon as it comes back with anything.
The user password was set to never expire as per yet another great tip from this website – Keep up the good work ThinkThin!
Many Thanks,
DarronThinkthin,
Well done, you found the cause of the problem! 😀
It seems that the PXE imaging boot process cannot handle FQDN to download their images! Once changed to the physical IP address of the server it worked!.
Once again thankyou Thinkthin for your help and keep up the good work – it is a fantastic source of information!
Kindest Regards
DarronThat’s awesome news Darron!
It had us going there for a while, thanks for supporting the site!
😀
- Total Post: 161
- Jacked into The Matrix
- ★★★★★★
I had the same problem with it searching for http. Turned out my ip in there was set to the ipaddress that the box had when first installed and not the current ip. After fixing this my problems cleared up. Thanks
Hi Gang,
I am having the same problem mentioned in this post. I have set up a test environment with 1 x wyse 941, 1 dhcp server hub and my test rapport server which is running windows 2000 pro. everything can see each other and i ran the rapport diagnostics check and everything either connected successfully or passed.
I can also manage the device by shutting down etc..
I want to try and stop the open failure rubbish coming up when i either try to Push an image to the device or pull the image to the device
Please advise
Barrie
Hi,
As per the posts here have you ran the test on the software repository and checked it has the correct IP? Also any errors in the event log relating to the hserver?
-TT
the repository ip address is setup correctly. I ran the Rapport Diag and everything passed (no failures) there is nothing in event viewer which relates to rapport or hserver
I’m getting the same error here. I’ve been through this thread and have tried everything suggested so far with no luck. Anyone else find a way to fix this?
You may want to start a new thread guys as posting on the end of this one its getting a bit cumbersome,
Cheers,
-TTI got some instructions on how to resolve this from Wyse. If they work I’ll share here…
I was able to resolve this by getting a new tools directory from Wyse (/ftproot/rapport/tools) and rebuilding the directory with the new contents. If you are having similar problems I suggest trying this yourself.
Hi everyone, i’ve only just joined up and i found the answer nearly straight away!!
I’ve been using Wyse devices with Rapport since 2002, and never had any major problems, until the recent install of WDM 4.5.1 onto a new server 2003 box. My first attempt at taking an image failed with the dreaded OPEN failure. I used some of the suggestions in this thread, and the change from FQDN to IP address has done the trick.
Hopefully this thread has, and will help others to sort this problem!! Thanks to thinkthin and other contributors
- You must be logged in to reply to this topic.