Reply With QuoteI would cross post this in the main SoB forum too, the guy who wrote SBQueue answers on there I think. You can probably find him and PM him too easily enough.
Good Luck, holler if you need me to track him down.
Bok
Right SBQueue up and running, localhost connects fine and collects work. Another host installed, configured to use the proxy on the SBQueue server (IP or Hostname) - attempts to connect then fails... on sbqueue log I see the client connect, then i get "Stream Read Error" and it retries. Stuck as Google isnt helping me
I would cross post this in the main SoB forum too, the guy who wrote SBQueue answers on there I think. You can probably find him and PM him too easily enough.
Good Luck, holler if you need me to track him down.
Bok
Incase anyone else runs into this same problem, i thought i would post the fix. The SBQueue app requires that it can resolve the connecting client via DNS, if it cannot you get the error above. I am using a test bed based on NT4 DC's which only has WINS servers, there is no DNS and so resolved the issues on the SBQueue host by populating the hosts file with the connecting client details.
BTW, where did my post in the official SOB forum go - can't find it ?!!?
Finally, Bok you are right, the Xeon 3.4 Dualie with HT enabled really does eat through the blocks
Cool, glad it got sorted..
nice on the xeons, look forward to the dumps!!
Thread is there...
[ur]http://www.free-dc.org/forum/showthread.php?t=11530[/url]
Bok
so now you have some borgage bang goes my ideas ofyou anytime soon.
Drat and double drat.
If the hosts you want to monitor aren't in DNS.
On the box running SBqueue
edit /windows/system32/drivers/etc/hosts
Add names and IP's for the monitored boxes.
PCZ, that is what I said, maybe not quite so clearly
"populating the hosts file with the connecting client details. "
Posting Permissions