locked
Error showing when more users the public IP RRS feed

  • Question

  • User-1578974752 posted

    When lot of people using the system(vb.net) at the same time error is coming after assigning the public Ip. (Just 3 to 4 people use at same time ) How can I avoid that.

    Appreciate the help

    Wednesday, September 26, 2018 11:34 AM

Answers

  • User753101303 posted

    With each post you describe something new that seems unrelated (a problem with IP address, an eventvalidation error message and now an http 403) which makes hard to understand the situation on your side.

    If previous problems are solved it would be better to close the thread and open a new discussion for each new problem.

    I would check the IIS log to see the substatus code to see which kind of 403 error you have among those listed at https://support.microsoft.com/en-us/help/943891/the-http-status-code-in-iis-7-0-iis-7-5-and-iis-8-0

    For example if doing an Ajax request too often it could be a 403.502 etc...

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 3, 2018 7:22 AM
  • User-821857111 posted

    All these errors are shown when public IP assigned to the system. Before that No issue at all.
    No. What you actually mean is that all of these issues appear to have occurred when you changed the environment that the application runs in from Development to Production.

    This often happens, especially if you are using shared hosting. You have set session timeouts to 45 minutes, but they may well get cleared before that if the application pool is recycled, which can happen for a lot of reasons outside of your control on a hosted platform.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 3, 2018 7:57 AM

