New Subnet not handing out IP Addresses

I have created a new subnet (10.168.64.x) on a Netware 6.5 server using DNS/DHCP Admin Tool.
The old subnet (10.168.60.x) is running out of IP addresses but still functioning properly. The new subnet (10.168.64.0) is showing in DNS/DHCP but not handing out addresses.
I have done all of the following-
-Bound an IP address to the Server in the range of the new subnet (10.168.64.1)
-Unloaded and Loaded DHCPSRVR
Still no luck - What are some other steps I can take to get this new Subnet to hand out IP's?
I loaded DHCPSRVR -d2 and got the following message - https://docs.google.com/document/d/1...it?usp=sharing
Any help is appreciated!

If you don't get any replies here, try the DNS/DHCP specialist forum
https://forums.novell.com/novell-pro...dent/dns-dhcp/

Similar Messages

AX does not hand out ip addresses in roaming mode

I am trying to set up roaming network in my house using a Airport Extreme as the main router and a ethernet connected (via Powerline HD) Airport Express on the second floor of my house. I followed the usual instructions to set up the Airport Express to create wireless network in bridge mode. The Express allows clients to connect and accepts the password but does not hand out ip addresses. so the roaming device (an ipad and an Air) end up with self-assigned addresses in the 169.*.*.* range.
How do I correct this?
option click on the Air wifi symbol shows that its corrected to the correct wifi base station
Airport Utility sees both the main Extreme base station and the Express second floor base station, and neither reports any problems.
Thanks.

I am trying to set up roaming network in my house using a Airport Extreme as the main router and a ethernet connected (via Powerline HD) Airport Express on the second floor of my house. I followed the usual instructions to set up the Airport Express to create wireless network in bridge mode. The Express allows clients to connect and accepts the password but does not hand out ip addresses.
Actually, with the AirPort Express in bridge mode, the AirPort Extreme would be the router "handing out" the IP addresses as they would just be "passing through" the Express in this configuration.
Let's double-check your roaming network configuration, just to be sure nothing was missed.
Roaming Network Setup
Ref: See page 42 of the Apple AirPort Networks guide.
Setup the AirPort connected to the Internet to "Share a public IP address." Internet > Internet Connection > Connection Sharing: Share a public IP address
Setup the remaining AirPorts, as bridges. Internet > Internet Connection > Connection Sharing: Off (Bridge Mode) For each AEBSn in the roaming network:
For each base station:
Connect to the same subnet of the Ethernet network.
Provide a unique Base Station Name.
The Network Name (SSID) should be identical.
If using security, use the same security type (WEP, WPA, etc.) and password. Note: It is highly recommended that you use WPA2 Personal for best bandwidth performance.
Make sure that the channel is set at least three channels apart from the next base station to prevent Wi-Fi interference.

New 2008 R2 DHCP server will not hand out IP addresses

We've recently migrated our Domain Controllers to 2008 R2, Virtual Machines. (DC3 & DC4).
DC2 is an older 2003 box, 32 bit, set for retirement. All former roles have been moved to DC3 & DC4, including FMSO roles, and the server (DC2) has been demoted. The only service that remains on DC2 is DHCP.
I've used NETSH to export / import the DHCP info to DC4. All reservations have transferred ( Printers) and the scope shows "active" on DC4 and authorized, and running, but whenever I shut DHCP down on DC2, DC4 doesn't start handing out
IP addresses to clients.
Even after rebooting a client multiple times, running ipconfig /release & /renew, it never finds the new DHCP server, nor does the server show any client information in the address leases. (other than reserves)
We have a Cisco ASDM deployed, but DHCP and DNS are both disabled on this device, so I'm not sure IP Helper would be an issue here.
Since both my new DC's are 2008R2, do I need to elevate active directory up to 2008 function before DHCP will work?

Hi,
Is the issue resolved? As suggested by
Wyatt Miller, you can check if it was caused by IP helper.
In addition, is the new server authorized?
Here is a migration guide for you:
Migration of DHCP Server from Windows Server 2003 to Windows Server 2008
http://blogs.technet.com/b/teamdhcp/archive/2009/02/18/migration-of-dhcp-server-from-windows-server-2003-to-windows-server-2008.aspx
Hope this helps.

