Smoothwall - Bypass Proxy/Authentication

[lmrogers]

Good Morning

 

I am hoping someone here can help me from going crazy and around in circles with a Smoothwall.

 

I have spun up a new VM and it has got a static IP in the same range as my other servers which should all be setup to bypass proxy authentication on the Smoothwall. On the old legacy servers this is working correctly and I can do everything I need.

 

I am just trying to use PowerShell to install some modules and testing it with the Invoke-WebRequest command. However, everytime I do this I get an error saying Kerberos/NTLM authentication failed. But the server shouldn't need to authenticate, it should be bypassing the proxy altogether. Other servers are working correctly and not producing this error.

 

Can someone help point me in the right direction as to how to achieve this?

 

Cheers

[markberry]

Have you tried setting the proxy settings in powershell?

 

https://cloudrun.co.uk/powershell/configuring-powershell-to-work-behind-a-proxy-server/

[lmrogers]

Have you tried setting the proxy settings in powershell?

 

https://cloudrun.co.uk/powershell/configuring-powershell-to-work-behind-a-proxy-server/

 

I've looked at this but the problem is that shouldn't be needed. I have other servers which are bypassing the proxy and working fine as is. Yet this new server is not. It's IP address is in the same range as the other working server and from what I can see in the smoothwall it is within the specified range for exemption.

[markberry]

Have you checked the Realtime logs to see why it's being blocked?

 

We tend to just add the IP of the servers to the Source exception IP addresses and use port 801.

[lmrogers]

Real time logs are showing it as code 407 which is no authentication.

 

Where do you add that Source exception?

[markberry]

Real time logs are showing it as code 407 which is no authentication.

 

Where do you add that Source exception?

 

Guardian -> Exceptions -> Manage source exceptions

 

Add the IP of the server then change the proxy settings on the server to Smoothwall_IP_Address and port 801

[ibpalle]

Or just use no proxy settings. The source exception in the Guardian section is for the transparent proxy so once the IP has been added, the upstream won't be intercepting it. You can also create a new auth policy for the proxy the system is set to use and use a location object with the server IP and set that to use no authentication.

[ITGuyNW]

Sorry to bring back an old thread

 

Has anyone found an ideal solution for this for when you want to run powershell scripts in OOBE? I'm wanting to add the hardware hash to Intune but I get errors because of the proxy.

[tom_newton]

Is this on a machine that should be excluded from proxying? If it's an auth issue you could put the destination domain in "allow for all" and do-not-auth-for...