- This topic is empty.
11. March 2008 at 14:22 #1017
I have a scenario developed here which results in failure of WTOS start up.
The problem occurs when I restart the two Wyse V10L devices at same time. Some times they successfully, but more often one of the devices or even both of them hangs on â€œContacting Authentication Serverâ€ for some time and does not load the wnos.ini file from ftp server successfully. I mean thet report failed to connect to Authentication Server and does not start successfully.
Also these devices startup successfully if I start them one after another. But not simultaneously.
WTOS version is 6.0
Can any one explain what is the problem?
🙁11. March 2008 at 19:26 #12104
can you post your wnos.ini file?
CG12. March 2008 at 6:28 #12125
Here is wnos.ini file
signon = 1 EnableOK = yes
autoload = 0
DomainList = (Local)
DefaultUser = Administrator
VDIBroker = http://192.168.77.248:9906/test/UPMJsp12. March 2008 at 7:34 #12126
Thanks for the confgen utility suggestion. I have generated the wnos.ini file from confgen utility. I am facing the same problem and mentioned in the first reply. No problem resolved!!12. March 2008 at 9:48 #12128
What is the exact version of code? You may need more recent as there were a number of changes with WTOS and the VDM2 during development.
-TT12. March 2008 at 10:09 #12129
one device has WTOS version is 6.0.0_14 and another has WTOS version is 6.0.1_04 and VDM i am using is just a compiled servlet running on tomcat sever by me?12. March 2008 at 10:16 #12130
OK, so the authentication server http://192.168.77.248:9906/test/UPMJsp is a application you have constructed? Its not a commercial connection broker?12. March 2008 at 13:02 #12135
yes its true its just a simple servlet just for testing purposes, actual case i will be using some other connection broker software, but today i tested the same scenario with out setting the the VDI broker field and it resulted in the same error as is mentioned in the first reply. In addition to that I also got the other error which states:
HAgent Open “” failed
when both the devices are restarted at the same time
can any one tell me what is the problem?12. March 2008 at 13:30 #12137
Don’t worry about the Hserver open – that just means there was no WDM server available.
I really think this is one you will have to tackle yourself, basically you have written your own connection broker and are trying to debug it. To do this fully you would also need at API’s that WTOS uses.
I can say that I have used a number of commercial connection brokers and they function fine so I would suggest you give one of these a try and I believe you will not see the same issue.
Hey, nice work on building the web app and getting it to even run on one device!
-TT12. March 2008 at 14:16 #12141
But I and not interested in setting the WDM property and nither i had set it why does it report so. Any how just keep a side the VDI broker field for now i am setting it to nothing i.e no VDI broker. Still i am having problems in getting the wnos.ini file from the ftp server when both the devices are restarted at the same time.13. March 2008 at 1:55 #12143
Hmm, that’s very strange. So you can not get the wnos.ini if more than one unit at a time? What FTP server are you using and are you accessing by anonymous? Maybe there is an account restriction on the ftp server?
-TT13. March 2008 at 5:25 #12155
I am using FTP server provided buy IIS that comes with windows. I am not accessing with anonymous account but with Administrators account. Also ftp server is configured to accept 10 connections at one time.13. March 2008 at 17:21 #12165
Can you try with anonymous to see if it is an authentication issue?
CG13. March 2008 at 19:13 #12166
hmm nice idea it worked actually. thanks alot.
But can u tell me why is ftp username and password not working properly. Also i found that it worked actually after i restarted the devices say about 4-5 mins but not immediately after the startup. (make explicit to the anonymous user) this senario dose not occur with the anonymous user.13. March 2008 at 19:48 #12167
No idea, maybe a network trace would show something.
- You must be logged in to reply to this topic.