All XP PRO clients keep losing IE LAN settings??

[lost_2003]

Hi all,

First of all allow me to explain to you it's my first time posting and that I am a complete novice at administering server 2003. BEEN LUMBERED WITH IT I'M AFRAID.

Second, I have inherited a system that runs 2 servers, a CURriculum server, and an applications server, both have server 2003 standard installed. A security system full of group policies that rivals only NASA's

Yesterday an upgrade of Symantecs Anti Virus 9 was installed on the CUR server and it services all clients. Ever since that installation all the client/workstations, around 30 of them, keep losing the proxy server address setting in Internet Explorer, and defaults back to the IP address of the CUR server, the port setting stays the same.

This doesn't allow anyone to access the Internet unless I manually go into a client/workstation PC, log in as the Administrator and change the proxy address setting in Internet Explorer manually, to the necessary ISP's proxy settings provided. ie: (address xxxx.cccc.nnnnn.ccc.au) (port xxxx). After I do this and log out as administrator, and a user logs in with their user account it works fine, but it seems after the computer is powered down it reverts back to seeing the CUR server IP as the proxy server address instead of the necessary ISP's proxy settings, and I have to set the client/workstation manually again, and this becomes too difficult and very time consuming.

Can anyone please tell me how I can change the settings on the CUR server, (in point form if possible, remember novice here) so that the clients receive the correct proxy setting permenantly, instead of reverting back to the IP address of the CUR server?

Thank you
Hope this makes sense.

[snowmonkey]

Originally Posted by lost_2003

Hi all,

First of all allow me to explain to you it's my first time posting and that I am a complete novice at administering server 2003. BEEN LUMBERED WITH IT I'M AFRAID.

Second, I have inherited a system that runs 2 servers, a CURriculum server, and an applications server, both have server 2003 standard installed. A security system full of group policies that rivals only NASA's

Yesterday an upgrade of Symantecs Anti Virus 9 was installed on the CUR server and it services all clients. Ever since that installation all the client/workstations, around 30 of them, keep losing the proxy server address setting in Internet Explorer, and defaults back to the IP address of the CUR server, the port setting stays the same.

This doesn't allow anyone to access the Internet unless I manually go into a client/workstation PC, log in as the Administrator and change the proxy address setting in Internet Explorer manually, to the necessary ISP's proxy settings provided. ie: (address xxxx.cccc.nnnnn.ccc.au) (port xxxx). After I do this and log out as administrator, and a user logs in with their user account it works fine, but it seems after the computer is powered down it reverts back to seeing the CUR server IP as the proxy server address instead of the necessary ISP's proxy settings, and I have to set the client/workstation manually again, and this becomes too difficult and very time consuming.

Can anyone please tell me how I can change the settings on the CUR server, (in point form if possible, remember novice here) so that the clients receive the correct proxy setting permenantly, instead of reverting back to the IP address of the CUR server?

Thank you
Hope this makes sense.

Welcome to this forum with your first post.

I think your issue could be resolved with couple of simple domain policy setting........since your predecessor was a policy natzy I guess you need to undo few things and get the network going

Go to start and type in "gpedit.msc" , this would open you local domain policy editor, drill down to...User Configuration->Windows Setting->Internet Explorer Maintenance-> Connection ..On the right panel you will see the Proxy Setting, double click on it and set your proxy detail information in there.

Also , from top down...Local Domain Policy ->Administrative Template->Windows Component-> Internet Explorer.....(Right Panel) Make sure the "Disable Proxy Setting" is not enabled...set it to "not configured".

After changing the policy, you either have to reboot the server or execute this command on the command prompt.

On the Server 2003 Server and XP Client:
C:\gpupdate /force and the same thing on client computer

On Windows 2000 Client:
C:\secedit /refreshpolicy /machine_policy
and
C:\secedit /refreshpolicy /user_policy

I hope this is what you were looking for.


Cheers

[snowmonkey]

Originally Posted by oldtimer

Call your server tech support.Tell them the above.
After all your paying them for a connection.

Oldtimer, just because you buy the server from a place such as Dell, IBM, HP ...etc , that doesn't mean they have to support the operating system and everything else that goes with.....in this case it appears that some old domain policy changes the behavior of the desktop system when they lo gin to the domain.......since our friend "lost_2003" is the Network Administrator of the work place, it would be his duty to fix it.....on the other hand, he could call technical contractor and pay lots of $$$$ to get the problem fixed.


Cheers

[lost_2003]

Hi SnowMonkey,

Thank you for taking the time to reply, and very sorry I didn't respond earlier. This is the first opportunity I have had to check for answers to my problem.

I have printed out what you suggested and will try it out. Thank you!

I will let you know how it turns out after trying it. As you may understand I am kind of terrified to try anything on a server that will affect so many other people!

Old timer thanks for your input too, however Snowmonkey is sort of correct the ISP's don't support you this way, it's not an ISP problem it's a problem on our side of things. Nevertheless thanks for the suggestion.

I'll definately let you guys know how things turn out with this one. Stay tuned I'll have a million more problems I'm sure.

"Policy Nazi" I like that description snowmonkey ,

Actually the system he set up is pretty good, he set it up as a Remote Installation System (Server), but adding anything to it is a nightmare!

Especially when one never worked with and knows nothing about server 2003!

He's really the only one that could administer it properly and now that he's gone he couldn't give a dang.

He hoped to be able to sell this system he set up to others, and basically go around administering it so he would never be out of work. However it didn't work out that way and now we're stuck with it until we can eventually change it, but that will take heaps of time, and money and it's the money side of things the principals don't like!

Anyhow thanks again guys don't want to bore you with all the background details.

catch ya all later.

[lost_2003]

Just a quick hello to let you know I implemented snowmonkeys suggestion, and so far it has seemed to work. But I only implemented it today, when all the workstations shut down for the night, tomorrow I'll know for sure when they re-start the workstations, but so far so good.

Thanks again