Lion Server not handing out DHCP addresses to Snow Leopard client

I have been pulling my hair out over this.
Here is the layout
Lion Server running on the newest Mac Mini and doing mail, DNS, DHCP, Software update and has a valid, not self assigned, certificate
3 clients running Lion Desktop (2 iMACs and a MBP pro (all no more that a year old and all woth the current updates)
1 client running Snow Leopard Desktop (last years 13 inch MBA)
The 3 Lion clients can get dhcp fro mthe Lion server without any issue
The SL client cannot get a DHCP address from the Lion server
A tcpdump shows the DHCP request coming from the MAC address of the SL client but no response from the Lion Server and nothing showing a deny in the logs for the DHCP server or any other system/kernel logs. The Lion clients all show the request and reply for them. All 4 clients currently have a static assignment in DHCP but even if I remove them all and do auto-assign for everything or even each one individually, the SL client will not get an address both on the Wifi and Ethernet (I have the USB ethernet adapter).
I also have an Aiport Extreme and if I use that for the DHCP server then all clients get the addresses. I know the DHCP server in the extreme cannot be shut down but if you give the extreme a static address then assign dhcp on the extreme to only give out one address and that is the same one that is statically assigned then it "thinks" it is out of addresses and no longer tries to assign addresses
At first I thought there was a conflict between the extreme and the Lion server but as I mentioned above, tcpdump clearly shows the requests going right to the Lion server
I'm usually pretty good at this kind of thing but this one has me stumped. I'm thinking bug, anyone else run into this yet?

Ryan jones,
> Having trouble with our dhcp server handing out IP addresses through the
> Wireless Lan Controller.
Has it ever worked? Is the Wireless controller configured to forward DHCP
requests to your DHCP server?
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)
Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

WRE54g not handing out IP address to client systems

This is probably a silly question, but I'll ask it anyways.
We have a Linksys WRT54G ver6 running latest firmware revision 1.02.0 along with a WRE54G ver3 running firmware 3.01.01.
Both devices are configured to use WPA-PSK security, and I have reconfirmed that the key is the same on both devices.
The wireless router is connected to our existing wired network, and so the DHCP functionality of the router is disabled as we want wireless clients to get their IP address from our existing DHCP server on the wired network. This part works fine, wireless systems can connect to the wireless router and they are given an IP address from the range configured on our wired DHCP server.
The range expander has been configured with the same SSID, and security settings as the wireless router. Wireless clients can see the SSID being broadcast by the range expander and they are able to connect to it, but they are not given an IP address.
Is this because the range expander is expecting to receive the IP's from the DHCP server on the wireless router ( which is disabled ) and does not know anything about our existing wired DHCP server?
Thanks.

ok I knew this was going to be something silly.
I tried disabling the wireless security on both devices and this allowed wireless clients to receive an IP address from the Range expander ( verified by the MAC address of the Access point the wireless clients were connected to ).
So I rechecked the security settings again, the key was fine but the issue turned out to be that the wireless router was configured to use WPA2 while the range expander only seems to have support for WPA. Once I enabled WPA on the wireless router, the wireless clients were able to connect and receive their IP address via the Range expander.

DHCP not handing out IP leases to non-domain members

Recently gotten DHCP working, server gives out IP address for domain computers only, non-domain computers do not get a lease and if I manually assign an IP and the device will gain network and internet access. I used the wizard to create the DHCP IP range
but have not done much beyond that. I have setup DHCP servers using Linux, my first go around with Windows. Any further information you may need please let me know.
Thanks.

Alright here we go, took some digging but found the solution for all issues.
netsh int ip reset
netsh winsock reset
Just as further step I restarted DHCP on the server, one more time, then restarted the network interface on my test laptop, I was given an IP address from the server and could browse the network\internet. This morning I checked Address Lease's and now
I see ten address have been leased for RRAS and all devices I have ran the above command on are pulling an address. So the solution to my problem, disable filters for allowed devices in DHCP manager, increase the range or block of IP address to be leased and
finally rebuild\reset winsock and ip stack on domain devices.
Hope this helps someone else in the future.
Cheers!

