Holding network setup

[MKKING]

I have manage to setup my home network despite the lack of instruction this semester by the networking class instructor. When I setup the network everything works fine. I can access other computers and the Internet from any of the other workstations and the server in my network, however, when I shut the network down for the night, the next morning it is as if nothing was ever setup. I have to build the network again from scratch. I am running XP Pro on all the computers (3 workstations and the server) as I said before all the features function fine all day, but after I turn the network off at night the next day nothing. Why is the setup not holding. I have set it up so many times now I can do it in my sleep. I have gone to the connectivity page and hit the repair connections button, but that does not repair the connections and I have to do the setup over again. Is there something I am doing wrong or a step I miss doing to make it hold the setup when I shut down? Please help because the next semester the course is called Network Administration, and I want to be prepared due to the lack of significant instruction by the instructor. Yes, it is the same guy. I have learned more at home in the last two weeks than I did from him the whole semester. I failed to mention, they made us by a server for $700 and build it in class, then we started the network applications. The labs were not structured ( he would give us projects then leave the lab until the end of class time and come in and ask who was successfull), but the lectures and labs did not tie together. A very strange way of teaching networking I thought. Anyway, I am getting too wordy, just give the solution to my problem please.

[classicsoftware]

We need a whole lot more information:

Number of PC's

Server OS

Workstation OS's

How did you set it up, be specific.

Sharing a broadband connection?

Using a router or ICS?

[MKKING]

I am running 2000serverOS on the server and the other three workstations are running XP Pro. I setup the network using the Network wizard and the hub I am using is GigaFast Ethernet--EZ500-S 5 ports 10/100Mbps N-Way switch, as I said all the features are functioning when I set the network up initially. It is when I shut down that I lose everything. When I get back up and go to the connection page for the toubleshooting area I go to the repair button and it says it can't repair the connections. It is not holding the network after shut down. I am at a loss on what to do with making it hold the connections. If you need more information I will gladly provide it. Also, should I make a disk for the setup when I set the network up again instead of using the CD each time I set the network? Would that save me anything? Your advice is greatly appreciated.

[MKKING]

I have gotten no further response to my problem. Have I not answered the questions sufficiently, or am I posting my response to the questions in the wrong place. I have waited several days and nothing further seems to be forthcoming.

[KenGr]

Hi MKKING:

Let me ask you some more questions.

When you say you shut the network down does this include the server or just the workstations? If you only shut down the workstations does the sever have access to the internet?

If you set up the network connections on a workstation and reboot it will the network connections still be there?

When you have a problem like this you have to break your network down to as few a components as possible. It is sometimes the only way to isolate the problem. At this point I would set up the server and one workstation only.

[MKKING]

When I say shutdown I mean everything. Being a student I have moved back home with mother, which means following her rules, thus, that means to shut everything down at night before going to sleep. When I get up in the morning I have to fire up the whole system again, including the network setup. It is at this time I find I have to configure the network again. I go to the connectivity page and hit the repair button it says it cannot repair the connections because the IP address have not been assigned to the workstations. I have to completely go through the network setup again, so the addresses can be assigned again. This will hold until I shut the system down at night. All the operations function properly throughout the day. It is only when I shut down for the night that I lose the connectivity. The server continues the internet access even when any of the workstations are shut down, but I never shut any of them down until the end of the day. Since this is just a home network I didn't think I needed to have the system stay up 24/7. I am the only one in the house with the technical curiousity to invest the time to study the function of computer systems, the others use the computers with the minimum amount of effort and internet curiousity to answer a few things they have seen or heard about from others or tv. I am hoping to get the home network to a point where they can turn it on and go for themselves. They shouldn't have to wait for me to go through setup each morning. Thank you for your assistance, and if more information is needed from me, don't hesitate to ask. I want to learn as much as I can, and to have the confidence to assist others when they have problems much as you do. I am getting more from this site than I get from going to school. Some of the responses I have read from this site have given me so much more insight in computer operations than I have from the hours I have put in earning my degree. Thanks for all of you knowledgable people. Also, if you could recommend the most comprehensive book for a novice like me to read and reference for future issues that might come up.

