Zum Hauptinhalt gehen

Site is blocked for some users, but available for others

Kommentare

3 Kommentare

  • Permanently deleted user

    Hi, Mick,

    I had opposite situation for our test sites. I could view my test application at work, but it stopped working from home. It turned out that our IT department restricted access to a certain known users from external to the test server. Otherwise didn't have access to the application.

    Out IT uses whitelist to control the sites and applications. I won't allow to run certain application unless they are whitelisted.  

    Not sure if your users has similar problem. May be they should check with their system admin team to rule out the blocking issue. 

    Helen

    0
  • Permanently deleted user

    Hi Mick

    maybe you need to look at installing Fiddler on both a 'sucessful' machine and and 'unsucessful' machine and see if there is any difference in the requests they are making and what url's they are using. What proxy/firewall is each set up to? Are they identical in that regard?

    Just a couple of thoughts

    Regards

    Ralph

    0
  • Permanently deleted user

     

    Thanks Helen and Ralph for your replies.

    I have tried a few more things based on your ideas.

    Running the site from my side with Fiddler shows everything going as expected.  Unfortunately, getting Fiddler onto one of the problem machines has proven problematic.  Because the people having the display issues are 'general public', I have not been able to get anything from them from fiddler. 

    One user did send me a tracert result, which indicates that the request timed out.

    We don't have a whitelist for this server, as it is publicly facing, but it does appear that certain IPs are being 'shunned'.  I'm no IT person, but this apparently is different to being on a blacklist.  It also seems that it occurs when requests from a network are NAT'ed to a single IP address.  The logical explanation is that there has simply been too many hits from these IPs, which has caused the servers threat detection to kick in, but I suspect that these users have hit the site while something was down (or updating), and then hit it again and again repeatedly.  I'm hoping the Server support will be able to resolve it!

    Thanks again for your replies

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.