All replies

  • User753101303 posted

    Hi,

    It's always easier to help when knowing the EXACT error you have. For now it seems you have some custom code that assumes each users have his own IP address and "fails" (maybe just a logic error) to achieve the wanted result ?

    Or maybe you are storing this value inside a static (or VB shared) variable in which case the same value is shared by ALL users?

    Wednesday, September 26, 2018 2:19 PM
  • User1120430333 posted

    When lot of people using the system(vb.net) at the same time error is coming after assigning the public Ip. (Just 3 to 4 people use at same time ) How can I avoid that.

    Appreciate the help

    what kind of O/S is being used?

    Wednesday, September 26, 2018 3:40 PM
  • User-1578974752 posted

    Windows server 2012 R2

    Monday, October 1, 2018 5:05 AM
  • User753101303 posted

    But what happens exaclty ? I can't think of any error that could happen out of the box regarding the IP address once you have more than few users. I believe you have an error in custom code because using static data or having done a wrong assumption about IPs...

    It is much easier to help when knwoing the EXACT problem you have. Don't you have an error message?

    Monday, October 1, 2018 7:18 AM
  • User1120430333 posted

    Windows server 2012 R2

    Maybe, you have a concurrent connection issue. How many concurrent connections is the O/S licensed for?

    Monday, October 1, 2018 3:55 PM
  • User-1578974752 posted

    Thanks . I am not sure about the number of connections allowed. One error message as below.There is a Timer in my Test Page which was running for 40 minutes in the local host with out any issue .But when I run from the Live server after few minutes below error message is showing. How to use the ClientScriptManager.RegisterForEventValidation

    Invalid postback or callback argument.  Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page.  For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them.  If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.

    Tuesday, October 2, 2018 6:33 AM
  • User753101303 posted

    You are using session based viewstate ? It fails after 20 minutes ? What does the timer ?

    This mechanism ensures that a hacker doesn't try to post a value which is not one that you expect. See the call stack which should help to better understand which control is triggered this one...

    Tuesday, October 2, 2018 11:25 AM
  • User-1578974752 posted

    I am using sessions in lot of pages.  I placed <sessionState timeout="45"/> in the web.config.

    Timer is used in the Online Test page. After some time ,timer is stopping and showing below error message.How can I solve this. Thanks

    This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.

    Wednesday, October 3, 2018 1:54 AM
  • User753101303 posted

    With each post you describe something new that seems unrelated (a problem with IP address, an eventvalidation error message and now an http 403) which makes hard to understand the situation on your side.

    If previous problems are solved it would be better to close the thread and open a new discussion for each new problem.

    I would check the IIS log to see the substatus code to see which kind of 403 error you have among those listed at https://support.microsoft.com/en-us/help/943891/the-http-status-code-in-iis-7-0-iis-7-5-and-iis-8-0

    For example if doing an Ajax request too often it could be a 403.502 etc...

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 3, 2018 7:22 AM
  • User-1578974752 posted

    All these errors are shown when public IP assigned to the system. Before that No issue at all.

    5 min, when I open the Online Test Page ,the 403 error is showing.

    some times it is showing below error.

    Invalid postback or callback argument.  Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page.  For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them.  If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.

    All these error are in the online text page and not solved yet.

    Wednesday, October 3, 2018 7:26 AM
  • User753101303 posted

    Ah I thought it was something related to user's IP addresses.

    So you mean you started to have all those issues when exposing your server to internet (though a public IP) ? I would start with the 403, looking at the IIS log to understand which kind of 403 error it is.

    It might be rather on the network admin side.

    Wednesday, October 3, 2018 7:34 AM
  • User-821857111 posted

    All these errors are shown when public IP assigned to the system. Before that No issue at all.
    No. What you actually mean is that all of these issues appear to have occurred when you changed the environment that the application runs in from Development to Production.

    This often happens, especially if you are using shared hosting. You have set session timeouts to 45 minutes, but they may well get cleared before that if the application pool is recycled, which can happen for a lot of reasons outside of your control on a hosted platform.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 3, 2018 7:57 AM
  • User-1578974752 posted

    There are  2 server.   1.Test and one live. Liver server for example :10.100.10.88

    In Both Test and live ,it is working fine.

    Then I informed the network admin to assign Public IP to 10.100.10.88. After assigning ,I used http://abc.companyname.com.mywebsitename  .

    Both abc.companyname.com and 10.100.10.88 are same server.

    After that all the above mentioned errors are showing .

    As you mentioned ,I set the application pool Idle time out minutes of 10.100.10.88 to 55 min. Now error is not showing . But after 25 min,the timer is stopping. But No error.  I want atleast 30 minute the timer can not stop.
    Is there any other values to be adjusted in the server application pool of 10.100.10.88. Will there be any other issue if I put application pool Idle time out  to 70 min?

    Thursday, October 4, 2018 9:07 AM
  • User753101303 posted

    We still don't know the purpose of this timer. If it does Ajax requests the application pool should be kept alive. 20 minutes is the default timeout for a browser session. What if you change sessionState to make this longer as well ? This is failing after 25 minutes that make me think it could be that.

    If it doesn't help I would really do things the other way round ie as already suggested ie I would check the IIS log to see the exact 403.x error that happens and then I would check the link I posted earlier to fix this particular error.

    Here it seems you start from the configuration and wonder what could cause an error which is perhaps not yet fully analyzed. IMHO you should always start from the exact error that happens.

    Thursday, October 4, 2018 11:28 AM
  • User-1578974752 posted

    Thanks for the link . Forbidden: Source access denied is one error

    403.21 - Forbidden: Source access denied. The solution for this is not provided in that link.

    Wednesday, October 10, 2018 2:53 AM
  • User753101303 posted

    Seems something like https://www.itprotoday.com/file-sharing-and-management/iis-informant-handling-script-source-access-permission-iis or https://serverfault.com/questions/819199/iis8-5-with-webdav-only-serves-read-only-files ?

    This is the first time I see someone having this status code and I'm not sure how it can happen in a web application (seems related to WebDAV operations ?).

    Try  maybe the IIS forum at https://forums.iis.net/ or a Windows admin group but you'll likely need an expert advice on the configuration side before doing any action.

    Edit: If WebDAV is enabled and not needed one of my first move might be to disable WebDAV. You have that on particular http queries (trying to fetch a particular file type or with a particular http method ??)

    Wednesday, October 10, 2018 11:09 AM
  • User-1578974752 posted

    Almost all other errors were solved with the help of the link you provided.Thanks

    Thursday, October 11, 2018 9:13 AM