What happens if you change the name server in your DHCP scope from 184.108.40.206 to one of your internal DNS servers?
same thing it never shows up in ipconfig /all and doesn't allow resolution. I want to say a big thanks so far for all your help.
So, the client isn't getting the DNS settings at all then. What about the default gateway, is the client receiving that from the DHCP server?
yes its getting everything else just not DNS, if I put it on the default VLAN everything is fine, somehow this VLAN is stopping DHCP propgating the DNS information to the clients. I can ping everything even accross subnets, can go to my servers on 172.16 via IP but just DNS isn't playing ball.
What routing information does the DNS server have? route print
Sound like the DNS/DHCP servers don't have a route back to the wireless VLAN all your replies are heading out the default gateway to nowhere?
This would point to a RIP configuration issue.
If you clients on both subnets are getting the correct default gateway (normally your core if that's doing the routing) make sure you have RIP configured correctly on the gateway device.
It should tell the originators which gateway to send the packets back through.
Last edited by m25man; 21st February 2014 at 01:07 PM.
I use a dhcp3 server on Ubuntu for my DHCP (2008r2 AD and DNS though), and don't use the Windows DHCP, so the config a aren't what I'm used to on the DHCP server
ccadit (21st February 2014)
I've tried doing that few time without any success.
All sorted now, a big thanks to FN-GM who pointed me in the direction of removing IP info from edge switch and seawolf for making my think that of trying scope on another DHCP server. All working now and its been an education.
There are currently 1 users browsing this thread. (0 members and 1 guests)