ACS handing out duplicate addresses

folks
we have an acs server which manages a number of dsl terminations
three of the vpns are having trouble logging on and the when looking at the acs box for the problem vpns it seems to be handing out duplicate IPs and those handed out are only from the higher end of a 24bit mask, i.e. 172.17.10.250 - 254
has anyone seen this before?
thanks to anyone taking the time to reply

Hi,
We must configure the accounting for the users who are fetching IP address from the ACS server, otherwise ACS would never know when that user logged in or logged out and according to that IP address would be freed or assigned to the user.
HTH
Parminder

WRT310N - Wireless not giving out IP addresses - Any hope?

I have a WRT310N. For wired ethernet there is no problem whatsoever but when I try to connect wireless laptops, cameras, etc. I can only do it 2 out of 10 times.
I usually get a limited connectivity error. It seems like the unit isn't giving out IP addresses over wireless. After rebooting and/or resetting it will sometimes work for a bit. There seems to be quite a few posts that are like mine so I don't have a good feeling about there being a solution to this problem.
Is there?
So I can get some work done, this morning I pulled the WRT310N and put the old WRT54G back on because it works great.

Upgrade/reflash the firmware for your router, reset the router and reconfigure. This should solve your problem.

New 5508 not handing our correct IP address Scope to LClients

Just inserted a new 5508 WLC into the network. We current have 3 4404 WLCs, and there was a need to duplicate, as much as possible, the configurations on the 4404s, and the design. The 5508 came online as expected. We moved a few access points over to it. The APs got the correct address range. The clients are expected to get addresses in the same scope range as the APs. However, the clients are receiving addresses in the management IP scope.
I know there are two "not a good way to do it" in here. Why is the management address range in the DHCP scope, and why are the clients using the same scope as the APs. We are going to change that. For now, the AP and client in the same range has been going on since we rolled out wireless in 2006.
The 8 ports on the 5508 are configured for LAG. There is no dedicated port for management. They tell me not to do that on a 5508.
Anyone got any ideas? I am suspecting bridging is the issue. Have no idea where to look or what to do.
Thank you for your feedback....
Sent from Cisco Technical Support iPad App

Do you have DHCP proxy disabled ?
CONTROLLER->ADVANCE->DHCP
If proxy is enabled the wlc will unicast the dhcp request on behalf of your wireless client from the dynamic interface the client is on.
If proxy is diabled, all normal wired side rules apply. A ip helper would be required on the SVI of the subnet the guest are on.
Check that
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

DHCP not handing out addresses

Hi all
I have Windows Server 2008 sp2 roles AD DNS and DHCP.
Several days my server DHCP is "hangs"
a few hours after restart
C:\Windows\system32\svchost.exe -k DHCPServer run on 50 % on procesor and mmc not responding I must before kill proses svchost and start DHCP is
looks good but not response to client PC

Run a free malware scan using the following to make sure there is no infection.
Microsoft's Safety Scanner (gest updated regularly):
http://www.microsoft.com/security/scanner/en-us/default.aspx
MalwareBytes free scanner - update before you run (to use the free version for occasional scans, do not opt to try the free 30 day pro version during installation)
www.malwarebytes.com
Are there any event log errors?
As a test, if you run it without any third party services running, does it do the same thing? To do that, from a Start/Run box, run
msconfig, select Service tab, click on Hide Microsoft Services, then make sure the list left is checked, and disable them, and restart. Run it as a test, and if it doesn't occur, then you know it's third party software doing it.
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Time capsule takes forever to hand out IP address

