Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Name: vande
Ok so i have had win2003 for some odd years now i finally set it up so now you can log into the domain i created. I have taken a associates in network administration and now can see there are many more options just by creating a domain. Now its a simple AMD 2.2 with 512 of RAM and boy is my dual xeon comp 2 gig memory taken some time to connect. You think its just because of the AMD 2.2 with 512 RAM on server? Its just hangin on applying comp settings
Got my associates in network administration
that doesn't say much for me :
What's your DNS like - lengthy logon times typically are caused by incorrect DNS settings. Some of the information my DNS links might prove useful to you - see:
http://www.lwcomputing.com/tips/sta...
0 
"can see there are many more options just by creating a domain"
Domains are a subset of the Forest. You get options due to the Forest which is the basis of Active Directory.
512ram for the server is too little. Really should have your dual zeon system be the server and the amd the workstation.
Imagine the power if you knew how to internet search
0
Well i know i know i should have server on dual xeon but maybe after i can get comfortable with using win 2003 i can do this. I created a new forest considering this was my first DNS setup and first server setup.
How about this i got many server2003 DNS,Active directory books, E.T.C. from school. I setup a domain and connected to it, just took about an hour lol to login via the profile created on server. What would you suggest is my next step? DNS for sure?
Got my associates in network administration
that doesn't say much for me :
0
You need to properly configure dns so yes that would be your first stop.
Imagine the power if you knew how to internet search
0
Ok so my DNS right now is my router DNS or my ISP i guess you would call it so i guess i understand what DNS does resolves ip to hostname? but why on a network with 4 or 5 computers is that important? After clients leave my network for DNS it goes to the ISP DNS so i mean i dont have to set up a big DNS like the ISP so whats the point eah it might be a little quicker but . So i guess what im asking is what does DNS solve for me on such a small network?
Got my associates in network administration
that doesn't say much for me :
0
Your isp's dns server can't know about your workstations or anything on you lan for that matter and never will.
Vande you really need to spend some time in your 2003 server book in the section concerning DNS configuration.
Reviewing that will explain why you want your intranet dns server configured properly to handle local name resolution and forward any internet name resolutions to your isp's dns server.
Imagine the power if you knew how to internet search
0
Well i have i mean i do agree it wouldn't hurt to crack them back open but my view on DNS is it helps with speed and what i mean by that. It already knows the ip to www.yahoo.com that is what DNS does you could however put www.IP.com to yahoos ip and get there but DNS solves this problem. My question is is why should i worry on such a small network it isn't gonna save me that much time ? or maybe im wrong
Learning in progress..........
0
Ok i just was reading about DNS being a phonebook in theory and i kindda understand but let me ask the question. If my computers are using my ISP DNS why would i need one? Except for it will resolve my computers on my domain by name? right? What about this will the DNS start to store information? What i mean is say i goto yahoo.com on one of my clients will it look at my Server DNS and if it cant find it it tries ISP next right? Well if ISP finds it will it be stored on my server so next time client does not have to resort to ISP DNS it can just goto mine
Learning in progress..........
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
