answersLogoWhite

0

Windows Server 2003

Also known as the Win2K3, Windows Server 2003 is a server OS (operating system) from the American software company Microsoft. This OS has the capability to share printers and files, provide email services, authenticate users, and host message queues.

1,215 Questions

How can one check server uptime in WIndows 2008?

There are seven simple ways to check server uptime in a Windows 2008. One way is to check under the performance tab in the 'Task Manager', another is typing 'systeminfo' in 'Command Prompt'.

When replicating information between sites Active Directory will designate a bridgehead server in each site to act as a gatekeeper in managing site-to-site replication?

if you have not selected any DC as bridgehead server then it automatically follows ISTG - InterSite Topology Generator,chooses its own DC to replicate and if this link is down makes another but if you define bridgehead server,in that case if the link fails the replication stops.

Why is port 1050 on my computer open?

I can think of two possibilities. I assume since you are asking specifically about Port 1050, that you have a software firewall or a NAT based firewall.

Taking a leap into the darkness, is your router by any chance the Netcomm NB5Plus4W as that has a manufacturing defect that causes the port to be open. See the guide guide for port forwarding to close your port if this is your router.

http://randompastime.blogspot.com/2010/01/netcomm-nb5plus4w-router-port-1050-open.html

It could be malware opening up your port or it could be your firewall.

The authentication protocol used by windows 2000 and later computers in a domain is called?

LDAP (Lightweight Directory Access Protocol ) is a protocol that is used for authentication in domain

What is the authentication protocol used in 2008?

The Windows operating systems implements a default set of authentication protocols-Kerberos, NTLM, TLS/SSL, Digest, and PKU2U-as part of an extensible architecture. In addition, some protocols are combined into authentication packages such as the Credential Security Support Provider (CredSSP), Negotiate, and Negotiate Extensions. These protocols and packages enable authentication of users, computers, and services; the authentication process, in turn, enables authorized users and services to access resources in a secure manner.

Windows authentication protocols are conventions that control or enable the connection, communication, and data transfer between computers in a Windows environment by verifying the identity of the credentials of a user, computer, or process. The authentication protocols are security support providers (SSPs) that are installed in the form of dynamic-link libraries (DLLs).

Negotiate

Microsoft Negotiate is an SSP that acts as an application layer between the Security Support Provider Interface (SSPI) and the other SSPs. When an application calls into SSPI to log on to a network, it can specify an SSP to process the request. If the application specifies Negotiate, Negotiate analyzes the request and selects the best SSP to handle the request based on the configured security policy.

Currently, the Negotiate SSP selects either the Kerberos or NTLM protocol. Negotiate selects the Kerberos protocol unless it cannot be used by one of the systems involved in the authentication or if the client application did not provide a target name as a service principal name (SPN), a user principal name (UPN), or a NetBIOS account name. Otherwise, Negotiate will select the NTLM protocol.

A server that uses the Negotiate SSP can respond to client applications that specifically select either the Kerberos or NTLM protocol. However, a client application must first query the server to determine if it supports the Negotiate package before using Negotiate. (Negotiate is supported on Windows operating systems beginning with Windows Server 2003 and Windows XP.) A server that does not support Negotiate cannot always respond to requests from clients that specify Negotiate as the SSP

Kerberos

:The Kerberos version 5 (v5) authentication protocol provides a mechanism for authentication-and mutual authentication-between a client and a server, or between one server and another server

NTLM

The NTLM version 2 (NTLMv2) authentication protocol is a challenge/response authentication protocol. NTLM is used when exchanging communications with a computer running Windows NT Server 4.0 or earlier. Networks with this configuration are referred to as mixed-mode. NTLM is also the authentication protocol for computers that are not participating in a domain, such as stand-alone servers and workgroups.

Negotiate Extensions

NegoExts (NegoExts.dll) is an authentication package that negotiates the use of SSPs for applications and scenarios implemented by Microsoft and other software companies. Pku2u.dll is one of the supported SSPs that is installed by default, and developers can create custom providers.

PKU2U

The PKU2U protocol in Windows 7 and Windows Server 2008 R2 is implemented as an SSP. The SSP enables peer-to-peer authentication, particularly through the Windows 7 media and file sharing feature called Homegroup, which permits sharing between computers that are not members of a domain.

Credential Security Support Provider

Windows Vista introduced a new authentication package called the Credential Security Support Provider (CredSSP) that provides a single sign-on (SSO) user experience when starting new Terminal Services sessions. CredSSP enables applications to delegate users' credentials from the client computer (by using the client-side SSP) to the target server (through the server-side SSP) based on client policies

TLS/SSL

The TLS/SSL protocols are used to authenticate servers and clients, and to encrypt messages between the authenticated parties. The TLS/SSL protocols, versions 2.0 and 3.0, and the Private Communications Transport (PCT) protocol are based on public key cryptography. The secure channel (Schannel) authentication protocol suite provides these protocols. All Schannel protocols use a client/server model and are primarily used for Internet applications that require secure Hypertext Transfer Protocol (HTTP) communications

Digest

The Digest authentication protocol is a challenge/response protocol that is designed for use with HTTP and Simple Authentication Security Layer (SASL) exchanges. These exchanges require that parties requesting authentication must provide secret keys.

How does a RODC differ from a normal domain controller?

RODC has Read only NTDS.Dit file & other hand Domain controller(ADC & DC) have read & write NTDS.Dit file.

Replication is only one way.. DC to RODC

Amit Tripathi

Annik SAT

Describe the steps taken by the client and DHCP server in order to obtain an IP address?

