Question Locked

how to install a switch and windows server 2003

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

our company has an old server with two hubs, and we are going to install a switch in place of the hubs and a windows 2003 server. Our internet is through the state, and comes in from their router. I've never worked with a switch..so..does the server we are going to use cable to the switch? Does the incoming internet cable connect to the switch as opposed to the server? I think I know, but want to make sure. Once I have the server and internet correctly connected to the switch, I should be able to run the server software through and convert the connections for tcp/ip from the old one without a problem..

Sorry, very new at this.

8 replies

by clarkd038

A network switch is a broad and imprecise marketing term for a computer networking device that connects network segments.

Plug the internet into the switch and then plug the server into the switch.

by cinn

I have done this step, and configured the tcp/ic settings on the server to the beginning range our network has. I cannot figure out how to access the switch to configure it?
Telnet doesn't seem to give me anything but a blank screen, although it says it's connected, and I can't access the internet on the server, nor can I find in the documentation what the ip address for the switch would be? I'm assuming I can't get the internet from the server because the switch isn't configured for our ip range yet.
Tried the default 192.168.1.100 and similar with no results

by cinn

internet is in from our state router and plugged into switch
server is plugged into main port on switch, and tcp/ip is configured to the range of ips that our state router is assigned to

by cg it

not all switches are managed switches that provide you with different configuration options.

I don't know of a switch, managed or unmanaged that requires any configuration to work. They all work if you plug it in, turn it on and connect devices to it. A managed switch just provides more configuration options that the basic switching capabilities.

Just guessing here but your problem isn't the switch, rather how your internet service is connected to your network.

Do you have a router [company or individual owned] that is connected to your internet service and provides NAT addressing for your private network?

by cinn

the state has routers that provide a internet connection to each agency. That cable is plugged into the main port on the new switch. (Its a managed linkysy switch and gives details on configuring, but I can't get to the configuration screens). The cable worked on our old hubs and the old novel server was plugged into that....

So, I have unplugged the internet cable from the old hub and plugged into the new switch. I have plugged the new windows server into the new switch. I have been told that I now need to configure the switch to accept our range of ips that were given to us by the state and are used on the various machines that will be connected to the new switch. The internet cable works fine when hooked to the old hubs, etc, but doesn't allow anything to connect to the internet when connected to the switch.

by cg it

get an address by default from DHCP. you can get that address via the DHCP server.

So, someone at "State" ought to be able to see your switch on the network and give you the address it was assigned. "State" also should have given you the necessary subnet information you will need to configure hosts on your network.

Without this information, you can't "logon" to the switch or configure it without doing a little bit of jury rigging which isn't going to help you configure the switch but will let you logon to it.

All this assumes your using the SPE series Linksys managed switches.

note: here's a hint....the linksys switches get an address from DHCP so you need a DHCP server. if you don't have one, you can get one by using a consumer level router which has DHCP server enabled by default.

word of caution: I'd disconnect all production equipment from the switch before I connected a consumer level router to the switch. hate to have to do a ipconfig/release on each and every production equipment host

Last but not Least: how come "State" didn't configure the switch before they sent it to you? Bad planning on their part

This discussion is closed to new replies.