my Questing is about Server networking?
353403
yes you can.\n\n1) each pc on your network you need to give a set ip address, as most routers give each computer an ip address when the computer starts up.\n\n2) in your router setup you would have to also look at port fowarding, this so outside world requests can get thorugh to a specif machine, you should have some already pre set but not operation, i have a linksys, i give an app name such as http, set the external port to 80, internal port to 80, it will ask for an internal ip address. this would be the ip of your web server in my case 10.0.0.3 and save changes.\n3) you would then need some sort of dns lookup service. if you join no-ip.com which is free, then go to download there software onto your web server. my site is shoey.no-ip.info (its not up as im upgrading my server) then this will keep no ip up to date with your connection.\n4) you would follow similar processes for setting up ftp etc\n\nthis is only a really rough quick, guide. if you e-mail me what router you got, id be able to give you something a bit more to your settings
167559
do you mean domain name server???\n\nIt resolves IP addresses to alphanemeric names
670609
That is a question which requires a hugh amount of time to answer.  You'd do better to just start searching the web for information on networking.  Also, "network" is something of an ambiguous term. Are you referring implementations of OSI?
1007971
you didn't  write if you will be connecting from client pc or what ever.\n\nanyways\n\n if your client os/computer is to be registered with domain\n\nInstall windows 2000 Server or 2003 \n1:-    Install routing and remote access\n2:- install terminal services\n\nsetup a vpn at isp( freely setup by isp, dsl provider)\n\nnow you can connect to you server from you client pc using ip address. \n\nopen a terminal windows/ give ip of your server/users name/password\nyou will be able to see the destop of your server as it is on your on pc\nenjoy running applition or what ever you like.\n\n\n if your client os/computer is not to be registered with domain\n\nsetup a vpn at isp( freely setup by isp, dsl provider)\n\ninstall any remotly anywhere software eg. symantec anywhere/ vnc viewer at both ends (server and client)\n\nrun remote viewer / give ip and password\n\nyou are connected to you server.\n\nGood Luck
628281
You computer can not locate the server due to a network or LAN failure...\n\nXLMan
623937
Look at what other providers can supply.  Are you going to hve guaranteed server up time?  What about back-ups of the data should a server go down or the data is lost?  If you are offering a special service for weddings you have to make sure it is perfect - this is a special day for people and if you mess it up you will not get much business.  Get it right and you will get lots.  Price in itself isn't normally an issue, it's value for money.  If you provide excellent quality and services, you can charge more.\n\nHope that helps
1039496
If you are in a Windows operating system do the following.\n\nstart -> run -> cmd -> enter -> tracert -> type the domain name -> enter\n\nit'll then try to find the fastest route to the server. if it encounters and unusually long pings along the way then that tells you the problem is not with your server. If it timesout at your server though then... well it is your server.
523892
you need to run the applications on the PC you consider as server, give it IP address then tell your DNS that this name map to this IP.\n\nopen ports for "others" that the applications will recieve requests through.\n\ntry to connect from one computer to the server.\n\nHave Fun!
490653
Check the network settings and server settings.
640566
get a good QoS software and limit all traffic but that on port 25 to 0kbps\nunless you are talking about webmail, then you have to let http through (port 80)\nand pop3: port 110\nhttps: 443\nvarious http servers: 8080\n\nhave fun
1109637
Get a connection from some if the ISP's that the previous asnwerer has told you. \nIf you need to know how its done, google for DHCP.
328743
on an NT 4 network?  not unless you have some sort of remote desktop software like pcanywhere on it.  then you could bring up the DHCP management console and check the settings.  NT4 dosent use MMC so you couldnt install the DHCP server plugin like you could in a 2k or 2k3 enviroment.\n\nhe said from the client, not the server
81287
In simple terms: \n\nA server is a powerful computer that serves, i.e. performs some sort of task, for other, usually smaller, computers attached to it via cables or phone lines. These smaller computers are called clients.\n\nHere's an example: When you're at home browing the web, your computer, or to be picky your browser software, is the client and it connects to a server via your phone line. When you want to view a web page or download a file, your computer (client) contacts the server and asks it to fetch the page or file and send it back to you. Simple.
1066903
1.What kind of network setup do you have?.\n2.Is there any Network monitoring system deployed?\n3.Are there any QOS policies implemented.?
790793
This is a multi-threaded server.  Much like a web server could do.\nFor comparison, the previous slide is a single threaded server.\n\nThe loops you are interested in are act as such.\nThe server starts and waits for a connection request from a client.  (Upper right yellow box).\nNext: Someone (like you or me) starts our client application (browser) which connects to the awaiting server.  (Dotted line that enters under the upper right yellow box).\nWhen the accept(...) happens, server creates a 'socket' (not shown).  This server fork() 's off (creates) a thread (process) [center right yellow box] that accepts the socket (not shown) and uses the socket to open an input and output channel which connects to the client (not shown).  This whole thing is generally a very fast operation.  That action is done for this client, so it loops waiting for another client to connect.\n\nBack to the client.  Remember, the last thing the client did was connect to the server.  Now the client wants to make a request (write() ) to the server for information.  This is the left yellow box.  It 'requests' and the server 'read()' the request.  Processes it, write() the response back to the client which read()'s the message and does what it needs to do.\n\nThe Client yellow box, and lower Server (client server) yellow box keep repeating (that's the loops) until the client is finished with all its requests.  A good client may send a 'bye' message to the server, so it can cleanly exit.  Other times just having the client exit, drops the I/O connection to the Server thread, which recognizes that action as the client exited, and that server thread exists.\n\nHope this helps.\n=mike
153536
you need 3 nic card network interface cards 2 in one that would be your server and 1 in the other and run a dsl cable tot he other machine from the second card tot he one card. then run the network set up wizerd on both machines and tell it how it will connect.\n\nyou can also do a router run a cable streat from your dsl modem to the router. and then branch off from there   that that has more room for expansion if you ever get a 3rd computer
660668
If you want a server to remain stable and have close to 24/356 uptime, you don't want a Windows server. If the Windows clients will be like dumb terminals, you might need to put some work into getting your clients to work with your non-Windows server, but for most purposes...\n\nLinux all the way.\n"Know-how" isn't even required if you use Fedora Core, Red Hat Enterprise Linux, or SUSE (among others), and their graphical server configuration tools.