Firstly, a DHCP server is needed which distributes the IP addresses. This machine will serve as a base for all DHCP requests and must also have a fixed IP address. Therefore, on a network there can only be one machine with a fixed IP address, the DHCP server.

The basic communication system is BOOTP (with UDP frame). When a machine is turned on, it has no information on its network configuration, and there is nothing special that the user needs to do to find an IP address. In order to do this, the technique used is the broadcast: to find and talk with a DHCP server, the machine will simply send a special broadcast packet (broadcast on 255.255.255.255 with other information such as the type of request, the connection ports, etc.) over the local network. When the DHCP receives the broadcast packet, it will send back another broadcast packet (do not forget that the client does not obviously have the IP address and that therefore cannot be connected to directly) containing all the information required for the client.

It could be believed that one single packet is enough for the protocol to work. In fact, there are several types of DHCP packets likely to be issued either by the client for the server(s), or by the servers to a client:

DHCPDISCOVER (to locate available DHCP servers)

DHCPOFFER (server response to a DHCPDISCOVER packet, which contains the initial parameters)

DHCPREQUEST (varied request from the client for example to extend its lease)

DHCPACK (server response which contains the parameters and IP address of the client)

DHCPNAK (server response to indicate to the client that its lease has expired or if the client announces a bad network configuration)

DHCPDECLINE (the client announces to the server that the address is already in use)

DHCPRELEASE (the client releases its IP address)

DHCPINFORM (the client requests local parameters, it already has its IP address)

The first packet issued by the client is a DHCPDISCOVER type packet. The server responds with a DHCPOFFER packet, particularly in order to submit an IP address to the client. The client establishes its configuration and then makes a DHCPREQUEST to validate its IP address (a broadcast request since DHCPOFFER does not contain the IP address). The server simply responds with a DHCPACK with the IP address for confirmation of the allocation. Normally, this is enough for the client to obtain an effective network configuration, but it can be longer or shorter according to whether the client accepts the IP address or not.


Hope this will help you to understand DHCP.

Regards,
Jaydeep.Gatlewar@gmail.com

Find the broadcast ip address network 200.100.100.0?

first u have to LOVE visual basic programming then search in http://www.planetsaourcecode.com .This will involve basically having/calculating the subnet then you will be able to calculate your broadcast ip address.

Can Windows 98 computers can have a computer account in a Windows Server 2008 domain?

Only computers running Windows NT or later can have a computer account in a Windows Server 2008 domain; Windows 9x computers cannot. Since Windows 98 came out after Windows NT, the answer is yes. -Brandon

What are the components of DNS?

DNS COMPONENTS:

The DNS consists of three components. The first is a "Name Space" that establishes the syntactical rules for creating and structuring legal DNS names. The second is a "Globally Distributed Database" implemented on a network of "Name Servers". The third is "Resolver" software, which understands how to formulate a DNS query and is built into practically every Internet-capable application.

(A) Name Space:

The DNS "Name Space" is the familiar inverted tree hierarchy with a null node named "" at the top. The child nodes of the root node are the Top Level Domains (TLDs)-.com, .net, .org, .gov, .mil-and the country code TLDs, including .jp, .uk, .us, .ca, and so forth. Node names, known as labels, can be as many as 63 characters long, with upper- and lower-case alphabetical letters, numerals, and the hyphen symbol constituting the complete list of legal characters. Labels cannot begin with a hyphen. Upper- and lower-case letters are treated equivalently. A label can appear in multiple places within the name space, but no two nodes with the same label can have the same parent node: A node name must be unique among its siblings.

(B) Name Servers:

The second key component of the DNS is a globally connected network of "name servers". Each zone has a primary or master name server, which is the authoritative source for the zone's resource records. The primary name server is the only server that can be updated by means of local administrative activity. Secondary or slave name servers hold replicated copies of the primary server's data in order to provide redundancy and reduce the primary server's workload.

Furthermore, name servers generally cache data they have looked up, which can greatly speed up subsequent queries for the same data. Name servers also have a built-in agent mechanism that knows where to ask for data it lacks. If a name server can't find a domain within its zone, it sends the query a step closer to the root, which will resend it yet a step closer if it can't find the domain itself. The process repeats until it reaches a TLD, which ensures that the entire depth of the name space will be queried if necessary.

The combination of all the DNS name servers and the architecture of the system creates a remarkable database. There are more than 32 million domain names in the popular TLDs for which the whois utility works. Nominum, whose chief scientist, Paul Mockapetris, invented DNS, claims that there are more than 100 million domain names stored and that the system can easily handle 24,000 queries per second. The database is distributed-no single computer contains all the data. Nevertheless, data is maintained locally even though it's distributed globally, and any device connected to the IP network can perform lookups. The update serial number mechanism in each zone ensures a form of loose coherency on the network-if a record is out of date, the querier knows to check a more authoritative name server.

(C) Resolver:

The third component of the DNS is the "resolver". The resolver is a piece of software that's implemented in the IP stack of every destination point, or "host" in IETF-speak. When a host is configured, manually or through DHCP, it's assigned at least one default name server along with its IP address and subnet mask. This name server is the first place that the host looks in order to resolve a domain name into an IP address. If the domain name is in the local zone, the default name server can handle the request. Otherwise, the default name server queries one of the root servers. The root server responds with a list of name servers that contain data for the TLD of the query. This response is known as a referral. The name server now queries the TLD name server and receives a list of name servers for the second-level domain name. The process repeats until the local name server receives the address for the domain name. The local server then caches the record and returns the address or other DNS data to the original querier.

How often do you run computer network security?

If a computer system is operating then it should be utilizing network security. So the answer would be all the time.