Question

Locked

DHCP won't work with new scope

By hillsteven ·
I've just about run out of available IP addresses in my current IP address pool (192.168.12.0), so I need to add a scope to my DHCP server. (Windows 2003 Standard Ed.)

So far, I've added the second scope (192.168.14.0), created a superscope with both scopes as members, and added the new scope to my router/firewall (Juniper Netscreen 5GT).

I can now set a pc with a static ip address in the new scope and it will work appropriately.
IP: 192.168.14.45
Subnet: 255.255.255.0
Gateway: 192.168.12.1
DNS1: 192.168.12.200
DNS2: 192.168.12.201

that being said, it would APPEAR that the new scope at least functions on the same thread as the rest of the network....

i then set a reservation for my "test" pc (my laptop) in my new scope so that it would force the DHCP server to assign an ip address in the new scope.

this is where i have issues: the laptop sits in "Acquiring address" status indefinitely.

anyone have any ideas??

This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

allow all

by livingathome In reply to DHCP won't work with new ...

I think this may have something to do with the firewall. I am not sure if you are blocking any traffic between the subnets but if you are that couuld be a source of problems. I know i had some issues with the same thing and it turned out to be an ACL.

Collapse -

Edited by moderator

Edited

Message was edited by: beth.blakely@...

Back to Networks Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums