cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted

407 error while trying to reach a foward facing internal server

Jump to solution

I have a forward faceing internal server that we cannot reach thru the MWG we get back a cannot connect from McAfee.  When I look at the traffic I see a 407 error.

I'm sure that I have not provided enought information but I need to start somwhere.  Any ideas?

1 Solution

Accepted Solutions
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 3 of 3

Re: 407 error while trying to reach a foward facing internal server

Jump to solution

Hello,

Jons approach is pretty common. I see many customers not filtering their internal services, because you would usually trust them. In case filtering is required, we need to find out where the 407 is coming from. 407 means authentication is required, so I see two options

- MWG fails to authenticate, which is unlikely if authentication works for other web sites

- MWG receives a 407 from the network, so either the server is sending a 407 because it requires authentication, or some other device.

I would start checking if Jons idea works out. If the traffic needs to bne authenticated and filtered, I would probably check the log files of the remote server, to see whats coming in there and whether it requires authentication or not.

Best,

Andre

View solution in original post

2 Replies
Highlighted
Level 12
Report Inappropriate Content
Message 2 of 3

Re: 407 error while trying to reach a foward facing internal server

Jump to solution

Internal servers on your network should already be trusted.  They do not need to be put through all the filters of the Web Gateway.  You should have an IP address whitelist in the Global Whitelist that will bypass any of your network subnets which should include this internal server.

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 3 of 3

Re: 407 error while trying to reach a foward facing internal server

Jump to solution

Hello,

Jons approach is pretty common. I see many customers not filtering their internal services, because you would usually trust them. In case filtering is required, we need to find out where the 407 is coming from. 407 means authentication is required, so I see two options

- MWG fails to authenticate, which is unlikely if authentication works for other web sites

- MWG receives a 407 from the network, so either the server is sending a 407 because it requires authentication, or some other device.

I would start checking if Jons idea works out. If the traffic needs to bne authenticated and filtered, I would probably check the log files of the remote server, to see whats coming in there and whether it requires authentication or not.

Best,

Andre

View solution in original post

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community