thin OS V10L cant connect to New Win 2008 Terminalserver

  • This topic is empty.
Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #5837
    RobDust
    Member
    • Total Post: 9
    • Regular Joe
    • β˜…β˜…

    Hello to all,
    I am new here πŸ™‚

    I Have set up successfully a new Windows 2008 R2 TerminalServer (remotedesktop Server) I can connect successfully remote into it, with our Windows 2003 Server and 2Windows XP Workstations. We have 20 per Device License. 3 are assigned to the obove named pcs. 17 empty.

    The Problem is. we have 10 Wyse Thin OS V10L Clients. No one of this can remote connect to the Server. The Screen Flashes quick and i am back at the Wyse start screen.

    Can someone help me fast with this issue?
    The V10L are from the year 08 and never updated, they were alle connected in the end with a Windows 2000 Terminalserver.
    I have reseted them to factory defaults, but it wanΒ΄t help.

    greetings Rob

    #18158
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • β˜…β˜…β˜…β˜…β˜…β˜…β˜…

    Put FixLicense=clean in your wnos.ini and reboot all clients once. Then you can remove it again.

    CG

    #18160
    RobDust
    Member
    • Total Post: 9
    • Regular Joe
    • β˜…β˜…

    Could you give me please a detailed Description how i Set FixLicense=clean
    what do you mean with, remove it again?

    At First i thought it can Be a problem with old Firmware … Couse i Never Update the thin Clients. Remote Desktop 6.1 problem or something…

    #18163
    RobDust
    Member
    • Total Post: 9
    • Regular Joe
    • β˜…β˜…

    Hey.
    ok I think that I know now what a wnos.ini is and how to download it on my client.
    you said i have to Put FixLicense=clean in my wnos.ini.

    is it ok, when i only put this line:
    FixLicense=clean
    and nothing more in my ini file?
    can the ini file consist of single row?

    greetings Rob

    #18165
    RobDust
    Member
    • Total Post: 9
    • Regular Joe
    • β˜…β˜…

    Hello.
    I have uploaded a wnos.ini file on my ftp://firmdomain/wyse/wnos
    then i tested from a local pc the connection and user and password succesfully.

    on the V10L Client i gave under the NetworkSetup Server Path
    the informations from above. Restarted, and nothing happen.
    Timout error as before.

    Firmware is 6.3.0_22
    perhaps someone could give me the newest Firmware?

    #18166
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • β˜…β˜…β˜…β˜…β˜…β˜…β˜…

    If you are currently not using a wnos.ini at all you can simply create one with two lines:
    FixLicense=clean
    Signon=no

    Then reboot the clients to read the wnos.ini. This will hide your locally created RDP connections but they com back if you remove the wnos.ini. I would recommend to stay with the wnos.ini and its centralized administration. Use my ConfGen tool to create one for your needs.

    CG

    #18169
    RobDust
    Member
    • Total Post: 9
    • Regular Joe
    • β˜…β˜…

    I see no where my Problem is…
    The wnos.ini file on my FTP Server is not recognized,
    couse i get the error:

    Line 17: DNS/WINS Can’t resolve [wyseftpfbc4tc]
    Line 18: Cannot acce3ss system profile

    My FTP Server is a Windows XP FileZilla FTP Server
    I can connect from other machines with WS_FTP Client without Problems!

    but the Wyse Client cant!

    The connection String is: 192.168.99.219/wyse
    the ini is in 192.168.99.219/wyse/wnos/wnos.ini
    Under DNS Servers i put my Router (The Router is our DHCP Server) in:
    192.168.99.1
    This configuration is the same like in the Windows XP PC, there it works,
    in the V10L not…
    Why get the error above?

    ps: can someone help me in german language perhaps? It will be more easy for me πŸ™‚

    #18172
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • β˜…β˜…β˜…β˜…β˜…β˜…β˜…

    Can you try a Windows FTP server? If your are using Windows XP you can use the integrated IIS for free.

    CG

    #18177
    RobDust
    Member
    • Total Post: 9
    • Regular Joe
    • β˜…β˜…

    Hi,
    I have set up the IIS integrated under my XP PC.Opended port 21 on firewall and tested succesfully the connection from other Windows Xp PC using smart FTP and it works great!!!
    C:inetpubftprootWysewnos is the path.

    Now i get the error:

    Line 16: FTP :Cannot open data socket. likely by Firewall
    line 17: FTP: data socket: connection timed out.
    Line 17: DNS/WINS Can’t resolve [wyseftpfbc4tc]
    Line 19: Cannot acce3ss system profile

    What the hell is messed up with the Clients??? I have before resetet to factory defaults…

    There is no firewall eror.. other Clients from windows xp can connect!!!

    File Server/Path: 192.168.219/wyse
    username anonymous
    Name Server 192.168.99.1
    under General is set DHCP.
    i get an IP couse i can ping and connect to my old w2k Terminal.

    #18178
    RobDust
    Member
    • Total Post: 9
    • Regular Joe
    • β˜…β˜…

    ok i deactivated my firewall complete…
    now i thin that it works… i see now in the log:

    Accessing system profile
    clear TS/CALS saved in NVRAM

    yeeeeeeha and i can connect to my Windows 2008 Server!!!!!!!!!!!!!!! great job CG πŸ™‚ , but only 1 time!
    then i have to reboot my V10L client. and the Rdp is away

    #18179
    RobDust
    Member
    • Total Post: 9
    • Regular Joe
    • β˜…β˜…

    could you give me please the newest firmware?`this would solve my problem too.

    #18180
    RobDust
    Member
    • Total Post: 9
    • Regular Joe
    • β˜…β˜…

    ohman… dont know what i have done… resetet all
    File Server/Path: 192.168.219/wyse
    username anonymous
    Name Server 192.168.99.1
    under General is set DHCP.
    put in this and i get the same error…

    Line 17: DNS/WINS Can’t resolve [wyseftpfbc4tc]
    Line 18: Cannot acce3ss system profile

    what is happen???
    connection from other pc is ok.

    #18182
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • β˜…β˜…β˜…β˜…β˜…β˜…β˜…

    Check the FTP log on your FTP server to see which path and file WTOS tries to access (system32logfilesFTP)

    CG

Viewing 13 posts - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.