- This topic is empty.
-
AuthorPosts
-
February 10, 2009 at 9:00 pm #1861
I am new to thin clients. I have set up a S10’s so that they would use our existing PN Agent site. I am unable to understand why it is not able to read the wnos.ini file. Any help would be greatly appreciated. Thanks in advance.
1: System Version: 6.1.0_08f (ROM: 1.14i)
2: Access protocol: FTP, username: wysewnos
3: CPU Version: AMD Geode (TM) GX 500
4: Checking Ethernet Link …
5: Checking Keyboard and Mouse …
6: Ethernet device version: RTL-8100B/8139D.
7: USB: Found a new device “HID” on port 2
8: USB: Found a new device “HID” on port 2
9: Looking up IP address from DHCP …
10: Checking security key …
11: Built-in certificate BTCTRoot.crt is installed
12: Built-in certificate Class3PCA_G2_v2.crt is installed
13: Built-in certificate Class4PCA_G2_v2.crt is installed
14: Built-in certificate GTECTGlobalRoot.crt is installed
15: Built-in certificate GTECTRoot.crt is installed
16: Built-in certificate Pc32ss_v4.crt is installed
17: Built-in certificate SecureServer.crt is installed
18: Built-in certificate EquafaxCA1.crt is installed
19: flash1:/cacerts: No such file or directory
20: Contacting SNTP [xxx.xxx.1.1] …
21: Contacting File Server …
22: DNS/WINS can’t resolve [wyseftpfbc4tc]
23: Cannot access system profile
24: Checking Software ftp:/wnos/RCA_wnos …February 11, 2009 at 6:58 am #15129Hi and welcome,
where have you stored your wnos.ini and what have you entered in the network configuration as your “fileserver”?
Read my “First Steps” doc from my website. This will help you.CG
February 12, 2009 at 9:52 pm #15144I have created a folder structure ‘F:thin_os_ftpwysewnos’ on one fo my server on which FTP publishing service is running. Also in IIS i have created a FTP site pointed the local path of the FTP site directory to ‘F:thin_os_ftp’ and have given the ‘Read’ access, allowed anonymous connections.
In the Network Setup of the Blazer File Servers/Path: ‘IP Address/wnos’
Do let me know if i am missing anything.February 12, 2009 at 11:08 pm #15145The fileserver entry should be IP/wyse
CG
February 17, 2009 at 1:59 pm #15190Thank you it worked but I have another S10 unit which is locked down and the event log says as follows…
22: Contacting authentication server …
23: Signon server (https://server1.domain.local) is not responding.
24: Contacting File Server …server1 is the server address entered under the VDI Brokers: on the S10
and it is shut down.February 17, 2009 at 2:45 pm #15193Don’t care about a missing authentication server. This is normally any Connection Broker.
Care about the possibly wrong entry under Fileserver.
Does line 25 in the eventlog say “Cannot access system profile”?
Try to find out the IP address of the entered fileserver (eg. sniffing) and build a FTP server with that IP.CG
February 17, 2009 at 5:02 pm #15200Is there any way to find the IP address as I have no idea of the details entered in for the file server.
thanks.
February 17, 2009 at 9:32 pm #15203You can use MS Netmon to sniff the network traffic. There you can see which IP the client is looking for.
CG
-
AuthorPosts
- You must be logged in to reply to this topic.