| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 37292 | 2003-09-03 06:08:00 | You must be logged in as an administrator. What the hell? | Kibito (623) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 172729 | 2003-09-03 06:08:00 | Hello. I have win 2000 pro. And since yesterday, it tells me that I need to be logged in as an administrator to activate and deactivate norton firewall. What the hell???? I am logged in as an administrator. I even tried the default Administrator account and it still gave me that crap. What the hell is going on why is it not recognizing me as the comp admin???? |
Kibito (623) | ||
| 172730 | 2003-09-03 06:31:00 | I think it means you need to be logged on as Supervisor to make changes (inside Norton Firewall user accounts options). Set Supervisor as the startup account as well if you like. | DMcKenzie (4203) | ||
| 172731 | 2003-09-03 06:37:00 | No but I did. Administrator and my other account which is under my name are both admin accounts. But now it suddenly tells me I can't do it coz I'm not an admin which i AM!!! |
Kibito (623) | ||
| 172732 | 2003-09-03 06:47:00 | What version of Norton Personal Firewall? Or do you have Norton Internet Security (which includes the firewall)??? Is Nortons set to use the Windows accounts as the Norton's accounts??? Or have you got it set to use Supervisor, not logged on etc. ??? |
DMcKenzie (4203) | ||
| 172733 | 2003-09-04 06:09:00 | I have internet security 2003. I don't know what it's set to use but it like worked like beginning of the week just yesterday it started happening. But I do know that like I don't use the Default Administrator login I use my own name login but it's set to administration group as well so yea??? It's still happening too!!! |
Kibito (623) | ||
| 172734 | 2003-09-04 16:10:00 | It's a known fault with the software, unfortunately it's user management is apalling and can cause all sorts of problems. First port of call, ensure you have hidden files and folders viewable and search for nisum.dat - find it, delete it and reboot - see if that works. Failing that, post back and I will see if I can rustle up the fix I used on a clients machine a couple of days ago. |
whiskeytangofoxtrot (438) | ||
| 1 | |||||