Technology Tips and News
Hi
I am facing an issue with TMG proxy.
Some times it is prompting for User credentials. Even after giving the correct credentials also it is prompting for the credentials again and again. After restarting the TMG proxy server it is working fine. Like this happening once in a day or once for every two days. Today without restarting the sever issue has been resolved.
Why this issue is coming. Please suggest me to resolve this issue.
This same issue plagued us for many months.
We ended up changing to Kerberos authentication and it went away.
This same issue plagued us for many months.
We ended up changing to Kerberos authentication and it went away.
This same issue plagued us for many months.
We ended up changing to Kerberos authentication and it went away.
This same issue plagued us for many months.
We ended up changing to Kerberos authentication and it went away.
This same issue plagued us for many months.
We ended up changing to Kerberos authentication and it went away.
It is TMG Standard edition.
Today also I faced the same issue. Then I restarted the microsoft forefront tmg control service. Now it is working fine. Please suggest to avoid this issue.
How many clients are going through the server? Is it one or multiple servers? Are they Web Proxy clients, Firewall clients, SecureNAT clients, or a mix of all 3 types?
Are your clients using the FQDN of TMG or the IP address in their browser settings?
Normally when we see issues like this it means that TMG is having problems communicating with the DCs or it is being overwhelmed for other reasons and packets are being backlogged.
If there are any types of delays in DNS this can have a snowball effect on forward proxy traffic and eventually we can see auth prompt issues.
Network traces are probably going to tell you the most if you can gather them when the issue is happening.
How many clients are going through the server? Is it one or multiple servers? Are they Web Proxy clients, Firewall clients, SecureNAT clients, or a mix of all 3 types?
Are your clients using the FQDN of TMG or the IP address in their browser settings?
Normally when we see issues like this it means that TMG is having problems communicating with the DCs or it is being overwhelmed for other reasons and packets are being backlogged.
If there are any types of delays in DNS this can have a snowball effect on forward proxy traffic and eventually we can see auth prompt issues.
Network traces are probably going to tell you the most if you can gather them when the issue is happening.
How many clients are going through the server? Is it one or multiple servers? Are they Web Proxy clients, Firewall clients, SecureNAT clients, or a mix of all 3 types?
Are your clients using the FQDN of TMG or the IP address in their browser settings?
Normally when we see issues like this it means that TMG is having problems communicating with the DCs or it is being overwhelmed for other reasons and packets are being backlogged.
If there are any types of delays in DNS this can have a snowball effect on forward proxy traffic and eventually we can see auth prompt issues.
Network traces are probably going to tell you the most if you can gather them when the issue is happening.
How many clients are going through the server? Is it one or multiple servers? Are they Web Proxy clients, Firewall clients, SecureNAT clients, or a mix of all 3 types?
Are your clients using the FQDN of TMG or the IP address in their browser settings?
Normally when we see issues like this it means that TMG is having problems communicating with the DCs or it is being overwhelmed for other reasons and packets are being backlogged.
If there are any types of delays in DNS this can have a snowball effect on forward proxy traffic and eventually we can see auth prompt issues.
Network traces are probably going to tell you the most if you can gather them when the issue is happening.
How many clients are going through the server? Is it one or multiple servers? Are they Web Proxy clients, Firewall clients, SecureNAT clients, or a mix of all 3 types?
Are your clients using the FQDN of TMG or the IP address in their browser settings?
Normally when we see issues like this it means that TMG is having problems communicating with the DCs or it is being overwhelmed for other reasons and packets are being backlogged.
If there are any types of delays in DNS this can have a snowball effect on forward proxy traffic and eventually we can see auth prompt issues.
Network traces are probably going to tell you the most if you can gather them when the issue is happening.
Hi,
Above 500 clients are going through this sever. We are having only one TMG sever. Using 3 types of clients.
clients are using the IP address in their browser settings.
Hi
Have the issue happened again? If yes, have you done any network tracing when the issue happened?
If you need further assistance, please feel free to let us know.
Best regards,
Susie
This topic is archived. No further replies will be accepted.
Other recent topics
Click here to get your free copy of Network Administrator. Over 25 plugins to make your life easier