(no subject)

[jacobine.livejournal.com]

How hard is it, I ask you, to grasp that if the login box you are looking at says 'Windows 2000' that you are supposed to use your Windows password?

Yet almost every day, somebody calls us having trouble. See, we use terminal servers to run a particularly bandwidth greedy application we have. Our users click on a link, log onto the server, then log onto the application (which has a different password, because it runs off our AS/400.)

Yet people don't connect that Log onto Windows with the Log onto Windows they see in the morning. Some of them even argue with us about it.

I really hope they get the web interface for the thing written soon. Really soon.

Comments

[anivair.livejournal.com]

This hapens to me every day. I ask someone what they password is and they ask if I mean their password for "the computer" or "procomm". neither one of these is really correct as the "computer" password is the password their their login fr their OS (Windows) and the password for "procomm" is really the password for teir login for our server, which they access through the terminal emulator function of procomm. Ahh well.

[omicron32.livejournal.com]

Erm... Well even I don't understand what you mean and I'm a sysadmin. :P

[anivair.livejournal.com]

I thought it was clear. They not only confuse their login for windows with their login for our internal system (a linux machine) but they also get teh descriptions all off. The Windows login becomes the computer login (easy enough to get my brain around though not correct) and their login for our server becomes their system login, their computer login, their procomm login (they treat the emulator as if IT were our server). it just gets all very confusing when dealing with them.

[dmsalem00.livejournal.com]

Everyone's system is clear to THEM. I almost followed the whole way, though.

But if I started babbling about our call-logging programs, I'm sure someone's head would start spinning. maybe that oddball guy.

[gnostalgia.livejournal.com]

someone higher up over there needs to learn how to set up the as/400 and windows to share passwords. sometimes there realy is a tech fix for a people problem. :)

it's kind of a pain because of the limitations on the '400 side with username and password lengths but it can be done...

[jacobine.livejournal.com]

There's some pretty long password capability -- and we just got a brand new 400 that they're migrating to, as well. Gonna have a partition running unix on the new one. And we have thier user IDs standardized across the systems.

Main problem would be the requirement that AS/400 passwords begin with an alpha character. A lot of my users use number strings for their network password.

Of course, our other problem is that Operations (the as400 people) are separate from the Network (windows) people and rarely the twain shall meet... However, since Operations also handles security, we'd just have to lobby. A lot.

We're actually working on that problem, though. We know it can be done, but try coordinating a group that wants nothing to do with the 400 and doesn't allow us to have high level network access....

[gnostalgia.livejournal.com]

That's a shame. :P But, yeah, you always have to remember that the majority of IT work takes place on the 8th, 9th, and 10th layers of the OSI model.

That would be the theoretical layer, the financial layer, and the political layer, respectively.