AD and MS Proxy conflict at the DNS level. AD requires a DNS entry on the
client computer. This DNS entry causes long delays on a Proxy client. See :
Q170043 - Windows 95 Clients May Be Slow Starting the Browser
This article mentions Win 95 clients on Proxy 1.0. I have seen this same
behavior on Win98/Win2k computers on Proxy 2.0 Sp1.
On another note. You don't need WSP Client to browse the internet through MS
proxy. You grant your users/groups permission to use www in the properties
of Web proxy and manually point the client browser to the proxy by IP
address and port. WSP Client is for POP3, SMTP, etc...
Quote:> I have necountered a strange problem. It seems that our Ms Proxy server
> stopping machine from connecting to AD. We are running a typical AD setup
> with 2 DCs. We are also running MS Proxy 2.0 SP2 for our internet access.
> We installed the Proxy clients on the servers to allow them to access the
> internet, but it seems to be stopping any Win2k machine with SP2 on it
> connecting to AD. If we active the Proxy client, the server can't connect
> to the AD serverices (for a test we opened Schema in mmc, and if Proxy
> client is enables, it can't find and connect to the Schema server, but if
> disable Proxy client it finds it fine). Thsi only seems to happen
> Anyone have any idea what could be the problem, or better yet how to fix
> without killing the proxy client?
Hi everyone. I am stumped. I have a windows 2000 server
that keeps telling the client machines to reset the
internet explorer to use a proxy setting of gate:8080.
Well that machine is gone and replaced and now we can't
get it to stop telling client machines to use the old
proxy settings. There are no proxies now. How do I get
it to stop telling clients to use the old proxy.
Also I looked in gpedit.msc but the proxy settings are
blank???? so is this where I cahnge it???