I have a time capsule and I have an airport express. The time capsule is downstairs and the the airport extreme is upstairs.
I have them both named the same thing. I don't know if that's right.
Here's the setup.
On the main page of the Airport Utility
FROOTY - time capsule Firmware = 7.6.4
Internet page - DHCP and 2 DNS servers listed
Wireless page
mode = create a wireless network
Network name = Frooty
Security = WPA2 Personal
Wireless Options
5ghz network name = FROOTY 5GHz
Radio mode = 802.11a/n - 802.11b/b/n (Automatic)
2.4GHz Channel = automatic
5GHz Channel = automatic
Network = Off (Bridge Mode)
no DHCP Reservations
no Port settings
Enable Access Control = unchecked
FROOTYU - airport express (U = upstairs) Firmware = 7.6.4
Base Station name = FROOTYU
Internet page - DHCP and 2 DNS servers listed
Wireless Options
Network Mode = extend a wireless network
Wireless name = FROOTY
Security = WPA2 Personal
Wireless options = FROOTY 5GHz
Network tab everything greyed out
Enable access control unchecked.
My setup is as follows
The airport express is recently configured, but I think this was happening before I hooked it up upstairs.
I have a Nvidia Shield and the wireless *****. You have to be like 10' from the WIFI device so I put the airport express
upstairs so when I'm up there I don't have issues with the Shield Tablet.
My Modem is a Charter cable modem, downstairs, wireless off. Plugged into a switch. Plugged into the switch as well
is all the CAT5 jacks I'm using around the house. The Airport Express and the Time capsule are both plugged into CAT5 jacks. I don't know if the airport express needs to be plugged into a CAT5 jack as well? That part I don't get.
Anyhow, any new device that is connected to the network, it takes about 1- 1.5 minutes to get an ip address. This is becoming increasingly annoying, to the point where I'm considering getting rid of the apple wifi devices.
Any help is appreciated.

This is what I did, posted below, but devices like my PS3 and my wifes Nook still take forever getting an IP it seems.
Temporarily, move the AirPort Extreme to the same room or general area of the Time Capsule, power it up, and wait a full minute.
Then, hold in the reset button on the back of the AirPort Extreme for 9-10 seconds, then release. Allow a full minute for the AirPort Extreme to restart to a slow, blinking amber light.
Close AirPort Utility if it is open.
Click the fan shaped AirPort icon at the top of your Mac's screen. Wait a few seconds for the listing of New AirPort Base Station to appear.
Click on AirPort Extreme just below that and AirPort Utility will open automatically open and analyze your network settings. In the example above, this is shown as an AirPort Express. In another minute, you will see that it will configure the AirPort Extreme to "Extend" the network.
Enter a device name that you want to use and click Next
Wait another minute for AirPort Utility to configure the AirPort Extreme. When you see the message of Setup Complete, click Done.
Move the AirPort Extreme to a location that is approximtely half the distance from the Time Capsule to the area that needs more wireless coverage and power it up.
You are all set.

DHCP Server not giving out IP Address to APPLE iPhone

