Forum Replies Created
-
Posts
-
Hi ConfGen,
The current WDM server is at the production site . Therefore if I needed to initiate DR it means that the WDM server will be unavailable.
As I can’t control the DHCP Scope Options, if I built a new WDM at the DR site, I wouldn’t have any control over the already deployed clients – unless I manually added them all? This isn’t a problem for S90s as they access the connection broker via a web interface and use DNS which is easily updated. The problem is purely with the S10s as they’ll still hold the EnableLocal option thus looking for the old FTP server.
I suppose what I could do (if it allows it) is to configure the initial WTOS.ini at the production site to use a live and a DR DNS server . Then if I specify the WDM FTP server by DNS name in the WNOS.ini file and EnableLocal, it would then redirect to the new WDM server. Will try it now and see what happens.
Thanks
Thanks
Glad you got there in the end.
Please post back whether you have any success with Windows 2008. I may setup a lab to test the platform as well.
Keep you posted.
Ok, we’ll need break down what you have configured in your IIS deployment
If we stick with what we know works (Windows 2003), you’ve installed configured IIS on this server and subsequently installed WDM.
Once you’ve done this, you’ve updated the WDM Applet from control panel on the XPe thin client to the IP address of the Windows 2003 IIS server (with the IP and port of 80)
The directory security on the Rapport web site thats automatically added needs to have Anonymous Access enabled (Right click Rapport HTTP Server –> Properties –> Directory Security –> Edit –> Enable anonymous access).
The other boxes on that page should remain blank.
Also, the server hosting IIS under W2k3 is only advertising one website on Port 80.
Do you receive an Under Construction page if you browse to the IP address of your WDM server – it looks like the basic IIS side of things is working given the success of your test.htm you tried.
Random thought – do you have any proxy connection settings configured on your web browsers?
Thanks
Hi Strax,
From the screen shot, it looks like you’re using the wrong URL.
Your screen shot suggests
http://192.168.0.3:80/hserver.dll&V99
It should be
http://192.168.0.3:80/hserver.dll?&V99
You’re missing the ?
Thanks
Hey strax,
You definitely don’t need the DHCP scope options. The document and image you are referring to relates to Wyse Thin Clients running WTOS not XPe.
To check to see if your WDM server is running properly, please type browse to:-
http://ipofyourwdmserver/hserver.dll?&V99
If you receive a time stamp back in the form of:-
2009|6|14|19|14|36|60|
Your WDM server is up and running fine.
Next thing to check is that the Hagent service is actually running on the Wyse XPe. As administrator, open up Services (services.msc) and look to see if the service is started/enabled. If not, start it and this should resolve your issues!
Thanks
