use of Windows server 2003

ok,let me narrow the question a bit...:-)
ok,I can host asp.net applications in windows XP itself...
so why do people provide hosting only in windows 2003? why not in XP?

Thanks

One of the simplest reasons is that Server operating systems are designed to utilize and use the hardware functionalities that are normally not available in ordinary desktops. For example, Server RAIDs, Multi GB RAM, Multi Processors, multiple Network Cards etc etc.

Another one is Financial one for Licensing purposes.

Actually, the simplest answer is, because Microsoft limited XP to 10 simultaneous connections.  Microsoft placed various limitations on XP and on IIS in XP.  To better accomodate those that just wanted web hosting abilities, Microsoft released a Web Server version of 2003.

DHCP and DNS aren't possible with windows XP? well,i use DHCP with windows XP.
Im not sure what is active directory

Leew,Thanks for that man.
So,there is some difference between a normal dhcp and MICROSOFT DHCP AND DNS? right?

Thanks,

Godwin

TECHNICALLY - DHCP and DNS are services.  Clients NEED DNS if they are to browse internet sites by names - DNS translates names into numbers.  Your workstation must either run a DNS Server OR it must be told WHERE a DNS server is.  Think of DNS like a Phone book, taking the name you're looking for and finding it's number.  If you don't have your own set of phone books, you call another person (information) and ask them the number for so-and-so.

DHCP is a method of assigning networking information to a workstation.  Every workstation that's going to access the internet needs to use TCP/IP.  TCP/IP requires several things to be setup - including DNS server information, it's own potentially unique address, a "gateway" address (think of it as a doorway to the internet - without the gateway, you can talk to everyone else in the building but nothing outside).

Like DNS, a server must be preconfigured with a range of addresses and the appropriate settings for computers on the network.  Then your client workstation contacts this server (by kinda shouting out "Hey, I'm on, Give me my own phone number and an exit to the internet" - The DHCP server hears this request and gives the workstation the requested information).

As for differences between RFC standards and Microsoft, not really and yes.  Microsoft DHCP (at least in 2000) did seemingly have a problem giving addresses to Solaris 2.6 (I THINK that's the version we were having trouble with).  But all other systems, Linux, Macs, other versions of Windows, they all worked just fine with Microsoft DHCP.  Microsoft's DNS is supposedly RFC compliant, but can also integrate with Active Directory which could help make it more redundant if you have multiple domain controllers and DNS servers.  That aside, Microsoft networks running Active Directory REQUIRE a DNS server that's Dynamic DNS compliant.  NEWER versions of third party DNS servers are USUALLY Dynamic DNS compliant and COULD be used, but in my opinion, so you can have a "single point of contact" in the event of problems, I would use Microsoft DNS.

Thanks for the assist points...always a pleasure.