- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsI am having a problem with a network I've set up. The network consists of a domain controller running Server 2003 with DNS and DHCP enabled, a wireless router, an ADSL router and a handful of client PC's wirelessly connected through the wireless router. The domain controller and ADSL router are cabled to the wireless router. DHCP is disabled on the wireless router, but enabled on the ADSL router. The network uses a basic 192.168.0.0 IP address range, with the domain controller and wireless router having static addresses. The ADSL router has a different subnet and a static IP address of 192.168.1.254.
My problem is that firstly, the ADSL router is a shared router residing in a comms room of which I have absolutely no control. I cannot disable the DHCP running on it. Secondly, despite the ADSL router being the default gateway, and being listed in the DC's forward lookup zone, the client PCs are not receiving an Internet connection. However, the DC is, so I know it's working.
I suspected that this was possibly due to the DHCP clashing so I disabled it on the DC and set up all the clients manually with a static IP address and pointing them to the ADSL router. This works ok and gets them an Internet connection, but this slow unless I manually assign them the ISP DNS IP address too. However, it is not ideal because if, say, a laptop was required to be wirelessly connected to the network, it would pick up a DHCP address from the ADSL router and get Internet connection no problem, but it would not be visible to the regular network.
I'm I right in thinking that this can be solved by changing the network's IP address range so that it is in the 192.168.1.0 range? I've been trying to sort it all day and now my brain is frazzled, so any suggestions appreciated, thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: nomorefuzzylogicPosted on 2006-09-27 at 14:38:16ID: 17614414
For your PC's to be able to see the ADSL router they must have addresses on the same network - 192.168.1.0 - unless your PC's are on a different network with a router between your network and the ADSL router network.
You should only have 1 x DHCP server allocating the IP addresses on a network - it is unlikely that having multiple DHCP servers will actually cause anything more than delays in the allocation of addresses though.
I guess that the ADSL router will set itself to be the default gateway when allocating the addresses.
From your description I assume that you have your own network of PC's over which you have 'departmental' control and the ADSL router is 'owned' by a central group. In practice I would have expected the central group to have installed a router between their network through which 'departmental' groups would connect - this would protect the integrity of the central groups network which you could otherwise disrupt - especially by setting IP addresses manually when you are not sure of their DHCP policy. If they do have a router between them and you then you will need to have your own DHCP server and a different IP network with all your machines presumably using the router as the default gateway for paths to the outside world.
Whilst you don't have access to the ADSL router I suggest that the administrator of the comms room already has procedures defined for the connection of other networks - a coffee break with him would sound to be the ideal next step.