Troubleshooting Q&A - September 29, 2005
To Static From Dynamic IP Addresses and Back
No need to stress. You can use both static and dynamic IP address on the same network. We provide a couple of options. Plus, what to do when two PCs on a LAN share the same name.
By Ron Pacchiano
Q. I serve as a one-man IT department for family business and I don't have the time to learn (much less understand) all of the intricacies of networking. In spite of this deficiency, though, I've managed to keep everyone connected, working and secured for about ten years now. Our little five-person office network uses a cable broadband connection for our Internet communication. We use both wired and wireless PCs around the office and have DHC- enabled on the router to handle IP address assignments.
I've just purchased a networked BizHub and the installation techs say it will require a static IP address. Since we currently use DHCP for our IP address assignments, I was wondering if it's even possible to use both dynamic and static addresses at the same time. If not, will we need to switch everyone over to a static IP? Lastly, how does one determine the appropriate static IP(s) to use in these cases?
A. No need to stress over this. Yes, you can use both static and dynamic IP address on the same network. The reason the BizHub requires a static IP address is because, unlike your client PCs, the BizHub will need to be accessed by everyone. With a static IP address, the unit can always be located. On the other hand, if you had configured it to use a dynamic IP address, then the address would change from time-to-time, causing the client PCs to occasionally lose communication with it. To correct that situation, the driver would need to be updated with the BizHubs new IP address every time it changed. Depending on the number of users you have and the frequency of the IP changes, this could be more than a little problematic.
The only thing you need to do on the client side of a system or device that needs a static IP address is to modify its TCP/IP configuration with the proper gateway, subnet mask and DNS addresses. Once the configuration has been saved, the device should be online.
Determining how to select the IP address is pretty simple. Essentially, all you would need to do is give it any address outside of your DHCP scope. For example, let say your DHCP scope was 192.168.0.50 - 192.168.0.100. This means that you have 50 IP address available to use with DHCP. So any address that falls between these two numbers (e.g., 192.168.0.72 or 192.168.0.90) will automatically be assigned to any client with DHCP enabled. Any of the IP addresses outside of this range can then be used as a static IP address.
Usually, I find it helpful to divide IP addresses into sections for easier manageability. For example, I would reserve 192.168.0.1 - 192.168.0.30 for use with network routers and servers. Then I would use the address range 192.168.0.31 - 192.168.0.49 for network peripherals such as your BizHub, scanners, copiers, printers. Finally, you can use the remaining addresses (in this case 192.168.0.50-192.168.0.100) for your DHCP scope. In this way you always know what IP addresses are available for use.
Another method is to use DHCP to assign the BizHub an IP address, but you can configure the DHCP scope to always give the BizHub the same IP address based on its MAC address. This ensures that the BizHub will always be assigned the same dynamic address, giving you all the benefits of a static address, without you having make any changes to your DHCP scope.
The nice thing about this is that you won't need to configure any of the TCP/IP settings manually. Most DHCP servers will support this feature and your routers documentation should be able to walk you through the setup.
Either method will work for you though, so choose whichever one is more comfortable for you.
Q. I have a Dell laptop computer running Windows XP and it's equipped with a Linksys wireless network adapter that I use to connect to our school's domain. When I attempt to log on to the school's network, I receive an error message that says "duplicate name exists on the network." I then clear the error and continue logging on. Once connected, I can browse the Internet. However, when I go to My Network places, I can drill down to the domain name, but cannot see any of the other computers on the network. Going under the assumption that this is a duplicate name on the network, I attempted to change the name of the computer, but was told I didn't have the rights to do this. I have checked the TPC/IP configurations of some of the other Dell computers in our lab and they appear to be similar. Do you have any suggestions about how I should go about resolving this? Any ideas would be appreciated. Thanks!
A. When you have a duplicate name on the network, the system will prevent you from gaining access to the domain, thus preventing you from browsing Network Neighborhood. So I think you were definitely on the right track when you tried changing the computer name. This was a common error I used to come across when rolling out new systems, particularly those that were setup using a Ghost image. Considering that you didn't have the rights to change the computer when you were logged in with your account, I'm wondering if this is a school laptop that was recently imaged. If that's the case, you'll need to get the school's IT department to assist in correcting this problem.
In any case, the way to get around this is simple. You need to log onto your laptop using the local network administrator's account. Once logged in, change the name of the computer. Once you reboot the syste,m you should be able to gain access to the domain. If not, you might need to login locally again and remove the laptop from the domain by making it a member of a workgroup. At this point it will prompt you to restart the system. Once restarted, log in locally again and rejoin the domain. You're going to need access to an account that has rights to join the school domain. If that's not you, as I suspect, then you'll need to coordinate your efforts with the schools IT department. Once that's been accomplished, restart your system. You should now be able to logon with your regular network account. I hope this helps!
Use our feedback form to submit your questions on home or SOHO networking issues. Please be as specific as possible. We cannot guarantee to answer every question we get, but we’ll consider them all.
|Home | Networking | Backgrounders | Internet Sharing | Security | HowTo | Troubleshooting | Reviews | News | About | Jobs | Tools | Forums|