|
|
| tetragamon 2003-04-30, 10:03 am |
| Hi All
I came across this question which I could not agree with 100% and it has been nagging at me for a few days. I hope someone can put my mind at rest with an authoritive answer.
The Qestion is...
quote:
Your Web server is configured to run a third party Web application for
users on your network. Users complain that each time they try to connect
to a secure Web page stored on the Web server, they receive the error
message "Web page requested is not available". They have no problem
connecting to FTP.
You have verified that the Web service has started. What should you do to
diagnose this problem?
a. Verify that port 443 is permitted in your TCP/IP filter.
b. Verify that port 80 is permitted in your TCP/IP filter.
c. Verify that port 21 and port 20 is permitted in your TCP/IP filter.
d. Verify that the correct NTFS file permissions are configured for the
web page.
Now the answer is supposed to be (a) and I understand the use of port 443 but I am not convinced that this error message is the correct one. I am concerned that (d) may be a better answer. I might expect an error message that said that the server was unreachable or something else if (a) was the problem while I feel that (d) is a better answer for the exact error message given.
I would like a definitive answer of what the error message would be in case (a) and case (d) by doing the experiment myself but I do not have the setup for it.
Can anyone help?
Thanks Graham | |
| tetragamon 2003-05-01, 4:10 am |
| If I'm just being stupid please tell me. | |
| stepfaul 2003-05-01, 6:14 am |
| Although I am unable to test this. I would expect the 'page cannot be displayed' error to appear if port 443 was not permitted.
What error would you expect ?
Sorry this is not a definitive answer, but an opinion. | |
| Tech Ranger 2003-05-01, 7:22 pm |
| We can't know everything. I would answer "A". I would assume that the tester is trying to verify that I am aware of the relationship of secure web pages and port 443. | |
| prezbedard 2003-05-02, 10:49 am |
| I would also 'guess' 443
I don't think NTFS permissions can control who views pages on a web server. | |
| g_ricardo 2003-05-04, 8:35 am |
| Hi!
See it this way, you know that answers b&c
are not.. while d looks fine I don't know
any NTFS permition that will not let you
"display a web page" it may not let you
use the application or "deny" access.
so the only logical answer should be a. | |
| jacurry101 2003-05-04, 8:25 pm |
| Ok,
If you are an administrator of ther web server and you are able to pull up the secure page useing you name and no one else is, then permissions are the problem. This does not mean that the File permissions are the problem though. It could be permissions on the Secure site it self..
If you are unable to open the secure page as an administrator of the box then your SSL port (Port 443) is being plocken and you will need to get with the network group to resolve the issue..
JAC | |
| g_ricardo 2003-05-05, 12:29 am |
| I agree with that, you didn't mention if
the question is single or multiple choice..
so maby ans. a-d are both correct...
but in the other hand the question states
that the problem is on a specific page and
that changes my thinking about a port problem, and focuses more on a permission issue.
Rick. | |
| smithy4u 2003-05-05, 12:45 am |
| You say that you can connect it through FTP sessions, it means you there is no problem in NTFS permissions. | |
| mrdelete 2003-05-06, 6:06 am |
| HI ppl;
sure that the reason of the problem accessing a secure web page is port 443.
port 443 is used for secure web traffic (HTTPS).
that used only on intranet as the case above .
NTFS permission it will be a general solution with IIS and the message will be
( u are not authorized to view this page )
and if u leave that permission to default which is every one gonna access that web page .
the scenario state the users complain that they cannot access this page . i mean all users so it will be not a NTFS problem .
bye bye  | |
|
| It is definitely "A".
"B" and "C" are out for sure, and you can access this page via FTP, so it is not a permissioning issue. (Also, it states the request page is not available, it does not say anything about access being denied or not being permitted to view the page.)
HTH! | |
| g_ricardo 2003-05-06, 3:54 pm |
| Found it !!
check the entire article at this link:
http://support.microsoft.com/defaul...kb;EN-US;297954
in short:,
Users Can Access Web Server but Not the Contents on Web Server
Verify the Authentication and Encryption Levels on the Web Server
Right click the My Computer icon on the desktop, and then click Manage.
In the Computer Management dialog box, expand Services and Applications.
Double-click Internet Information Services.
Right-click the Web site, and then click Properties.
On the Directory Security tab, under anonymous access and authentication control, click Edit.
Verify that the correct authentication and encryption settings are set at the server.
Verify the Web Sharing Permissions
Right click the My Computer icon on the desktop, and then click Manage.
In the Computer Management dialog box, expand Services and Applications.
Double-click Internet Information Services.
Right-click the default Web site, and then click Properties.
On the Directory Security tab, under anonymous access and authentication control, click Edit.
Verify that the appropriate client access settings are set, such as the following permissions:
Read files
Write
Directory browsing
Run scripts
Rick | |
|
| Nice article but it does not address the fact that you can access via FTP but not HTTPS. If it was a permissioning issue, neither access method would work. |
|
|
|