wyldstallyn

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • wyldstallyn
    Participant
    • Total Post: 5
    • Newbie

    Thanks for this – it’s helpful to know we’re not alone.  We’ve got the same issue… Windows Server 2016 hosts, Dell Wyse 5470 clients with ThinOS 9.1.2101 all being reported with the name 5070.  Our old C10LE devices running ThinOS 8.6 are fine.

    This stops us mapping printers to devices…

    in reply to: WMS Standard (Free) #53710
    wyldstallyn
    Participant
    • Total Post: 5
    • Newbie

    Thanks very much for that guide.  I may have a go at renaming the server back to our convention and redo the aliases over Christmas.  Thank you very much again!

    in reply to: WMS Standard (Free) #53636
    wyldstallyn
    Participant
    • Total Post: 5
    • Newbie

    Thank you!  We name our servers using a convention based on purpose and server version and then use DNS aliases so that when we upgrade servers we just remap an alias rather than having to change a setting in a device.

    Anyway, after clients were pointed at WMS using the DNS alias, they would then get the true name of the server and try using that which is where things were breaking.

    Your reply gave me the confidence that it should work and last night I resolved the issue, so we’re happily running now.  Thank you!

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