Unsolved
This post is more than 5 years old
6 Posts
0
197132
wnos.ini - Cannot access system profile
wnos.ini - Cannot access system profile
There is already a similar thread, but the problem isnt solved and there are no usefull points of reference.
My environment:
2 W2K3 2003 DCs
1 W2K8 R2 RDS
1 T10 ThinClient with ThinOS
IIS7 is installed on the RDS Server, RDS server is a client server in the domain, this machine has two roles only: RDS and IIS (no DC).
I have created a new FTP site to allow the ThinClient to get the wnos.ini. The FTP site in IIS is created with default settings, I used as IP adress the local RDS IP (it is running the FTP role).
The FTP server seems to work fine - at least, it is w/o problems possible to access the wnos.ini from everywhere in the browser by opening ftp://10.10.10.10 and in the DOS box with the ftp command.
But the ThinClient can not find the wnos.ini, in the event log on the T10 ThinClient appear following lines:
Looking up IP adress from DHCP...
Contacting File Server...
Cannot access system profile
The option tag 161 on DHCP is configured too (Data type is not string, I took IP. Does it matter?)
So, what did I wrong, where is the mistake? Any help and hints would be cheerful.
P.S.
If connecting to the RDP server manually , it works pretty fine but in the event log appear following errors:
Connect to the host rds...
RDP: negotiate failure 2
RDP: x224 layer connect failure!
ERROR: Connection failed!
Connect to the host rds...
RDP: Decompression type is RDP 6.1 bulk
DimitriK-2015
6 Posts
0
June 25th, 2015 03:00
Thank for the hint, but I'm still receiving the "Cannot access system profile" - error. I changed the line to "Fileserver=10.10.131.5". The path is: C:\inetpub\ftproot\wyse\wnos\wnos.ini
DimitriK-2015
6 Posts
0
June 25th, 2015 03:00
Thanx for the answer, we had a big desaster in the firm and I couldnt answer soon. I didnt try it out yet, I'll tell if I did.
DimitriK-2015
6 Posts
0
June 25th, 2015 03:00
The problem is still persistent.
Cannot access system profile - Please help.
The FTP Server is working well, the path is correct. Whats wrong? Here the content of the wnos.ini:
;************************************************* ************
;* *
;* This wnos.ini file was generated with the *
;* Configuration File Generator 6.3.06 *
;* Copyright by Thomas Moellerbernd *
;* *
;* http://www.technicalhelp.de *
;* *
;************************************************* ************
;************************************************* ************
;* General 1 *
;************************************************* ************
autoload=0
Fileserver=10.10.131.5/wyse
Privilege=High
;************************************************* ************
;* Peripherals *
;************************************************* ************
Language=De
KeySequence=yes Ctrl+Alt+Up=no Ctrl+Alt+Down=no Ctrl+Alt+Left=no Ctrl+Alt+Right=no Ctrl+Alt+Del=yes
;************************************************* ************
;* Display *
;************************************************* ************
; If you are using a version of WTOS code < 7.0.1_13 please use:
; Resolution=1440x900 Refresh=
Screen=1 Resolution=1440x900
DesktopColorDepth=32
;************************************************* ************
;* Time *
;************************************************* ************
Timeserver=62.116.182.44 Timeformat="24-hour format" Dateformat=dd/mm/yyyy
TimeZone='GMT + 02:00' ManualOverride=yes
;************************************************* ************
;* Network *
;************************************************* ************
Device=Ethernet Speed="100M FD"
SignOn=No
;************************************************* ************
;* General Session *
;************************************************* ************
SessionConfig=ALL DisableSound=Yes
;************************************************* ************
;* RDP *
;************************************************* ************
SessionConfig=RDP DefaultColor=2 WallPaper=no
;-------------------------------------------------------------
;- RDP Session 1 -
;- Each line but the last must end with a '\' -
;-------------------------------------------------------------
CONNECT=RDP \
Host=10.10.131.5 \
Description="ELEARN RDS" \
Colors=32k \
Autoconnect=yes\
Autologin=yes\
Fullscreen=yes \
Resolution=1440x900 \
Username=rdsuser \
Password=password\
Domainname= \
Disablesound=Yes \
LocalCopy=no
DimitriK-2015
6 Posts
0
June 25th, 2015 03:00
No ideas what it may be?
Rmontalvo1
623 Posts
0
June 25th, 2015 03:00
What does your WNOS directory structure looks like?
The "Fileserver=" should not have the /wyse unless your directory looks like ftproot/wyse/wyse/WNOS
Roger Montalvo
Visit our Dell Wyse Thin Client Knowledge Base and Manuals web site at www.wyse.com/KB
Visit our Dell Wyse PocketCloud Knowledge Base and Manuals web site at http://pocketcloudsupport.wyse.com/forums
[SIGPIC][/SIGPIC]
Rmontalvo1
623 Posts
0
June 25th, 2015 03:00
Dimitrik,
The data type does matter. Go to www.wyse.com/manuals and search for "16132" (no quotes) for instructions.
Hope this helps.
Roger Montalvo
Visit our Dell Wyse Thin Client Knowledge Base and Manuals web site at www.wyse.com/KB
Visit our Dell Wyse PocketCloud Knowledge Base and Manuals web site at http://pocketcloudsupport.wyse.com/forums
[SIGPIC][/SIGPIC]
brgaulin
1 Message
0
June 25th, 2015 05:00
Something changed
I think something changed. I moved all my files to ftproot/WNOS/WNOS.ini and the folders in there. No Wyse folder. And everything works fine now. I was having the same issues as you stated
Correction: I was not using DHCP to set my FTP server. If you use DHCP option 161(as described in the manual) to "Push" the FTP server address to thin clients, it will add /wyse/ to the end. so ftproot/Wyse/WNOS/Inc/file.ini
In my config, our thin clients have two numbers at the beginning that identify physical location, so I do include = &Left($TN,2).ini which loads the file "/wyse/wnos/inc/05.ini"
Double check you have the correct file names, and check FTP logs to see
DimitriK-2015
6 Posts
0
June 25th, 2015 05:00
Really helpfull official forums here.