MacNN Forums (http://forums.macnn.com/)
-   Classic Macs and Mac OS (http://forums.macnn.com/classic-macs-and-mac-os/)
-   -   DHCP Wierdness (http://forums.macnn.com/64/classic-macs-and-mac-os/44381/dhcp-wierdness/)

 
cameronc Jun 14, 2000 05:15 PM
DHCP Wierdness
Having a problem with DHCP on a few macs in my office. The Macs in question are running various versions of the Mac OS, including 7.6.1 and 8.x. The DHCP Server is on NT Server 4 (sp5).

I had previously been using static IP addressing for our mixed Mac/PC office, but recently switched to DHCP to simplify my life. Instead, it is making it very complicated. All of the PCs, and most of the newer Macs are handling it just fine, but some of the older Macs have started to give me a problem.

After about two weeks of running smoothly, four of the oldest machines have started to give IP conflict errors. It seems that they are all trying to use the same IP address. This IP, coincidentally, is the lowest available IP address (according to my DHCP server), and is not actually leased by ANY of them.

My working theory is that the Mac gets a lease offer, takes it, and never sends a message back to the DHCP server letting it know that it accepted the lease.

Any ideas on solutions? I have tried wiping out the TCP/IP, Appletalk and, Appleshare prefs, then restarting and resetting everything. Didn't work.

Any other ideas?

Thanks!

-Cameron
 
Torkel Spindler Jun 15, 2000 11:46 AM
Cameron,

Waht version(s) of MacOS and OpenTransport do you have on the faulty machines??

Older versions of OpenTransport (before 2.0) had these problems.

-Torkel Spindler
 
marcus_s Jun 15, 2000 12:11 PM
We have also been experiencing a similar problem. We had a few current Macs (8.5) that were having IP problems on a DHCP, we moved them to static IPs and they were fine. We replaced the DHCP, and now those same Macs are having problems with the static IPs. This really doesn't make any sense. I think we're running the latest OpnTx.
marcus_schoen@at-a-glance.com
 
cameronc Jun 15, 2000 01:33 PM
Quote
Originally posted by Torkel Spindler:
What version(s) of MacOS and OpenTransport do you have on the faulty machines??
Actually, we are running OS 7.6.1 and 8.1 on the offending machines, and it looks like they are running either v.1.2 or 1.3.1 of Open Transport.

I wouldn't mind upgrading them to a higher OS (which I think would solve the problem), but they are really old machines (6116s and 4400s) which are scheduled for retirement in the next few months, and don't have much RAM. I'd prefer not to have to upgrade the memory and OS to solve this problem.

Having said that, I have done a bit of searching around and it seems that Open Transport v.2.0 and higher is built with a newer OS in mind. Is there a way to install a newer version of Open Transport on these older machines without upgrading the OS? If so, I have not found it yet.

Thanks!

-Cameron

[This message has been edited by cameronc (edited 06-15-2000).]
 
Hans M Aus Jun 15, 2000 11:45 PM
There is an informative article in the Apple Tech Info Library:

Open Transport: DHCP Client Behavior
Article ID: 58372
Created: 5/12/99
Modified: 4/20/00

We use Vicomsoft's DHCP 6.6.2 server and had a similar problem with previous versions. A client would complain about a duplicate address which was always the same client's own IP address. The problem seemed to occur whenever the client needed to renew the IP lease but couldn't reach the server within a very short, critical time period; the client lost sync with the server. One cause of the network noise problem turned out to be another client which was connected to the same multiport repeater as the DHCP server. We reduced the problem by connecting the DHCP server directly to its own switch port in the network.

The DHCP 6.6.2 server PINGs the network with a candidate IP address until a free IP is found. The clients haven't complained about a duplicate address problem since we installed version 6.6.2 several months ago. I wish that the server had a log file where I could see how often the PING finds a duplicate IP.

 
Hans M Aus Jun 16, 2000 06:17 AM
PS:

On the Macs that receive the same or wrong IP address, check the AppleTalk control panel. On an older MacOS, AppleTalk automatically switches to the printer port (LocalTalk) when a problem is detected on the network. The fact that several Macs are receiving the wrong address suggests that the client is not communicating with the DHCP server.
 
All times are GMT -4. The time now is 02:55 PM.

Copyright © 2005-2007 MacNN. All rights reserved.
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2016, vBulletin Solutions, Inc.


Content Relevant URLs by vBSEO 3.3.2