I have a Windows 2000 terminal server with the following symptoms.
Some users (logging into AD with Internet Explorer Maintenance GP settings) can access external websites with no problem.
Some users (including the local administrator) cannot and receive the "Page cannot be displayed" error when attempting to browse to an external website. Even though they cannot go to the page, they can successfully ping external both through FQDN and IP address. You can enter the resolved IP in the browsed and still NOT connect.
When logged on as the local administrator I browse to the following in the registry:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet
Settings]
I am interested in this:
"ProxyServer"="<proxy IP address>:80"
If I manually edit this value, it is overwritten almost instantaneously, and set back to another value. The value it is changed to was a working configuration in the past, but we have changed the outbound ports for http access on our proxy server. What's weird is the browser will reflect and maintain the change made in the registry but the registry reverts back to the original setting.
I have a GP with loopback processing that should be configuring the proxy settings (through Internet Explorer Maintenance) the same for everyone on this machine. For the most part this appears to be working and I have 4 other Terminal Servers that are configured the same and are in the same AD container. They have been set up and working time for a year now. The local group policy for the machine shows to be disabled for both the machine and user, and beyond that, nothing was ever configured through the local group policy. This is a new build.
Also, if I set the proxy settings for other apps such as Adaware, they can connect fine and pull updates. Outbound connectivity has been verified, but individual profiles seem corrupted.
Let me know what else you need to know. But help me! I'm stuck!
Some users (logging into AD with Internet Explorer Maintenance GP settings) can access external websites with no problem.
Some users (including the local administrator) cannot and receive the "Page cannot be displayed" error when attempting to browse to an external website. Even though they cannot go to the page, they can successfully ping external both through FQDN and IP address. You can enter the resolved IP in the browsed and still NOT connect.
When logged on as the local administrator I browse to the following in the registry:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet
Settings]
I am interested in this:
"ProxyServer"="<proxy IP address>:80"
If I manually edit this value, it is overwritten almost instantaneously, and set back to another value. The value it is changed to was a working configuration in the past, but we have changed the outbound ports for http access on our proxy server. What's weird is the browser will reflect and maintain the change made in the registry but the registry reverts back to the original setting.
I have a GP with loopback processing that should be configuring the proxy settings (through Internet Explorer Maintenance) the same for everyone on this machine. For the most part this appears to be working and I have 4 other Terminal Servers that are configured the same and are in the same AD container. They have been set up and working time for a year now. The local group policy for the machine shows to be disabled for both the machine and user, and beyond that, nothing was ever configured through the local group policy. This is a new build.
Also, if I set the proxy settings for other apps such as Adaware, they can connect fine and pull updates. Outbound connectivity has been verified, but individual profiles seem corrupted.
Let me know what else you need to know. But help me! I'm stuck!
