HTTP 403.6

  • Thread starter Mike Honeycutt, MCSE
  • Start date
M

Mike Honeycutt, MCSE

I have a site that is having an issue getting to a specific website. Any
Windows 98 system connects just fine but all of the Windows 2000 & XP
systems receive this error.

They are connected to the internet via T-1 and use NAT thru a WatchGuard
Firebox III 500. I have watched the Firebox logs and don't find an issue
there. A Win2k server handles DNS for all of the internal clients, so I
would not think DNS is an issue.

Every thing I have found for that error indicates it is on the hosting end,
but the site is hosted by a fairly large commercial service and you can get
to it from 2000 & XP from outside of that site.

Any thoughts or suggestions.

You are not authorized to view this page
You do not have permission to view this directory or page from the Internet
address of your Web browser.

If you believe you should be able to view this directory or page, please
contact the Web site administrator by using the a-mail address or phone
number listed on the www.domain.com home page.
HTTP 403.6 - Forbidden: IP address rejected
Internet Information Services
Technical Information (for support personnel)
Background:
This error is caused when the server has a list of IP addresses that are not
allowed to access the site, and the IP address you are using is in this
list.
More information:
Microsoft Support
 
R

Robert Aldwinckle

all of the Windows 2000 & XP systems receive this error.

Take a packet trace. Is the message really coming from the site?
Then the explanation for the symptom is at the site.
Is the request that the NT boxes send identical to the request that
the W9x boxes send? (No. Due to User-Agent but if you want
you could simulate either box being the other type by sending the
wrong User-Agent (or test by using a different browser or telnet).)


Otherwise you must have compromised tcp-ip stacks
on all of your NT5 boxes. ;o

FYI for XPsp2 there is a new repair command for the latter possibility:

netsh winsock reset

Otherwise there is

netsh interface ip reset

You might try checking for abnormalities beforehand by

netsh winsock show catalog type=LSP

ipseccmd show filters

(ipseccmd is on the XP Pro Support Tools)


BTW you may get better suggestions in a newsgroup
which specializes in networking for your OS.


Good luck

Robert Aldwinckle
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top