Upgrading V50L to newer OS issues

  • This topic is empty.
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #5417
    p0opap0o
    Member
    • Total Post: 37
    • Frequent Flyer
    • ★★★

    I am trying to upgrade the os on all our V50L’s from version 6.4 build 19 to 6.6.1. I added wy_sc_6.6.1-03.64m to c:Inetpubftprootwysewlx and rebooted my terminal. When the V50L boots up it sees the new os and start booting up the config. It reaches a point where on the screen it says:
    Reading ftp://IP Address/wyse/wlx/wy_sc_6.6.1-03.64m to memory……..
    It just sits there and never finishes the upgrade.

    Any thoughts on what could be happening to cause this issue?
    Thank you,

    -Ari

    #16818
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Which FTP server are you using?

    CG

    #16819
    p0opap0o
    Member
    • Total Post: 37
    • Frequent Flyer
    • ★★★

    Its a ftp server on my network using IIS.
    Thank you,
    -Ari

    #16820
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Again, what Server OS? I saw issue with XP but never with à real server OS

    CG

    #16822
    p0opap0o
    Member
    • Total Post: 37
    • Frequent Flyer
    • ★★★

    Sorry about that.
    I’m running windows server 2003 R2 Standard Edition with service pack 2.

    Not sure if this helps but when i try and push a packaged image from WDM it reboots the wyse terminal to install the image but then the wyse just boots back up into the previous os like nothing happened.
    Thank you,
    -Ari

    #16839
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Can you verify the FTP server logs? Are there any error in the log?

    CG

    #16860
    p0opap0o
    Member
    • Total Post: 37
    • Frequent Flyer
    • ★★★

    #Software: Microsoft Internet Information Services 6.0
    #Version: 1.0
    #Date: 2009-11-02 15:30:31
    #Fields: date time c-ip cs-method cs-uri-stem sc-status sc-win32-status sc-bytes cs-bytes
    2009-11-02 15:30:31 172.16.35.106 [771]USER anonymous 331 0 0 0
    2009-11-02 15:30:31 172.16.35.106 [771]PASS [email protected] 230 0 0 0
    2009-11-02 15:30:31 172.16.35.106 [771]sent /wyse/wlx/00806470CC45.ini 550 2 0 0
    2009-11-02 15:30:31 172.16.35.106 [772]USER anonymous 331 0 0 0
    2009-11-02 15:30:31 172.16.35.106 [772]PASS [email protected] 230 0 0 0
    2009-11-02 15:30:31 172.16.35.106 [772]sent /wyse/wlx/wlx.ini 226 0 2632 0
    2009-11-02 15:30:31 172.16.35.106 [772]QUIT – 226 0 0 0
    2009-11-02 15:30:34 172.16.35.106 [773]USER anonymous 331 0 0 0
    2009-11-02 15:30:34 172.16.35.106 [773]PASS [email protected] 230 0 0 0
    2009-11-02 15:30:34 172.16.35.106 [773]CWD wyse/wlx 250 0 0 0
    2009-11-02 15:30:34 172.16.35.106 [773]QUIT – 226 0 0 0
    2009-11-02 15:30:34 172.16.35.106 [774]USER anonymous 331 0 0 0
    2009-11-02 15:30:34 172.16.35.106 [774]PASS [email protected] 230 0 0 0
    2009-11-02 15:30:34 172.16.35.106 [774]CWD wyse/wlx/addons 250 0 0 0
    2009-11-02 15:30:34 172.16.35.106 [774]QUIT – 226 0 0 0
    2009-11-02 15:31:03 172.16.35.106 [775]USER anonymous 331 0 0 0
    2009-11-02 15:31:03 172.16.35.106 [775]PASS [email protected] 230 0 0 0
    2009-11-02 15:31:26 172.16.35.106 [775]sent /wyse/wlx/wy_sc_6.6.2-02.64m 426 121 13172736 0
    2009-11-02 15:34:29 172.16.35.106 [776]USER anonymous 331 0 0 0
    2009-11-02 15:34:29 172.16.35.106 [776]PASS [email protected] 230 0 0 0
    2009-11-02 15:34:29 172.16.35.106 [776]sent /wyse/wlx/wy_sc_6.6.2-02.64m 550 2 0 0
    2009-11-02 15:34:36 172.16.35.106 [775]closed – 421 121 0 0
    2009-11-02 15:35:00 172.16.35.106 [777]USER anonymous 331 0 0 0
    2009-11-02 15:35:00 172.16.35.106 [777]PASS [email protected] 230 0 0 0
    2009-11-02 15:35:00 172.16.35.106 [777]sent /wyse/wlx/00806470CC45.ini 550 2 0 0
    2009-11-02 15:35:00 172.16.35.106 [778]USER anonymous 331 0 0 0
    2009-11-02 15:35:00 172.16.35.106 [778]PASS [email protected] 230 0 0 0
    2009-11-02 15:35:00 172.16.35.106 [778]sent /wyse/wlx/wlx.ini 226 0 2632 0
    2009-11-02 15:35:00 172.16.35.106 [778]QUIT – 226 0 0 0
    2009-11-02 15:35:02 172.16.35.106 [779]USER anonymous 331 0 0 0
    2009-11-02 15:35:02 172.16.35.106 [779]PASS [email protected] 230 0 0 0
    2009-11-02 15:35:02 172.16.35.106 [779]CWD wyse/wlx 250 0 0 0
    2009-11-02 15:35:02 172.16.35.106 [779]QUIT – 226 0 0 0
    2009-11-02 15:35:02 172.16.35.106 [780]USER anonymous 331 0 0 0
    2009-11-02 15:35:02 172.16.35.106 [780]PASS [email protected] 230 0 0 0
    2009-11-02 15:35:02 172.16.35.106 [780]CWD wyse/wlx/addons 250 0 0 0
    2009-11-02 15:35:02 172.16.35.106 [780]QUIT – 226 0 0 0

    The only thing that I notice is the time is wrong on the logs. Its showing that my wyse terminal connected at 15:30 EST but its only 10:30 EST. Both the ftp server and the wyse terminal are showing the correct time of 10:30.
    What do you think?
    Thank you,
    -Ari

    #16862
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Don’t mind the time.

    But if you look here:

    2009-11-02 15:34:29 172.16.35.106 [776]sent /wyse/wlx/wy_sc_6.6.2-02.64m 550 2 0 0

    you can see that the access to the firmware file was denied. This could be seen by the error code “550” behind the filename.
    Check NTFS rights to that file.

    CG

    #16868
    p0opap0o
    Member
    • Total Post: 37
    • Frequent Flyer
    • ★★★

    Confgen,
    The file had only read execute rights so I gave anonymous users full control to that file. When I started the wyse terminal it worked perfectly and upgraded to the new os.
    The issue now is when I plugged in a new wyse to upgrade it I get error 426 in the log file:
    2009-11-02 16:51:08 172.16.35.109 [798]USER anonymous 331 0 0 0
    2009-11-02 16:51:08 172.16.35.109 [798]PASS [email protected] 230 0 0 0
    2009-11-02 16:51:08 172.16.35.109 [798]sent /wyse/wlx/00806470CD9C.ini 550 2 0 0
    2009-11-02 16:51:08 172.16.35.109 [799]USER anonymous 331 0 0 0
    2009-11-02 16:51:08 172.16.35.109 [799]PASS [email protected] 230 0 0 0
    2009-11-02 16:51:08 172.16.35.109 [799]sent /wyse/wlx/wlx.ini 226 0 2632 0
    2009-11-02 16:51:08 172.16.35.109 [799]QUIT – 226 0 0 0
    2009-11-02 16:51:10 172.16.35.109 [800]USER anonymous 331 0 0 0
    2009-11-02 16:51:10 172.16.35.109 [800]PASS [email protected] 230 0 0 0
    2009-11-02 16:51:10 172.16.35.109 [800]CWD wyse/wlx 250 0 0 0
    2009-11-02 16:51:10 172.16.35.109 [800]QUIT – 226 0 0 0
    2009-11-02 16:51:48 172.16.35.109 [801]USER anonymous 331 0 0 0
    2009-11-02 16:51:48 172.16.35.109 [801]PASS [email protected] 230 0 0 0
    2009-11-02 16:52:23 172.16.35.109 [801]sent /wyse/wlx/wy_sc_6.6.2-02.64m 426 121 11730944 0
    2009-11-02 16:55:39 172.16.35.109 [801]closed – 421 121 0 0
    Thank you,
    -Ari

    #16870
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Check out these MS KB articles. Maybe they help you. But honestly it looks like a pure FTP issue and not a Wyse TC issue.

    306183 Repeated 426 Entries in the IIS FTP Log
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;306183

    318380 IIS Status Codes
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;318380

    817829 FIX: Passive Mode FTP May Break with Multiple IP Addresses on External Interface
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;817829

    283679 Information About the IIS File Transmission Protocol (FTP) Service
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;283679

    CG

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