|
|
|
how to connect router to server
|
Original Message
|
Name: pirx
Date: August 13, 2004 at 13:41:43 Pacific
Subject: how to connect router to serverOS: Windows 2003CPU/Ram: 2 GHz, 1GB |
Comment: Hi! I´m a newbie to networks so please be tolerant with me ;) We have a: - server, with 2 NIC (network cards), running Windows 2003 Server - HW router and ADSL modem - a lot of switches Now I need to connect all of this together so the client machines will be connecting to the Win2k3 Server, which is going to be a DHCP server and proxy server. How to do the physical connecting? Any help is *greatly* apprechiated :) regards, H.
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: Jamie_McCoy
Date: August 13, 2004 at 18:10:40 Pacific
|
Reply: (edit)SERVER >> Router >> PCS all connected via RJ45's, client PS hook up into the routers LAN ports, SERVER hooks into WAN port its quite simple, just pretend your server is the ISP, in which case you would be hooking into WAN to get internet access.. the router will act as your DHCP server Jaymc.co.nr
Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: pirx
Date: August 14, 2004 at 03:00:55 Pacific
|
Reply: (edit)Thanks for replying, Jamie! We have also 2 NIC´s in the server - as I understood, one is for external traffic and one is for internal traffic. External part: NIC1 >> Router >> ADSL modem Internal part: NIC2 >> Switch Is this correct? Luckaly the PC´s are already connected to the switches.
Report Offensive Follow Up For Removal
|
|
Response Number 4
|
Name: Jamie_McCoy
Date: August 14, 2004 at 08:10:44 Pacific
|
Reply: (edit)If it was me, this is what id have, actually this is what i have, lol MODEM (CABLE) >> NIC 1 (SERVER) This will give your server internet access. Install the proxy server on your server and you will have the ability to share this access So, now for the sharing NIC 2 >> ROUTER/SWITCH/HUB >> Client PC's NIC 2 will have a static IP address, with DHCP enabled. All the client PC's will recieve their internet through the server, which is also connected to the ROUTER/SERVER If you need any more help on anything im an email away jamie_mccoy@hotmail.com Jaymc.co.nr
Report Offensive Follow Up For Removal
|
|
Response Number 6
|
Name: pirx
Date: August 14, 2004 at 09:01:56 Pacific
|
Reply: (edit)Many thanks for enlightening me on the subject! :) I will be doing this shortly and I apprechiate your offer. best regards, H.
Report Offensive Follow Up For Removal
|
|
Response Number 8
|
Name: heropsycho
Date: August 14, 2004 at 11:20:26 Pacific
|
Reply: (edit)I'm very confused why you wouldn't put the router/firewall in front of the server for security reasons. If he's using a proxy server such as ISA, then yes, one NIC should be plugged into a switch, where the rest of his clients should be connected. But the other NIC should be connected to the router's LAN ports. Regardless, you don't need a router between the proxy server's LAN interface and the other clients since they're on the same network. In effect, the proxy server is a router in this scenario between the router/switch, and the LAN. You only need to make sure you assign the DHCP server in win2K a network range that is different from what the router/switch is using. Putting the router in front of the proxy server would give firewall protection to the Win2K3 server, which in my mind is VERY important. The Win2K3 server has DHCP services, so it could take care of that, not to mention you'd probably want the Win2K3 box to do DHCP if you want active directory implemented anyway. MCSE, MCSA Messaging, baby!
Report Offensive Follow Up For Removal
|
|
Response Number 9
|
Name: pirx
Date: August 14, 2004 at 12:47:56 Pacific
|
Reply: (edit)Here is what I had in mind: External network: NIC1 -> switch -> HW router -> ADSL modem - here is going to be the proxy server Internal network: NIC2 -> switch -> client computers - this one has the fixed IP (192.168.0.1) and is the DHCP server. Am I confusing anything? :)
Report Offensive Follow Up For Removal
|
|
Response Number 10
|
Name: heropsycho
Date: August 14, 2004 at 13:18:23 Pacific
|
Reply: (edit)Good job! ;-) Just make sure the DHCP server in the router and the service in the Win2K3 server don't assign the same network address numbers. In other words, if that is going to be the IP address of the NIC in the Win2k3 server, make sure the hardware router's DHCP server doesn't use the same network address. Make it do something like 192.168.1.0 network range. MCSE, MCSA Messaging, baby!
Report Offensive Follow Up For Removal
|
|
Response Number 12
|
Name: pirx
Date: August 15, 2004 at 08:37:06 Pacific
|
Reply: (edit)Today I have connected the HW and it works! :) I don´t know if I should open a new thread because I have a question about configuring DHCP. (btw, as mentioned before, I use Win2k3 Server) NIC1 is configured with IP, subnet mask, default gateway and DNS the way I was told to from the ISP. Trouble starts with configuring NIC2. I did it like this: IP: 192.168.0.1 Subnet: 255.255.255.0 Default gateway: ?? (don´t know what to type in here - router IP?) DNS: ?? (can i use the one from ISP? Or should I configure my own DNS server, because I´m going to need one for Active Directory) Then I can start configuring DHCP from Administration tools. How to do it is described here: http://www.windowsnetworking.com/articles_tutorials/DHCP_Server_Windows_2003.html Picture no. 7 from the setup wizard is confusing me. "To configure scope clients to use DNS servers on your network , enter the IP addresses for those servers". Server name: (i type the name of my server here) IP address: which IP should I type in here? And when I Authorise the DHCP server and the settings are correct, then the client PC´s should be getting their IPs from the Win2k3 server, am I right? Oh man, am I troubeling you :))
Report Offensive Follow Up For Removal
|
Use following form to reply to current message:
|
|

|