Hi, First off, I hope this is the correct forum....
A little background, I have a very nice 16GB 3G iPhone (from Apple of course). It has no problem connecting to my wireless access point (cisco 1240). I have an old windows server that I can turn on as a dhcp server and it gets an address back right away, however my mac server (10.5) will no give it an address and I do not understand why. Here is the log.....
Mar 16 19:06:37 macserver bootpd[37021]: server starting
Mar 16 19:06:37 macserver bootpd[37021]: server name macserver.schmittg.com
Mar 16 19:06:37 macserver bootpd[37021]: interface en0: ip 192.168.1.75 mask 255.255.255.0
Mar 16 19:06:37 macserver bootpd[37021]: interface en2: ip 10.211.55.2 mask 255.255.255.0
Mar 16 19:06:37 macserver bootpd[37021]: interface en3: ip 10.37.129.2 mask 255.255.255.0
Mar 16 19:06:49 macserver bootpd[37021]: DHCP DISCOVER [en0]: 1,0:21:e9:5:d3:de <iPhone-5>
Mar 16 19:06:49 macserver bootpd[37021]: service time 0.008083 seconds
Mar 16 19:08:11 macserver bootpd[37021]: DHCP DISCOVER [en0]: 1,0:21:e9:5:d3:de <iPhone-5>
Mar 16 19:08:11 macserver bootpd[37021]: service time 0.003807 seconds
Mar 16 19:08:12 macserver bootpd[37021]: DHCP DISCOVER [en0]: 1,0:21:e9:5:d3:de <iPhone-5>
Mar 16 19:08:12 macserver bootpd[37021]: service time 0.000683 seconds
Mar 16 19:08:13 macserver bootpd[37021]: DHCP REQUEST [en0]: 1,0:21:e9:5:d3:de <iPhone-5>
Mar 16 19:08:13 macserver bootpd[37021]: service time 0.001844 seconds
Mar 16 19:08:24 macserver bootpd[37021]: DHCP DISCOVER [en0]: 1,0:21:e9:5:d3:de <iPhone-5>
Mar 16 19:08:24 macserver bootpd[37021]: service time 0.000587 seconds
Mar 16 19:08:25 macserver bootpd[37021]: DHCP REQUEST [en0]: 1,0:21:e9:5:d3:de <iPhone-5>
Mar 16 19:08:25 macserver bootpd[37021]: service time 0.000409 seconds
Mar 16 19:08:27 macserver bootpd[37021]: DHCP DECLINE [en0]: 1,0:21:e9:5:d3:de
Mar 16 19:08:27 macserver bootpd[37021]: dhcpd: host 1,0:21:e9:5:d3:de declines IP 192.168.1.227 from server 192.168.1.1
Mar 16 19:08:27 macserver bootpd[37021]: service time 0.001994 seconds
What is wrong?
Thanks!

I am having a similar problem:
---------------- Client Request --------------------
op = BOOTREQUEST
htype = 1
flags = 0
hlen = 6
hops = 0
xid = 20714
secs = 27
ciaddr = 0.0.0.0
yiaddr = 0.0.0.0
siaddr = 0.0.0.0
giaddr = 0.0.0.0
chaddr = 0:4:13:2a:2f:ed
sname =
file =
options:
Options count is 9
dhcpmessagetype (uint8): REQUEST 0x3
maxdhcp_messagesize (uint16): 0x224
requestedipaddress (ip): 192.168.1.66
server_identifier (ip): 192.168.1.200
host_name (string): m3-0004132A2FED
parameterrequestlist (uint8_mult): {0x1, 0x3, 0x6, 0xf, 0x21, 0x42, 0xa0}
vendorclassidentifier (string): snom-m3-SIP/01.25//10-Mar-09 16:36
client_identifier (uint8_mult): {0x1, 0x0, 0x4, 0x13, 0x2a, 0x2f, 0xed}
end (none):
bootpd[3138]: DHCP REQUEST [en1]: 1,0:4:13:2a:2f:ed <m3-0004132A2FED>
SELECT
state=SELECT
Sending: DHCP ACK (size 300)
bootpd[3138]: replying to 192.168.1.66
=================== Server Reply =====================
op = BOOTREPLY
htype = 1
flags = 0
hlen = 6
hops = 0
xid = 20714
secs = 0
ciaddr = 0.0.0.0
yiaddr = 192.168.1.66
siaddr = 192.168.1.200
giaddr = 0.0.0.0
chaddr = 0:4:13:2a:2f:ed
sname = ryan-perrys-computer.local
file =
options:
Options count is 8
dhcpmessagetype (uint8): ACK 0x5
server_identifier (ip): 192.168.1.200
lease_time (uint32): 0xdec
subnet_mask (ip): 255.255.255.0
router (ip_mult): {192.168.1.1}
domainnameserver (ip_mult): {208.67.222.222, 208.67.220.220}
domain_name (string): wha
end (none):
bootpd[3138]: ACK sent <no hostname> 192.168.1.66 pktsize 300
bootpd[3138]: service time 0.001879 seconds
destination address 255.255.255.255
---------------- Client Request --------------------
op = BOOTREQUEST
htype = 1
flags = 0
hlen = 6
hops = 0
xid = 11587
secs = 27
ciaddr = 0.0.0.0
yiaddr = 0.0.0.0
siaddr = 0.0.0.0
giaddr = 0.0.0.0
chaddr = 0:4:13:2a:2f:ed
sname =
file =
options:
Options count is 4
dhcpmessagetype (uint8): DECLINE 0x4
server_identifier (ip): 192.168.1.200
requestedipaddress (ip): 192.168.1.66
end (none):
bootpd[3138]: DHCP DECLINE [en1]: 1,0:4:13:2a:2f:ed
bootpd[3138]: dhcpd: IP 192.168.1.66 declined by 1,0:4:13:2a:2f:ed
marking host 192.168.1.66 as declined
state=<none>
bootpd[3138]: service time 0.001143 seconds
destination address 255.255.255.255

