Windows server 2008: Discovering devices problems

I think that the problem come from the DHCP configuration.

I used Wireshark to snif the network when a wyse is trying to boot on PXE.

I took a screenshot of that:

Which option do i have to configure on the DHCP server ?

I’ve configured the option number 66 host name for boot server (192.168.0.3)

Do i have to configure the option number 67 boot file name ? And which name i have to give ?

There are others option to configure ?

thanks. 🙂

Ok, i configure the two option in the DHCP server

66: Host boot server name = 192.168.0.3
67: Boot file name = “rapport”

So now Wyse are booting with PXE.

Intel UNDI, PXE-2.0 (build 082)

For Realtek RTL8137(X)/8130:810X PCI Fast Ethernet Controller v2.13 (020326)



Client Mac addr: 0080645c811c

GUID: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF

Client IP: 192.168.0.11

Mask: 255.255.255.0

DHCP IP: 192.168.0.2

TFTP....

The Wyse can’t find a TFTP server and it is normal because i don’t have one. I use a FTP server.

Is SNMP necessary on 4.7.2 version ?

another thing: When i right click on “Device manager” and then click on “find device” i’ve got this message:

HTTP discovery attempt failed. unable to contact web service.

Are you sure that i don’t have to put option on the DHCP server ?

I’ve looked on this documentation: https://technicalhelp.de/products/1000/TG_Wyse%201xxx%20Serie_english.pdf

how the dhcp server can give the ip to the wyse if the dhcp didn’t know it ?

What does WTOS wyse means ?

@CG wrote:

As Windows 2008 is currently not fully supported I would highly (!!) recommend installing WDM on a 2003 server.

Oh ! 😯
Why Wyse don’t tell that ? We can’t see that anywhere.

I’ve tried on a 2003 server, and it is exactly the same problem.

@ConfGen wrote:

Your last message shows clearly that the webservice for WDM is not running. This explains perfectly why no clients can be found /could not check in.

I’ve tried on a 2003 server, and it is exactly the same problem too. 🙁
I’ve just installed the IIS services, with FTP. I can access from wyse to the http server with this url

http://192.168.0.3/test.html

(test.html = a page that i created myself)

So the HTTP server is working but i still have this message when i try to find device:

HTTP discovery attempt failed. unable to contact web service.

thanks 🙂

Hello alienjoker,

Thanks you for your answer 🙂

@alienjoker wrote:

Hey strax,

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.

I’ve tested that url on my DHCP server and on a Wyse XPe

On my DHCP server, the url is working and makes me download a file named “hserver”.

On a Wyse XPe, i have a web page error “404 File or folder not found”

@alienjoker wrote:

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

I’ve watched on the Wyse Xpe and the service is running.

But i’ve watched on my 2 WDM servers, and i have a service called Hserverinit which is not working. I have to launch it manually each boot.

After i’ve launched it, i start WDM and i have this message:

the problem seem to be on the server. This message appear on 2008 server and on 2003 server. So it is not a compatibility problem.

@Alienjoker wrote:

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.

Ok, i’ve deleted all the option on the DHCP server.
Now PXE is not working again.

See you.

@straxjam wrote:

@alienjoker wrote:

Hey strax,

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.

I’ve tested that url on my DHCP server and on a Wyse XPe

On my DHCP server, the url is working and makes me download a file named “hserver”.

On a Wyse XPe, i have a web page error “404 File or folder not found”

I’ve just tried it on the WDM server and i have a 404 error too.

http://img7.imageshack.us/img7/627/erreurhttp404.jpg

so there is no time stamp anywhere.. 🙁

I discovered the freewysemonkey’s Wyse Device Manager:
Quick Reference Troubleshooting Guide here: http://www.freewysemonkeys.com/downloads/WDM%20Quick%20Reference%20Troubleshooting%20Guide.pdf

I’m reading it at the moment, maybe i’m gonna find some issues.

@CG wrote:

Hserverinit is just an initialization service as the name indicates. So it is OK that it is not running. Starting it manually should leave it only for 2-5 seconds running.

Oh ok, thanks for the info 🙂

@CG wrote:

If it is running longer this indicats that there is a problem.
The HServer not running box proves that.

You’re all right. The service auto shutdown with a few minute delay.

@CG wrote:

Check if DEP is running and disable it if posible or at least permit IIS to run correctly.

Sorry, what is DEP ? I don’t find that in the service manager

@alienjoker wrote:

From the screen shot, it looks like you’re using the wrong URL.

yeah i made a mistake on the WDM server, i retry with the correct url and it is the same problem. 🙁

_____________

For the moment, i found on the WDM quick reference troubleshooting an option which suggest to install ISAPI filter, i’ve done it:

@Quick reference troubleshooting wrote:

7. Check for any ISAPI Filters loaded on Server
a. IIS Manager > Web Sites > ISAPI Filters
i. RapportFilter should be loaded
1. If missing add new Filter Named ‘RapportFilter’
a. C:inetpubwwwrootrapportfilter.dll
ii. No Other filters need to be loaded
b. IIS Manager > Web Sites > Rapport HTTP Server > ISAPI Filters
i. No Filters should be loaded under Rapport Site

I’ve also tried that:

@Quick reference troubleshooting wrote:

10. Is server member of AD?
a. Is AD overriding local IIS configuration?
b. Will HServer start outside of AD?

Same problem in local

@alienjoker wrote:

Random thought – do you have any proxy connection settings configured on your web browsers?

Thanks

No proxy, i detailled you all my network configuration in my first post.