[Variable]

You need to configure DHCP properly.

[deddard]

Hi MKKing
There's a link at the top of this page for certiguide.com, which is set up by our very own IXL. On here you will find numerous bits of information in a readable format - check out the Network+ section.
With your system, it would be helpful for us to clarify things.
1: Do you use a router to connect to the Internet, or is the Server configured to do the routing?
2: Are you using DHCP or Static IP addresses?
3: Is the Server 2000 set up as a Domain controller, or just as a standalone server? (what does the Server actually do for the network?)

If you don't understand any of this, don't worry, just say so and we can help you along. It sounds like your lecturer was a bit of a flake - Networking is tough enough without worrying whether you're going to have to study everything in the wrong order or upside down!
;)

[Variable]

I go to the connectivity page and hit the repair button it says it cannot repair the connections because the IP address have not been assigned to the workstations.
This statement tells you he is not using static addresses but DHCP on the clients. If the network is shut down and turned back on and has no connectivity with the above message it is a DHCP problem. The computer requests an IP and nothing is forthcoming. Hence, no networking.

[Erik]

What is acting as your DHCP server? I would guess it is the server running Windows 2000 Server, but it could also be a consumer router with built in DHCP.

Anyway you need to make sure that the device that is responsible for giving out IP addresses is fully up and running before trying to power on any other device. So if you are currently powering on everything at once that could very well be your problem. If your setup is anything like mine your client PCs will be asking for an IP address well before the server is ready to give one. Not a problem as long as you let the server boot up and get fully running before trying to power on any client.

[MKKING]

Ok Erik, that may well be the problem. I have no idea when they turn on their computers. Sometimes they knock on my door and say it is not working and sometimes I wake and turn on my server not know if theirs is on or not. I am not using a router but a hub. Yes I am confused by the way the instructor taught us. I am not really sure what I am doing just that the system works with what I am doing. I have found another book and I will construct the network using that instead of the textbook from the class. I seem to understand the new book better. I will let you know how things turn out. Thanks for all your suggestions and help on this problem. Will be back in a couple of days with my results.

[Variable]

/sigh That is not your problem, even if your DHCP server was fired up after all the pc's were turned on, if you go to a PC and repair the connection ( which you say you did ) it will request a new IP, the first thing it does is renew your DHCP addressing. If the DHCP server was operating correctly it would fix the problem. Since it did not, you can assume the DHCP server is not set up correctly or something is blocking the DHCP request/receive process. In order for a network to work using clients set to Obtain IP address automatically a DHCP server must be set up to give out addressing.

http://techrepublic.com.com/5100-1035_11-1041798.html#

[KenGr]

This is a rather small network, so maybe just setting up static ip addresses would be eaiser.

[Erik]

This is a rather small network, so maybe just setting up static ip addresses would be eaiser.

Yes, but it would also defeat the whole point. He is setting this up to learn about networking, and using static IPs won't help you get a job. Not many organizations use static IPs for end user PCs, just dedicated devices such as servers.

[KenGr]

You could set the network up initially with static IPs then after learning more about DHCP switch over. He is trying to learn on a functional(somewhat) network and not a test network. Sometimes a temporary workaround is appropriate.

You are absoultly correct Erik when you say organizations do not use statically assigned IPs for end-user workstations. The maintenace would be a nightmare. On my network the only static IP addresses are printers.

MKKING:
Here is an additional link:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/10112946-1204-4ff4-b52c-599c303135d1.mspx

[MKKING]

I would like to thank everyone for their advice. I read each carefully, and the certiguide.com questions. I then read the text for the initial networking class I took and was able to set the network over from scratch. It is now functioning correctly. The text is Windows 2000 Networking Certification Edition by Caudle-Glenn-Stewart. It is a MCSE guide. I am still not sure what the problem(s) was, but I now have a functioning home network. I can't thank you guys enough for you time and expertise. It must be very comforting to know that your knowledge and skill can help us poor novices to overcome what seems to us an insurmountable problem. Again, thank you all very much.