Alexio

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: ‘Invalid Credential’ while printing… #12874
    Alexio
    Member
    • Total Post: 5
    • Newbie

    Thanks CG, I will look at those things that you pointed out.

    Alex

    in reply to: V10L freezes on printing #12846
    Alexio
    Member
    • Total Post: 5
    • Newbie

    Hi all,

    I would concur that V10L firmware version 6.1.0_05 is unstable. For us, the hardware ceased to respond when a restart was initiated requiring a fat finger on the power switch. We also had issues with 6.1.0_06 and are currently using 6.1.0_08. Some of our users are reporting “Trap: Protection fault” with 6.1.0_08 but all in all it seems more stable than previous versions. Curiously, the version that shipped with our Feb 08 V10Ls (6.1.0_07) is not on the download site. Firmware stability continues to be an issue for us.

    Cheers,
    Alex

    in reply to: ‘Invalid Credential’ while printing… #12844
    Alexio
    Member
    • Total Post: 5
    • Newbie

    Hi CG,

    Here’s my wnos.ini
    Followed by a typical user.ini

    Thanks,
    Alex

    … and looking at it now, I wonder if my problem might be related to the fact that I have ‘blank’ SMB configurations in the user.ini for SMB3 and SMB4. These server no purpose, I know. They are just artifacts of the web page form that created the user.ini. Also, I assume that having ThinPrintEnable set to zero for global session settings is not a problem, right?

    Thanks again!

    #####################################################
    #
    # Global settings for all thin clients
    #
    #####################################################

    # do not automatically load firmware upgrades
    #autoload=0

    # **** domain/signon settings ****
    DomainList=ZZZ
    DisableDomain=1
    PasswordServer=ZZZ1
    SignOn=1 EnableOK=1 DisableGuest=1 ConnectionManager=hide
    NoticeFile=notice.txt
    KeySequence=1 Ctrl+Alt+Del=0

    # **** time settings ****
    TimeServer=10.100.61.22 TimeFormat=’24-hour format’
    TimeZone=’GMT – 09:00′ ManualOverride=1 daylight=1 Start=030207 End=110107 TimeZoneName=’Alaskan Standard Time’ DaylightName=’Alaskan Daylight Time’

    # **** security settings ****
    PRIVILEGE=NONE EnableNetworkTest=1 ShowDisplaySettings=1
    EnableGKey=1

    # **** desktop settings ****
    DesktopColorDepth=32
    DeskColor=’000 153 220′
    formurl=logo.jpg
    ScreenSaver=15 LockTerminal=2 Type=2 image=patch2.jpg
    Device=keyboard numlockoff=0

    # **** global Session Configuration *****
    PNLiteServer=ZZZ1/citrix/pnagent1/config.xml
    IcaBrowsing=http
    SessionConfig=ALL unmapprinters=0 unmapserials=0 disablesound=0 mapdisks=1
    seamless=1
    SpeedBrowser=1
    ThinPrintEnable=0

    #jfedco: thin client user configuration file

    DefaultPrinter=’SMB1′
    Printer=SMB1 Localname=” host=ZZZ3 Name=’YY2pr243′ PrinterID=’HP Color LaserJet 3000 PS’ Enabled=1
    Printer=SMB2 Localname=” host=ZZZ3 Name=’YYpr149′ PrinterID=’Xerox WorkCentre Pro 32 C PS’ Enabled=1
    Printer=SMB3 Localname=” host=ZZZ3 Name=” PrinterID=” Enabled=0
    Printer=SMB4 Localname=” host=ZZZ3 Name=” PrinterID=” Enabled=0
    Resolution=’1280×1024′ Refresh=60
    DeskColor=’000 000 000′
    MouseSpeed=1
    MouseSwap=0
    Device=keyboard numlockoff=0 repeatrate=1 repeatdelay=2
    PRIVILEGE=LOW EnableNetworkTest=1 ShowDisplaySettings=1
    TimeServer=10.100.61.22 TimeFormat=’12-Hour format’ DateFormat=’yyyy/mm/dd’
    ScreenSaver=15 LockTerminal=1 Type=2 Image=patch.jpg
    desktop=jfedcojfedco.jpg

    in reply to: V10L looses settings after Restart. #12543
    Alexio
    Member
    • Total Post: 5
    • Newbie

    Are you using WDM and the 161 DHCP option? If so, have you seen this link?

    http://www.freewysemonkeys.com/modules.php?name=News&file=article&sid=23&mode=thread&order=0&thold=0

    We had things set up just fine using an FTP server to serve up wnos.ini and as soon as I introduced WDM into the mix our V10Ls failed to configure after restart. It turns out that WDM overrides the 161 option by default and resets the FTP server entry to itself. Unchecking “Enable Return FTP/INI at Checkin” fixed the problem. Don’t know if this is applicable but good luck!

Viewing 4 posts - 1 through 4 (of 4 total)