Forum Replies Created
-
Posts
-
sorry to rehash the topic –
The solution “LoadPkg=0” did not change anything for me.
i.e. i can ignore this message and have to accept it when using 3010 devices, right?
Vielleicht schon selbst gefunden –
Reicht es die Einstellung unter “erweitert” “keine globale INI” zu aktivieren?
Perhaps already found myself –
Is it enough to activate the setting in “extended” “no global INI”?
Vergessen zu schreiben – es geht natürlich um THIN OS Geräte
Forgot to write – it’s about THIN OS devices, of course.
For your information, we log on to the FTP as anonymous.
what irritates me is that the updates works with the 3020 and 3040 and not with the T10.
Here is an excerpt from the log
Thanks for the answer,
when i change the settings in the WNOS.INI they arrive at the client (e.g. changes to the RDP session). So the WNOS.INI should be reached.
Is there no other way to update the clients, for example via USB?
Changes i make in the mac.ini for this client are accepted.
In the local Event Log there is not really any information:
….
07:45:10 Kontaktiere Datei-Server …
07:45:10 Rufe Systemprofil auf…
07:45:10 locale/German.msg: Keine solche(s) Datei oder Verzeichnis
07:45:10 Ungültiger SESSIONCONFIG Parameter: WyseVDA
07:45:10 Ungültiger VERBINDUNGS-Parameter: WyseVDA=no
07:45:11 Kontaktiere Datei-Server …
07:45:11 Kann das Systemprofil nicht aufrufen
07:45:11 Prüfe Software ftp:/wnos/DOVE_boot …
07:45:11 Prüfe Paket von ftp:/wnos/DOVE_boot …
07:45:12 Kontaktiere SNTP [de.pool.ntp.org] …
07:45:12 RDP: Start session to xxx.xxx.xxx.xxx
07:45:12 RDP: Connect to xxx.xxx.xxx.xxx …
07:45:12 RDP: NLA CredSSP Authentication
07:45:12 RDP: NLA CredSSP Authentication failed (1)
07:45:12 ERROR: Connection Failed!
….Thanks for the tip.
I will set this.
When i will test the WDS on one client:
can i set the command for this client to CCMEnable=YES in the INC/mac.ini?
So it should only work for this client, right? Then i can test it…
Short summary:
I didn’t get the access over FTP * but via HTTP.
I only had to find out the correct port and specify it –
then it worked 🙂
I hope it makes no difference between http and ftp
Thanks a lot
* Whatever the reason is…. I try it with the Explorer and any browser and I was able to Access and open the files…
** english text below **
Hallo ConfGen,
irgendetwas muss dann aber das Profil blockieren, da ich immer die Fehlermeldung “Can not Access User Profile” bekomme. Den Zugriff über Http habe ich auch schon probiert – dort ist das selbe.
Das NAS kann ich vom Wyse Client aus anpingen und bekomme auch eine “Antwort”.
Meine Testumgebung ist eine Fritzbox mit Zyxel NAS. Ich will jetzt noch das ganze mit statischen IPAdressen und ohne DHCP/Router ausprobieren – um diese als Fehlerquelle auszuschließen.
Aber vielleicht fällt Dir ja vorher noch was ein…
Gruß Markus
** english text **
Hi,
then something must block the profile – it always show the error message “Can not access system profile”. I have already tried http for access – same there.
When I ping the NAS from the client I get an answer.
I will now test the situation with static IP addresses and without DHCP and router – (only the NAS and one client).
But maybe someone has another idea?
Markus
