Discussion Locked

Using DHCP

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a DSL router that I recently had setup with a DHCP scope to dynamically assign IPs to my mixed NT and Macintosh network. Previously IPs had been static on our private network. The problem: only two of the 20 macs configured the connection using DHCP correctly. The others pointed to the router as the name server, which has a private network address, instead of pointing to the ISP's name server on the net, although they did correctly get an IP from the scope, the subnet mask is correct, asis the gateway (the router). I tried trashing the TCP/IP pref to no avail. The OS version doesn't seem to make a difference. All the NTs are working correctly.

7 replies

by bcforrest

Is this keeping the Macs from seeing the
internet properly, or is the router
translating the DNS properly? I had a
similar problem with my Mac when I
connected it to a PC using Internet
Connection Sharing. The Mac would hit
the internet,but it would take a few
seconds longer for the DNS to translate
properly. If you are not running OS 9.04,
please do, if possible. Mac OS 8.5-8.6
don't handle DHCP correctly and have
difficulty renewing a DHCP lease. If you
are not running OS 9.x, I suggest you give
the Macs static IPs.

by chum

The TCP/IP configuration software on Mac OS has different "User Modes." It sounds to me like you are in the Basic User Mode. If you set TCP/IP to configure using DHCP server, the name server addr. says "will be supplied by server"

To change this,while you are in the TCP/IP control panel, go to the Edit menu and select User Mode. Click on Advanced, the click OK. Now, you should be able to manually enter the ISP's DNS address into the Name server addr. field.

Try this out before you upgrade all the Mac OS machines.

by tweakyterrase

First and foremost, It doesn't matter where the DNS translation is done. If you are on Qwest network, you are more than able to use AT&T's DNS Boxes. Behind the scenes, you router is every once and a while requesting of other DNS boxes for a routing table update, (this is also done when you submit an address no already stored in your router's table) The important thing is that your computer have internet and office resources avaible to them. Besides static ip's are not all that bad as long as you have a relatively small computer base to connect together.

But if that doesn't help, try these leads:

1. Check and see what the physical limitation of your router's DHCP server table are. For example a Cisco 675 router DSL modem can only handle thirty two computer at any one time.

2. Fore shits and gigles, I would go onto you NT boxes and release the ip address and then request anouther one to make sure the router isn't giving you hard ache.

Wish I could be of more assistance but that is all...

This discussion is closed to new replies.