Discussion Locked

Windows95 Logon Script Does not Work

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

To Any corresponding TechRepublic Members:

I am attempting to remotely support a Tech consultant at a satelite company location that is having problems with a Windows95 logon script. he states: (exact quote):
----------------------------------------
There is a 95 computer here that runs a scanner. Since we have logon scripts that run from the server, anybody can logon to this computer - run their scan and save it to their network folder because their script maps the drives for them.

Itis currently at 192.168.10.127 IP address. I wanted (just because I need organization) to move it into one of the unused addresses below .125 (like 103 for instance) when I did that, the logon script didn?t run. I tried a bunch of different open address and the only one that seems to work is 127. I also tried this experiment with Chris? new (Karen?s old) NT laptop and the problem didn?t exist. The NT will run the script from any IP address.

Any ideas as to why this happens?
-----------------------------------------
I am not sure why this is happening either, but would greatly apprecaite any insight into this quirk of a problem. Thank you.

Paul M. Chavez
IT Support Technician
Taylor Metro Corporation
pchavez@taylorusa.com

6 replies

by pahosler

Are there any networking functions working? Could the netmask be wrong? Is the ip set by the server, ie DHCP, or is it manually set? What do they mean by run the script from any address, did they hook the scanner up to the other machines and access them, or did they just change the ip of the clients and leave the win95 ip at original ip setting? In which case it shouldn't matter what the client IP is, but this script that maps the drive, etc, may be looking for specifc ip?

Paul

by xpertdragon

Thank you for your rapid response. Yes, regular network functions are working, just not the login batch file used to setup personal drive mappings for every user logged in. All IP address's at the site are manually set, and this one was manually changed. He means that the IP address the machine HAD was executing logon scripts just fine, and the minute he changed it to something like 192.168.10.103, the scripts were no longer working. I am almost positive that the script has no settings specifying a certain permanent IP address. I assume they want to physically leave the machine where it is, with the scanner attached, so that users can go log into it, scan, logout and leave.

by pahosler

Ok, I wouldn't assume that the scripts don't have hard coded ip's since all the other machines do. I will at this point go on the assumption that the win95 box had that ip when it was set up with the scripts. This makes the most since, otherwise swapping ip's shouldn't matter. Though win95 can be kind of quirky about networking. Can this particular pc be upgraded to win98, if so have him do it, as this may at least solve any networking issues. But then if it is something in the script thenyou'll still have to fix that aspect.
Paul

by pahosler

Hey, I just realized something. If you are running the scripts through the NT server you will have to let the server know that you changed the IP for that machine. LMHOSTS maybe? Sorry I am more familiar with Linux than NT. If I had a name assigned to a machine and I changed it's IP I would have to change the IP in my hosts file. I know NT uses at least a similar scheme.

Paul

This discussion is closed to new replies.