Jump to content

Recommended Posts

Posted

Used to have a Vanilla Windows Server 2003 R2 domain that was set up by a local company who covered several schools in the County. Network was then wholly XP and I noticed that occasionally clients were picking up a proxy setting that had clearly been set from another school.

 

Now have a new domain served by a Windows Server 2008 - clients are a mix of XP Pro and Windows 7. This domain was set up by a really good server installer. However, I notice that despite the correct proxy setting being listed in Group Policy somehow the erroneous proxy setting still sometimes gets picked up by clients.

 

Where could the setting be lurking:confused:

Posted
Use the RSoP snapin just to make sure that it is not ferrited away in some long forgotten policy somewhere (assuming domain migration to 2008) and check for settings as above.
  • Thanks 1
Posted
Make sure that (if you have more than one DC) that the servers are replicating properly. The GPO's are part of the SYSVOL file replication topology, if its broke - then you can end up with GPO's that are out of sync and that can lead to all sorts of problems. If its happening on some XP machines (only) then check KB 888254 - its an old one - but it's often overlooked escpecially if you have re-used old images that haven't been updated properly.
Posted

Thanks Waldronm200

 

Looks like this might be something to do with it.

 

We have a lone dc and looking at the DNS I now see that the current domain is listed in the Forward Lookup plus the old Server 2003 domain is listed as Secondary.Would I be right in thinking I can just delete it?

 

Might be set on either your DNS or DHCP server using WPAD.
Posted
We have this problem with our Administrator account, there are no policies setting proxy for administrator and no scripts, however when we login as admin and go to enable proxy for machines which aren't routed it has the address of our 8yr old ISA server, no idea where it is coming from, have searched and searched. This includes if we login on a vanilla install machine.
  • Thanks 1
Posted

Thanks SkreM1980. Any thoughts on my earlier post; it's reassuring to hear that it's not just little old me having this issue. If you do find an answer don't forget to holler please.

 

"We have a lone dc and looking at the DNS I now see that the current domain is listed in the Forward Lookup plus the old Server 2003 domain is listed as Secondary.Would I be right in thinking I can just delete it?"

Posted
"We have a lone dc and looking at the DNS I now see that the current domain is listed in the Forward Lookup plus the old Server 2003 domain is listed as Secondary.Would I be right in thinking I can just delete it?"

 

Without looking at everything .. I can't be certain, however most likley yes. This is probably a legacy setting from the domain migration. Send me a couple of screenshots of excatly where you mean and i can maybe be more helpful.

 

Back to your original proxy problem ... what type of user profiles do you use? Is it possibly hidden in the registry of the profile. I know at one stage we edited the registry of our mandatory profile (Regedit>file>Load Hive>Browse to \\serverpath\profileshare\ntuser.man) to ensure the correct settings were there too just incase of GPO applying issues.

 

 

Skr

Posted
Apologies to FN and also replying to your and Skrs question on profiles - nothing specific set up in AD everything seems to get picked up from a logon.bat. Feels like mandatory though.
Posted
Mandatory profile could be configured in GPO i think?? (Know TS mandatory profiles can be) Very worth checking, as the profile could contain the settings in the registry.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...