Subj : NT Proxy access from remote subnets
To   : All
From : Tom Yost
Date : Thu Aug 31 2000 06:51 am

I first posted the following in the Windows NT 
conference. However, it now looks like this could 
be a routing issue accross subnets. I'm currently 
unable to even ping our proxy server from our 
remote subnets.

We later determine that drive C on the Proxy 
Server was full. I did a backup and then deleted 
files in the following directories.

c:\temp
c:\urlcache
c:\winnt\temporary internet files

Also I moved DHCP services to another Server, one 
that did not need to be frequently reset. 
Afterwards everything was fine on the local 
segment. However, remote subnets are now unable 
to get out through the Proxy Server. 

Our vendor told use this was because we moved the 
DHCP  services to another server. That the 
routers had to be reconfigured for the new 
location. However, I don't understand this since 
all of our remote sites have static address. 
We'll then moved  DHCP back to the proxy and 
continue to have a problem from our remote 
subnets.

On a positive note, the Proxy Socks services are 
now stable.

> Our Socks Proxy services need to be 
> restart "often". When checking for "current 
> connections" in the Microsoft Internet Service 
> Manager I get the following:
> 
>  The connection attemp failed because there's a 
>  version conflict betwwen the server and client
>  software.
> 
> Does this suggest that "a" desktop browser 
> could  be the cause of this problem? 

--- Platinum Xpress/Win/WINServer v3.0pr4
 * Origin: MPCUG WeBBS (1:121/2)

.