Windows Forum

Ask something
Discussion Locked

USR modem with W2K Power Users (Again)

0 helpful
5 replies

by eblank 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have over 50 US Robotics 5699B V.92 Win modems deployed in remote locations that our state is using for remote login connections and general internet access. These modems are installed in Windows 2000 systems with PIII and PIV processors, AGP video cards, 20 gig HD's (with our build, these are only about ? used), and 128 MB of RAM. The problem comes when using the V.92 drivers with the modem from a "power user" account on the local machine. On initial login to the local machine it will allow the user to dial out to either the local ISP or our WAN access servers, but after a disconnect command is sent, the modem returns an error in the 3cmlink.exe program. At this point, the user is forced to log off of the machine before it will allow them to dial out again

Note that they do not need to REBOOT, only log off.

This problem does not occur if the user is a local admin on the machine. When logged on as a local admin (either as administrator or as a user with admin rights) the modem performs properly allowing the user to dial, disconnect, dial again, disconnect and then connect to any of our established dialup accounts.

If I replace the V.92 drivers with their 56K drivers, the modem WILL allow power users to perform consecutive dialups, but this driver has it's own set of problems. (It will occasionally return an error saying that the modem is no longer present requiring a re-boot.)

USR says that their modem works fine and that his is an issuw with our software (W2K)

In further testing, I have set permissions at the directory level to give all power users full controll of the System32 folder and all sub folders. I have gone into the registery and set permissions for any instance of 3cm*; USR; and Modem to give power users fuill control. This STILL gives me an error on disconnect when logged on as a power user, but NOT when logged on as local admin.

HELP! PLEASE!

5 replies

by chris910

Well since nobody else has thrown any thing out mayby this will help.
I did this for an application that I was having similar problems with. I took a clean image where the driver had never been installed. I then loaded the Symantec Ghost AI builder client (it creates installation packages for apps, I understand that ZenWorks and some of the other imaging packages have similar features) and ran the initial pass. Then I installed the driver and closed out the client. Durring the editing phase of closing the client it displays all of the system changes that where made durring the install. Perhaps a similar method will help you locate the erant file(s).

Question:
Have you looked the the event logs to see if any error is being reported or a warning is being generated?

by eblank

I've checked the even logs and also the Dr. Watson logs. None of these logs were helpfull. As for using Ghost AI builder, I am neither familiar with the program nor (more importantly) authorized to purchase a copy (*sigh*).

by curacao_dejavu

you need this http://tinyurl.com/33tyo
or another program that tracks changes made during an installation so you can then vhnage the permissions then accoringly so others users can use the program (in your case modem) properly.

Leopold

by eblank

This was a nice idea, but since the drivers are not installed by a 3rd party installation program (they are instaed installed via a windows hardware PNP detection) the above utility can't help.

by eblank

FIXED! After literally months of poking at this issue, I have finally found the culprit!
I had originally tried to fix this issue via windows update, update of the computers BIOS and firmware/driver updates of the modem. I also went into regedit and set the permissions on every key that I could find with reference to the modem, all with no luck.
With the help of some of the 3rd level support at my "company" (actually I work for a state government IT group) I was re-introduced to the wonders of the SecPol.MSC management console, where I discovered the offending group policy by first finding every policy that listed Administrators WITHOUT power users, and adding the power users to these. Lo and behold after doing that, the modem no longer generated errors. I then went through and removed each entry until I got it to fail again. It turns out that this issue revolved around the "Increase Schedule Priority" security policy group. My only question now is: What the heck does this have to do with a MODEM???

This discussion is closed to new replies.