[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 340
  • Last Modified:

Multihomed Server 2003 to access device on different LAN subnet

Happy New Year to Everyone...

My LAN is configured on 192.168.20.x
DC: 192.168.20.2
Gateway: 192.168.20.1

Phone system was just installed with 192.168.43.x (as a DHCP server for IP phones).
I need the phone system to be on the LAN so that I can access it from the WAN side as well as management on the LAN side.

With the phone system connected to the LAN, it takes over DHCP from the DC....workstations get addresses on the 192.168.43 subnet.

Is it possible to configure a 2nd NIC my server to account for this dilema?

Thanks


0
OnsiteSupport
Asked:
OnsiteSupport
  • 6
  • 4
  • 2
  • +1
1 Solution
 
magicdlfCommented:
Just change your subnet mask to 255.255.0.0 and see if this will solve your problem.
If not, let us know how the phone is plug into your network.
0
 
amichaellCommented:
You can also VLAN your phone network, which will segregate traffic and the DHCP responses.
0
 
OnsiteSupportAuthor Commented:
phone system is plugged into unmanaged switch (currently).  What if it plugged into the 2nd Server 2003 NIC?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
magicdlfCommented:
You can do that. Just plug and get an IP from the DHCP should be working. Remember NOT to setup the default gateway on your 2nd NIC. It'd better if you configure an IPTable on your win2003 system. Good luck!
0
 
ChiefITCommented:
recommended practice for an IP phone based system is to set it up on VLANS, as amichael suggested. Then, to configure QoS on the switches. Otherwise, you will experience problems with your IP phones.

Once on its own VLAN, you will have to configure DHCP relay to the second VLAN. DHCP broadcasts will stop at the L3 switch that is used to route IP traffic from one VLAN to the other. A recommended practice there is to create a superscope and DHCP relay for your IP phones to have their own IP subnet.

Multihoming your DC is troublesome at best. I can't tell you how many people I had to help overcome a multihomed DC problems. adding a second active nic messes up netbios translation, DNS, DHCP, and internet access. All broadcast data will be confused as to what network it is suppose to spit out to and DNS doesn't know what IP to use. These communications problems cause problems throughout the domain.  I seriously don't recommend it.

Taking into consideration the time it takes to fix and administer these problems, your best bet is to go to managed switches, impliment VLANS, create a QoS plan for your IP phones and DHCP relay for providing an IP.
0
 
OnsiteSupportAuthor Commented:
Chief, I appreciate the comments. But that is not what I need.

I just need my LAN on the 20 subnet to talk to my device thatis configured on the 43 subnet.

Thx
0
 
OnsiteSupportAuthor Commented:
I need it so my vendor to reach the device remotely so they can reconfig it totthe correct ip settings.
0
 
ChiefITCommented:
Is this only for DHCP services, to provide your IP phones with an IP?
0
 
OnsiteSupportAuthor Commented:
Its an avaya IPoffice system that with a port to my LAN that allows mgmt as well as email notifica(ion for voicemails.

Otherwise, it doesn't comm with "IP phones"...they have their own Comm over a separate network.
0
 
ChiefITCommented:
This might be a wee bit difficult with a managed switch unless you configure your router to route to that other subnet.

So, SMTP is one protocol, for email notifications.

What type of connection do  you use to interface the avaya console?
HTTP, telnet/VTY ???

Will your DC, provide time synchronization to the IP phones?

I am trying to build a list of session layer or application layer protocols needed to communicate with this IP phone console.
0
 
OnsiteSupportAuthor Commented:
A bit over my head.  I can get you in touch with someone if you like.  


Just a NIC on the IP office module.
0
 
ChiefITCommented:
Well, let me break it down in a little bit easier terms.

In order to communicate between two different subnets, you  will need to route between them.

If they want to set in their office and configure the IP phone or if a contractor wants to configure this phone from a remote location, it has to be routed traffic.

Can your server do this: (I think so, but that is a wee bit above my head)

I think you can add a fixed route on the server, (or an alternative IP address on your server's  nic card).

If you add an alternative IP address, the route will automatically exist. BUT, what will that do to domain services? (I don't know)

I am thinking, I don't want to gamble with your system. A test environment is needed.

Try taking a NON-important client machine and creating an alternative IP address for the .43 subnet. I have used alternative IP addresses for web page servers before, but they were always on the same subnet.
0
 
OnsiteSupportAuthor Commented:
Problem solved...phone vendor came on site and did what they were supposed to do originally! LOL

I'm giving you the points anyway..thanks for your assistance!
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 6
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now