WRT54gr not giving out ip addresses

I have a WRT54GR that seems to stall after running a couple of days. After about 3 - 5 days of running my PC's can see the wireless network, connect to it, but will not be given an IP address. If I reset the WR54gR the PC or laptop get's an IP address just fine. Any thoughts?
It has the latest firmware and YES, I have re-applied the latest firmware to this router.

Hi , try a few changes in the wireless settings.....from a hardwired PC access your router using http://192.168.1.1 "admin" is the password.....slect the wireless section and select channel 11....save settings....then go to the advanced wireless settings and reduce the beacon interval to 50 and reduce the RTS and fragmentation threshold by 40 each..
re-connect to your wireless network and observe.

Will my new MBP have the same IP address if I use Migration Assistant?

In a couple of weeks I'll have my new MacBook Pro-13". I want to transfer all files from my current Intel MacBook via Migration Assistant. I'll have both Macs running 10.6.3 Snow Leopard or latest OS when I do this.
OK but now I still want to use the old MacBook -but won't the IP Address (looks like this: 192.168.0.###) be the same on both Macs after using Migration Assistant? If so, then how do I avoid that? Do I set-up my NEW MacBook Pro first and then use Migration Assistant? Or ???
Thanks for any advise as I will only have a couple of days to set-up my new MBP as I am giving the old MB to my daughter and then she's leaving to fly home! If no volcano of course!
Thanks,
Steve

Hi
+"are you saying that when I first start-up the new MBP my home wired and wireless internet setup will assign an IP number to the MBP that will be different from the existing MB?"+
Yes. Most 'ad-hoc' home networks will have 'something' handing out IP addresses. Typically this will be a Router or possibly Router/Modem combination depending which kind of DSL Service you have. In an environment like this the Router/Gateway will be the DHCP Server. If you're not manually assigning IP address this would be the case. No DHCP Server AFAIK hands out the same IP addresses to two or more separate devices connecting to the same network. If you are manually assigning IP Addresses you still would not do this. Even if you did a warning message would appear telling you the IP address was in use. This is typical of the sort of basic networking most home environments have.
+"Further I should then use Migration Assistant but I should NOT ENABLE the option to transfer network settings?"+
As already mentioned whenever I've tried this they never transfer anyway. In which case don't bother selecting the option. If you're using firewire cables you don't have to have them connected to any network at all.
It's always a good idea to turn on anything new and test it. It's not impossible for there to be a hardware problem. It's rare but it does happen.
HTH?
Tony

CISCO ACS has stopped handing out IPs from IP Pool

I've setup ACS to assign a user an IP address from the IP Pool assigned to the group. Gave the pool a 10.1.16.150 - 10.1.16.250 range. 20 clients worked fine, and now it won't hand out any addresses. I rebooted the ACS and one of the clients that did not get an IP address now gets one, but now others don't.
Any ideas?

All addresses in an IP pool must be on the same Class C network, so the first three octets of the start and end addresses must be the same. For example, if the start address is 192.168.1.1, the end address must be between 192.168.1.2 and 192.168.1.254.
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacs4nt/acs32/user/sad.htm#wp36881

New Subnet not handing out IP Addresses

Similar Messages

Maybe you are looking for