Archive for January, 2010:
Written on January 22nd, 2010 by viliyana89no shouts
User creates a new Web page named Private.htm for the Web application. He saves the Web page in the C:\Inetpub\wwwroot folder on his computer. Private.htm should be accessible only to users who provide a valid user name and password. Other pages in the Web site should be accessible to anyone. Using his Web browser, user can access Private.htm without providing a user name or password. You need to ensure that users are required to provide a valid user name and password in order to access Private.htm.
We must allow anyone access the Web site. The only exception is the private.htm file that should be accessible only to users who provide a valid user name and password. We accomplish this by setting the appropriate NTFS permissions, the security permission, on the file private.htm. In this scenario the anonymous access check box on the Web site properties dialog box is selected. This permits people to access the Web site anonymously without any form of authentication.
Note: By using permissions we will prevent unauthorized people from access the Web site. Permissions rely on and Access Control List (ACL), which contains a list of all user accounts and groups that have been granted access to the Web site as well as the type of access that they have been granted. When a user attempts to gain access to the resource, the ACL must contain an entry for the user account or a group to which the user belongs. The entry must allow the type of access that is requested by the user before that user can gain access to the resource. If the access control entry does not exist or the entry does not match the type of access the user requests, the user will not be granted access to the resource.
Filed under Network Connection, Windows
Tags:access, Access Control List, ACL, annonymous, NTFS permissions, password, permission, permissions, user name, web application, Web browser, Web page
Written on January 16th, 2010 by viliyana892 shouts
After upgrade from Windows 2000 to Windows XP Professional, the user reports that he cannot change his Display settings to anything other than 640 x 480 resolution with 16 color. You verify that this computer has the same video hardware as all the other client computers. You also verify that the hardware vendor does not currently offer a video driver for Windows XP Professional. You need to enable the user to change his Display settings to higher resolution and color quality. What should Install the Windows 2000 Professional version of the video drivers on the computer.
The computers that are using Windows XP are working properly but the new computer did not. This suggests that the Windows XP installation CD does not have drivers for the video adapter and that the upgraded computers are still using the Windows 2000 drivers. It also suggests that the Windows 2000 driver is compatible with Windows XP Professional and that we could therefore use the Windows 2000 video adapter driver on the Windows XP Professional computer.
Written on January 14th, 2010 by viliyana89one shout
When the client computer cannot contact the DHCP server for IP address configuration, Windows XP uses APIPA (Automatic Private IP Address) for IP configuration. This allows the client computer to communicate with other computers and printers on a single subnet. APIPA uses the private IP address range of 169.254.0.1 through 169.254.255.254 and a subnet mask of 255.255.0.0. 169.254.96.107 is thus an APIPA address that was assigned by Windows because the computer did not receive an IP configuration from a DHCP server. By running the Ipconfig /renew command we will force the computer to attempt to contact the DHCP server again so that it renew the client IP configuration.
Written on January 11th, 2010 by viliyana89one shout
You have just set up a new Windows XP Professional computer at home. The computer is always connected to the internet via an ADSL modem. The computer is configured to have a static IP address assigned by your Internet Service Provider. You enable the Internet connection Firewall on the ADSL connection. You use the Ping command on your office computer to try to connect to your home computer. However, you receive the following error message: “Request timed out.”
The ping command sends a series of ICMP echo requests to the specified computer. However, the ICMP echo requests are being dropped by the firewall and are therefore not reaching the specified computer. We need to configure the firewall to allow the ICMP echo requests so that they can pass to the specified computer.
Filed under Network Connection, Windows
Tags:ADSL connection, computer, error, Firewall, ICMP, Internet Service, IP address, ping command, Professional, Request timed out, Windows XP, Windows XP Professional
Written on January 7th, 2010 by viliyana89no shouts
A user is attempting to open a Microsoft Word document Phonelist.doc by using Internet Explorer. However, when he types http://Server1/Files/Phonelist.doc into the address bar in Internet Explorer, he receives the following error message: “404: Page not found.”. You verify that Phonelist.doc exists in a shared folder named Files on Server1. You need to ensure that user can access Phonelist.doc by using Internet Explorer. What should you do?
The error message 404 indicates that the Web page cannot be located at the URL address specified by the user. This is because the user specified a Web server address, which is denoted by http:// in the URL. He should use file:// in the URL to specify a file server. The correct URL for opening the file with a Web browser in this scenario is file://server1/File/Phonelist.doc.
Written on January 4th, 2010 by viliyana89one shout
You need to establish a Remote Assistance connection with Michael’s computer. What should you do next? The right answer is to ask your firewall administrator to open the TCP/IP ports that are used by Remote Desktop Services.
The problem in this scenario is that the firewall is blocking the Remote Desktop Protocol port 3389. Remote Assistance uses the Remote Desktop Protocol port 3389 for outbound RDP traffic. This port is typically blocked on most firewalls, in which case we cannot connect to the Remote Desktop. We must configure the firewall to enable Remote Desktop Services program, which is Mstsc.exe, to make outbound TCP connections on port 3389.
Written on January 1st, 2010 by viliyana89no shouts
The network consists of a single Active Directory domain. The network includes Windows 2000 Advanced Server computers, and Windows 2000
Professional and Windows XP Professional client computers. Except for the domain controllers, all computers on the network use DHCP for their TCP/IP configuration. Users begin reporting that when they try to access resources on File Server, they receive the following error message: “Network path not found.”
The likely problem in this scenario is that when the file server was restarted, it received a new IP address. When a user connects to a server using a user-friendly name, DNS resolves the user-friendly name to an IP Address that is then used to connect to the server. This name-to-IP address resolution is then stored in cache on the user’s computer so that when they attempt to connect to the same server, they do not have to use DNS. The DNS cache on the users’ computers has the old IP address for the file server. Thus, when the client attempts to contact the file server it is using the wrong IP address that it has cached. The /flushdns switch of the Ipconfig command flushes the list of locally cached DNS names.