- Total Post: 1
I too am getting this error on a remote site. They have a good network connection and they are configured the same as the one at my desk yet theirs will not check into the wdm or load the ini. They get that damn error. Also have added the alias to dns but still no luck. We are having issues with v10le WTOS ver. 7.1_122 connecting to our file server/wyse. A new thin client would not work. Then an existing working thin client lost connection, got rebooted and now that one won’t work either. About to get the shotgun out and put them on the thrower.
ct335i: If you haven’t tried yet, in your file server/path, drop the http:// so it should only be 10.26.168.35/wyse. Also delete the username and password and hit ok then reboot. That is how mine are setup. Ip’s differ of course