Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I have a network with 60 pc's and we use VOIP. The VOIP uses VLAN2. The DHCP server for the computers is on VLAN1. Some of our new dell laptops are pulling an ip address from the phone system instead of the dchp server. It is only happening on newer pc's. Any help would be greatly appreciated. Thanks!

Where do your VoIP sets get their IP's from? DHCP? Static?
If DHCP, do they have their own DHCP server on their VLAN?
A little more information regarding your setup would help.

Thanks for your replay. The VoIP sets get their IP's via DHCP server. A mitel 3300 box. The phones get an ip of 192.168.x.x and the pc's get an ip from a win2000 dhcp server with a 10.128.x.x address. The phones are set to receive their ip on VLAN2. The router is a dell powerconnect 3448P and I beleive the ports are set to show both vlans. Does this help a little.
Thanks a lot!!!

I beleive the ports are set to show both vlans.
That would be the problem then. The DHCP servers have no way to identify which is which (PC vs VoIP set).
We're in the process of deploying VoIP where I work and we have separate switches (Baystack 5520 PoE capable) and VLAN for VoIP. PC's do not get plugged into the VoIP ports (we use different color keystones in the wall jacks to differentiate visually) and VoIP sets do not get plugged into the PC ports. This elimates the issues you're having.
I would program certain ports for the VoIP VLAN only and others for PC and do not mix and match (ie: VoIP set plugged into VoIP only port, PC plugged into PC only port). This will remove the issue you're having.

I see what your saying, but one problem we have is that the pc's plug into the phones and then the phones plug into the wall jacks. Once the pc with the wrong ip address boots up, you can do an IPCONFIG /RELEASE AND /RENEW and then it grabs the correct address. I am still curious why the older pc's don't have this issue. Are the new nics vlan aware? Thanks for the help!

That's an interesting setup and an interesting problem. We use statically assigned IP's for our PC's and DHCP for VoIP where I'm working so there haven't been any similar issues.
Check the settings on the VoIP handsets. I know with ours you can either manually enter the VLAN tag, or let it be automatic. If your VoIP sets are set to automatic that might explain the problem (ie: with improper tag the first DHCP to "hear" the request answers regardless of what device is requesting). Once manually set to the proper VLAN for your VoIP, the confusion should end.

Entirely possible the older PCs have fixed IP addresses or their MACs are registered. It's not the age, it's how they were configured. Once you discover the difference in setups between the old ones and the new, you'll know.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |