vaworx
asked on
Windows 2003, 2 x DHCP, VoIP, 2 x Subnets, 2 x Routers, Proper Planning!
Hello,
I'm new to VoIP and Windows 2003 but i do wanted to give the following setup a shot so i've planned it appropriately however i have a few questions which i'm not sure about and was hoping that someone could help out, so here is the deal:
10.0.0.1/20 192.168.1.1
255.255.0.0 255.255.0.0
Internet-----DSL/Router---
| | (1 x NIC, 192.168.0.32, 255.255.0.0, gw 192.168.1.1)
| | (DNS 192.168.0.32, FW to my ISPs DNS server IPs)
Windows XP SP2(4 x PCs)---| | (DHCP Range 192.168.0.100/175)
| |-----------3COM NBX100 VoIP Base System
XEROX Copier----------------| |
| 10mbps Switch-----------VoIP Phones (4 x phones)
Canon Copier-----------------|
|
10/100mbps Switch------------------Vo
|
10/100/1000Gbps Switch-------------Windows
My Questions are:
1. Can i Have 2 x DHCP running, one is a NETGEAR Router (192.168.1.1/100,255.255.0
2. Can i Authorize the Windows 2003 to be the default DHCP for the Windows XP machines and have the NETGEAR lease IPs for the VoIP phones?
3. What would the routing table look like on the Windows 2003 machine or how should i set it up. Do i use the Remote access and routing Tools?
4. Is there anything in the setup listed above looking wrong or could be improved.
5. Regarding the two printers i was thinking to set reserved addresses in the DHCP Scope in Windows 2003 say 192.168.0.100 and 192.168.0.101.
6. Reading through other posts i saw that there are some internet connectivity issues when i don't have the gateway on the say segment as well as no ping, isn't that a routing table issue?
7. The reason why i've planned it this way is because of DHCP failover - if the Windows machine goes down then the phones will be still functional running of the NETGEAR router on a separate IP range.
Please let me know when you get a chance. Thanks.
I'm new to VoIP and Windows 2003 but i do wanted to give the following setup a shot so i've planned it appropriately however i have a few questions which i'm not sure about and was hoping that someone could help out, so here is the deal:
10.0.0.1/20 192.168.1.1
255.255.0.0 255.255.0.0
Internet-----DSL/Router---
| | (1 x NIC, 192.168.0.32, 255.255.0.0, gw 192.168.1.1)
| | (DNS 192.168.0.32, FW to my ISPs DNS server IPs)
Windows XP SP2(4 x PCs)---| | (DHCP Range 192.168.0.100/175)
| |-----------3COM NBX100 VoIP Base System
XEROX Copier----------------| |
| 10mbps Switch-----------VoIP Phones (4 x phones)
Canon Copier-----------------|
|
10/100mbps Switch------------------Vo
|
10/100/1000Gbps Switch-------------Windows
My Questions are:
1. Can i Have 2 x DHCP running, one is a NETGEAR Router (192.168.1.1/100,255.255.0
2. Can i Authorize the Windows 2003 to be the default DHCP for the Windows XP machines and have the NETGEAR lease IPs for the VoIP phones?
3. What would the routing table look like on the Windows 2003 machine or how should i set it up. Do i use the Remote access and routing Tools?
4. Is there anything in the setup listed above looking wrong or could be improved.
5. Regarding the two printers i was thinking to set reserved addresses in the DHCP Scope in Windows 2003 say 192.168.0.100 and 192.168.0.101.
6. Reading through other posts i saw that there are some internet connectivity issues when i don't have the gateway on the say segment as well as no ping, isn't that a routing table issue?
7. The reason why i've planned it this way is because of DHCP failover - if the Windows machine goes down then the phones will be still functional running of the NETGEAR router on a separate IP range.
Please let me know when you get a chance. Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
please advise
ASKER
1. How would the two subents see each other since the Windows 2003 Server is connected to the network using only 1 NIC with a static ip on it 192.168.0.32
2. How would it see the Gateway which is on a separate subnet range 192.168.1.1
3. I want to install an application that comes with the 3COM NBX100 on the Windows XP machines that emulates phones as well as the control panel for the Base Station has to be accessible from the XP machines so that the users can add new employee extensions and manipulate it online which would look like so:
PC------------------IE http:\\192.168.1.150 (the NBX100 address)
192.168.0.102
4. How would these networks talk to each other, Do i have to set routing on the NETGEAR Router somehow or that would be a servie running on the Windows 2003 Server. I already tested the above mentioned situation in my place with a linksys router 192.168.1.1 and the server but the networks don't talk to each other. Not only that but the Server does not even connect to the internet.
I assume there is something wrong with the routing but i'm not sure where and how to set it up. Please advise....
2. How would it see the Gateway which is on a separate subnet range 192.168.1.1
3. I want to install an application that comes with the 3COM NBX100 on the Windows XP machines that emulates phones as well as the control panel for the Base Station has to be accessible from the XP machines so that the users can add new employee extensions and manipulate it online which would look like so:
PC------------------IE http:\\192.168.1.150 (the NBX100 address)
192.168.0.102
4. How would these networks talk to each other, Do i have to set routing on the NETGEAR Router somehow or that would be a servie running on the Windows 2003 Server. I already tested the above mentioned situation in my place with a linksys router 192.168.1.1 and the server but the networks don't talk to each other. Not only that but the Server does not even connect to the internet.
I assume there is something wrong with the routing but i'm not sure where and how to set it up. Please advise....
I haven't forgotten you.
I'm trying to make sense of your last picture.
I think you're confusing things by using routers for each building - that unnecessary.
Place a switch at each location and you can join them using a crossover cable. Since the last switch will share 1 port connection, then if you can afford it you should use GB switches - this will mean the last building will share a duplexed GB pipe (good).
If you run past 300ft, then copper isn't going to be reliable. You may need to use a tranceiver on each end and fiber in the middle. Alternatively, you can use 2 fiber ready switches and Gbics to daisy-chain them to the main office.
By keeping each building on the same LAN segment, you save a bit of work in subnetting and working out the bugs because of it.
I'm trying to make sense of your last picture.
I think you're confusing things by using routers for each building - that unnecessary.
Place a switch at each location and you can join them using a crossover cable. Since the last switch will share 1 port connection, then if you can afford it you should use GB switches - this will mean the last building will share a duplexed GB pipe (good).
If you run past 300ft, then copper isn't going to be reliable. You may need to use a tranceiver on each end and fiber in the middle. Alternatively, you can use 2 fiber ready switches and Gbics to daisy-chain them to the main office.
By keeping each building on the same LAN segment, you save a bit of work in subnetting and working out the bugs because of it.
ASKER
Thank you for the reply again,
That would be the easiest thing to do but as i've mentioned in the previous post the main reason why i want to have 2 X DHCP on the same network is because of DHCP failover which is more of a - if the Windows 2003 box goes down that's OK, because the NETGEAR would still lease addresses to the VoIP phones and that would be less down time for the business in general. I am not using 2 x NIC on the server because if it goes down there will be no connection for the Windows XP machines wheras in this case when there is only one NIC only the domain portion won't work other than that the machines will still lease an ip from the NETGEAR DHCP. The things that i'm not quite sure about is if the Windows 2003 box will in fact do proper routing with one NIC so that the 2 x Subnets will in fact talk to each other. I'm not good at explaining stuff but the idea is there. As we say here it all comes down to CAN or NO CAN do that kine of setup :D. If not, what would your recommendation be given the fact that having the phones working at all times is crucial to that company.
Thanks again for all your help.
That would be the easiest thing to do but as i've mentioned in the previous post the main reason why i want to have 2 X DHCP on the same network is because of DHCP failover which is more of a - if the Windows 2003 box goes down that's OK, because the NETGEAR would still lease addresses to the VoIP phones and that would be less down time for the business in general. I am not using 2 x NIC on the server because if it goes down there will be no connection for the Windows XP machines wheras in this case when there is only one NIC only the domain portion won't work other than that the machines will still lease an ip from the NETGEAR DHCP. The things that i'm not quite sure about is if the Windows 2003 box will in fact do proper routing with one NIC so that the 2 x Subnets will in fact talk to each other. I'm not good at explaining stuff but the idea is there. As we say here it all comes down to CAN or NO CAN do that kine of setup :D. If not, what would your recommendation be given the fact that having the phones working at all times is crucial to that company.
Thanks again for all your help.
I think you'll find the phones will continue to work since they have a lease on their IP addresses (by default 8 days) so it would be a very slim chance that the server would go offline around the time they require a refreshed IP.
All you would have to do at that point would be turn on DHCP on the router and you're good to go. Not a long process at all.
With respect to routing, by subnetting things you actually make things a bit more difficult since broadcasts do not pass the routers so DHCP would then have to come from a local source - which also means the clients probably won't register in DNS also. NetBIOS traffic will also be affected - which means that browsing for a resource across the router won't yield any results and the Master browser (the server) would not know anything about machines outside it's own router.
I would try to keep it all on one network - you'll make your life a lot easier.
All you would have to do at that point would be turn on DHCP on the router and you're good to go. Not a long process at all.
With respect to routing, by subnetting things you actually make things a bit more difficult since broadcasts do not pass the routers so DHCP would then have to come from a local source - which also means the clients probably won't register in DNS also. NetBIOS traffic will also be affected - which means that browsing for a resource across the router won't yield any results and the Master browser (the server) would not know anything about machines outside it's own router.
I would try to keep it all on one network - you'll make your life a lot easier.
ASKER
I think i finally found the answer to my question. It looks like i need to setup what is called a one-armed router in order to manipulate the setup that i wanted at the first place:
http://en.wikipedia.org/wiki/One-armed_router
I'm still reading on it so i'm gonna come back and probably post a manual if i have succeeded in my setup. If you have any comments on that feel free to post here at any time. I'm going to have to perform the setup tomorrow so i hope it works as planned. It will be another sleepless night until i figure this one out...
http://en.wikipedia.org/wiki/One-armed_router
I'm still reading on it so i'm gonna come back and probably post a manual if i have succeeded in my setup. If you have any comments on that feel free to post here at any time. I'm going to have to perform the setup tomorrow so i hope it works as planned. It will be another sleepless night until i figure this one out...
ASKER
Here is some more info, i guess 2 X DHCP was misleading in fact looking at all the NFO it all comes down to setting up DHCP on the Windows 2003 only and having the NETGEAR Router setup as gateway with DHCP disabled then create two separate scopes for 192.168.0.100/175 and 192.168.1.1/24 on the Win2k3.
http://technet2.microsoft.com/WindowsServer/en/library/3967ddab-0b28-4959-8b4d-3052c178731b1033.mspx?mfr=true
Does that sound about right so far?....
http://technet2.microsoft.com/WindowsServer/en/library/3967ddab-0b28-4959-8b4d-3052c178731b1033.mspx?mfr=true
Does that sound about right so far?....
If you're still thinking the remote offices will connect via router then that trick won't work. Besides, I don't think these consumer routers allow more than one IP on an interface - and even if it did, it wouldn't do what you are looking to do.
If you're simply looking to separate the phone and date traffic then each switch in your solution should be capable of VLANs. Set it up the way I mentioned above where the switches connect each office, then VLAN off the number of phone ports you need plus a few extra in case you need them later.
DHCP can then be setup to handle both subnets.
If you're simply looking to separate the phone and date traffic then each switch in your solution should be capable of VLANs. Set it up the way I mentioned above where the switches connect each office, then VLAN off the number of phone ports you need plus a few extra in case you need them later.
DHCP can then be setup to handle both subnets.
ASKER
It actually turned out to be working a OK:
In my NETGEAR router i've added the Win2k3 Server as static router, on the Win2k3 machine i've installed Routing and Remote Access(which actually comes by default all you have to do is configure it), both my switches are VLAN enabled so that wasn't a problem and now both machines ping each other and can logon to the domain. I'm still testing to make sure how is everything working but i guess as far as DHCP lease goes i'll know for sure after 8 days. Of course the Win2k3 messed up the DHCP domain and added mshome.net as default DNS suffix so i'm still working on that. From what i've read so far i have to remove the service and install it again to make sure that it will be working a OK. I'll keep everyone posted on that.
In my NETGEAR router i've added the Win2k3 Server as static router, on the Win2k3 machine i've installed Routing and Remote Access(which actually comes by default all you have to do is configure it), both my switches are VLAN enabled so that wasn't a problem and now both machines ping each other and can logon to the domain. I'm still testing to make sure how is everything working but i guess as far as DHCP lease goes i'll know for sure after 8 days. Of course the Win2k3 messed up the DHCP domain and added mshome.net as default DNS suffix so i'm still working on that. From what i've read so far i have to remove the service and install it again to make sure that it will be working a OK. I'll keep everyone posted on that.
ASKER
Main office:
PC PC PC PC PC PC PC Server
|__|__|__|__|__|__|___|___
|
Ph Ph Ph Ph Ph Ph Ph Copier0 | Second Office: WAN Port
|__|__|__|__|__|__|____|__
| | | | | | |
PC PC PC PC Copier1 | Internet
|
3COM NBX100------10MBps Switch-----------|
| | | |
Ph Ph Ph Ph