Thin Client and Virtual Machines Thread, Upgrade to WDS now thinstation reports errors in Technical; We recently upgraded to WDS on one of our domain controllers, which also is the same DC that our thin ...
7th November 2007, 09:55 AM #1
Upgrade to WDS now thinstation reports errors
We recently upgraded to WDS on one of our domain controllers, which also is the same DC that our thin clients get the bootfile from. WDS and thinstation all appear to be running together fine, but whenever a thinstation boots an error is reported in the DCs event viewer:
Event Type: Error
Event Source: BINLSVC
Event Category: BINLSVC
Event ID: 522
An error occurred in the Active Directory Connection Manager while querying a Global Catalog server. Verify that a Global Catalog server is available on the network.
Error Information: 0x2AF9
The Global Catalog server is setup just fine. I think that it is something to do with thinstation looking for the binlsvc service when it boots, but this service no longer exists.
Anybody have any clues about this? It doesn't seem to actually be affecting anything, but I'd certainly like to get rid of the errors from my event viewer if possible.
5th December 2007, 12:40 PM #2
Re: Upgrade to WDS now thinstation reports errors
28th January 2008, 01:03 PM #3
OK, I'm going to try and move the thinstation files to another server to try and get rid of this problem.
How do I go about doing this?
28th January 2008, 02:24 PM #4
You would need to move the TFTP server (assuming you aren't using the MS one) and also change the options in DHCP to point to the new location.
I too had this problem, however it luckily coincided with the last of my thinstation clients being replaced by HP terminals.
Thanks to Ric_ from:
Andi (14th February 2008)
31st January 2008, 12:10 PM #5
I'm also seeing this error did you find a solution?
I'm sure it started after i installed Specops GPupdate but i could be wrong.
14th February 2008, 12:53 PM #6
Kind of sorted, kind of not.
I did as Ric suggested and setup a TFTP server on a different machine and pointed the stations to that using the DHCP options 66 & 67. My thinclients now boot up no problem.
My new related problem is that I'm not entirely sure that I'm going to be able to boot to WDS for rebuilding my fat clients.
All of my workstations on the entire network are in the same DHCP scope and we have no vlans setup to separate them, so I can't set separate options for fat vs thin clients.
By lee_sri in forum Thin Client and Virtual Machines
Last Post: 28th October 2010, 09:01 AM
Last Post: 30th July 2008, 01:48 PM
By tosca925 in forum Windows
Last Post: 2nd July 2007, 04:27 PM
By ICTNUT in forum Thin Client and Virtual Machines
Last Post: 9th May 2007, 03:33 PM
By Ric_ in forum Thin Client and Virtual Machines
Last Post: 26th May 2006, 11:53 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)