Currently I have a peer-to-peer network mostly win98 machines. We have a rough number of about 30
- 40 users. About 98% are in this office and we have pcs in two stores that currently do not view
our "corporate" network.
I am planning on transforming it from a peer-to-peer to a Client-Server WAN.
Currently I have a router, a firewall, 2 Hubs and 2 Switches. 1 Linux box which serves as our web
and email server. 2 Linux boxes -- one which can only be viewed by the employees in our corporate
office and in the two stores, and a second which is viewed publicly through telnet.
This setup was here before I arrived so I'm not fully sure about all of the details.
Our firewall is being managed by our ISP. I am also told that we have some VPN set up here which
is how the machines from the two stores are able to view that one linux box behind the firewall.
All of our machines in the corporate office have static IPs. That is part of the reason why I
want to go to a client-Server set-up.
I am not a network admin so I know very little about networking. I have some knowledge of trouble
shooting and connectivity. Originally, I had wanted them to have a certified company come in here
and take care of this, but it backfired on me and now it's on my lap.
Here is my question(s):
-What hardware (computers, components...etc), operating systems, software and other peripherals
will I need to do go from peer-to-peer to a client-server.
-I am aware that we'll have to purchase a server and the president wants it to be fully
redundant. What will I need to have on this server to make it be redundant, and what requirements
should the machine meet to be a usable file server for 30-40 users?
-There are 7 shared but network capable printers in my "network". Should I set up a printer
server on this same file server?
-What is the best way to go about setting up a client-server network from a peer-to-peer network?
-Will I need to bring my current Network down or can I just plug the server up and set up each machine one at a time without having any down time?
- 40 users. About 98% are in this office and we have pcs in two stores that currently do not view
our "corporate" network.
I am planning on transforming it from a peer-to-peer to a Client-Server WAN.
Currently I have a router, a firewall, 2 Hubs and 2 Switches. 1 Linux box which serves as our web
and email server. 2 Linux boxes -- one which can only be viewed by the employees in our corporate
office and in the two stores, and a second which is viewed publicly through telnet.
This setup was here before I arrived so I'm not fully sure about all of the details.
Our firewall is being managed by our ISP. I am also told that we have some VPN set up here which
is how the machines from the two stores are able to view that one linux box behind the firewall.
All of our machines in the corporate office have static IPs. That is part of the reason why I
want to go to a client-Server set-up.
I am not a network admin so I know very little about networking. I have some knowledge of trouble
shooting and connectivity. Originally, I had wanted them to have a certified company come in here
and take care of this, but it backfired on me and now it's on my lap.
Here is my question(s):
-What hardware (computers, components...etc), operating systems, software and other peripherals
will I need to do go from peer-to-peer to a client-server.
-I am aware that we'll have to purchase a server and the president wants it to be fully
redundant. What will I need to have on this server to make it be redundant, and what requirements
should the machine meet to be a usable file server for 30-40 users?
-There are 7 shared but network capable printers in my "network". Should I set up a printer
server on this same file server?
-What is the best way to go about setting up a client-server network from a peer-to-peer network?
-Will I need to bring my current Network down or can I just plug the server up and set up each machine one at a time without having any down time?
