I want to block DHCP Server

Hi i want to block on an ap where wlan clients are connected, dhcp server from the clients. bc the clients are getting the ip from my dhcp server. but when he also starts an dhcp server i ahve two server in my wlan. so i want to block dhcp ports on my ap.
i have tried it:
i made an port filter: port 67 and 68 (bootp server and client) then i places the filter on RADIO recive site. but then the client doenst get an ip. so i tried it only with port 67 or 68 it also doesnt work.
hope anybody can help me with this issue.
regards Bernhard

DHCP client requests are sent from DHCP client (68) to server's DHCP server port (67). Server replies using port 67 to client's port 68. All above are UDP obviously. So to block rogue DHCP servers put an input ACL 'deny any eq 68 any' to AP radio interface and this should work. Also remember that DHCP client for initial message exchanges uses 0.0.0.0 as src IP and 255.255.255.255 as dest IP so do not replace 'any' with your IP subnets. Hope this helps.

Similar Messages

How to Configure Compact 7 as DHCP Server

HI All,
I have a Windows Embedded Compact 7 headless device.
I want o run DHCP Server on this device to connect 10 clients to it over wired Ethernet.
Later I need to communicate with all 10 clients periodically by using ip allocated by DHCP server.
The DHCP clients we need to use will have only Dynamic IP configuration, no provision to set static IP.
So we need to make WEC7 device as DHCP Server.
Is it really possible to use WEC7 device as DHCP server?
If Yes, how can I Configure WEC7 as DHCP server?
If No, Please suggest any other alternatives to assign IP's to clients and start communicating with clients.
Thanks in advance.
rakesh

Hi All,
DHCP Allocator is working fine on WEC7.
I am able to see the connected DHCP clients information in Registry under ConnectionSharing/Addresses.
But for my application development I don't want to read the registry all the time to get updates of connected clients.
Are there any other options (API) available to read connected clients info (IP, MAC, Client Name etc).
And if i can register to some services for client connection status change notifications would be better.
Do you suggest any appropriate ways?
Thanks in Advance.
rakesh

I want to disable the DHCP server on HH3 and use l...

Hi, i live in a flat with 5 other people so i have my HH3 connected to a linksys wrt5gl so that i can use the QoS capbilities of the linksys (tomato firmware). The linksys router can also limit bandwidth per ip address IF its also the DHCP server. When i disable the DHCP on the HH3 and enable it on the linksys the internet no longer works on any of the PC's, but if i have the DHCP on the hh3 i cannot limit bandwidth per ip on the linksys.
In the flat before this i managed to set this up fine (wasnt with the HH3- some other router) just need some advice on how to disable DHCP on the HH3 and enable it on the linksys wrt5gl whilst still being able to connect to the net.
Here is how its set up atm:
Phone line>>>HH3 (assighns IP through DHCP)>>>Linksys (data goes through QoS)>>>PC's/laptops/consoles in flat
Here is how i want it set up:
Phone line>>>HH3 (Acts as a modem)>>>Linksys (assighns IP through DHCP to allow bandwidth limiting /data goes through QoS)>>>PC's/laptops/consoles in flat
thanks in advance, sorry if this is hard to understand- im not so good at putting the problem into words
Solved!
Go to Solution.

Hi,
Don't know to be honest......but as an idea....you will have to disable DHCP server on the hub, apply a static ip to the Linksys, 192.168.1.100. You'll then need to set up DHCP on the Linksys....start ip 192.168.1.64 end 192.168.1.253, you'll need to add a subnet 255.255.255.0, then the gateway.....192.168.1.254 that's the ip address of the HH and that could be the real problem as normally the default gateway for DHCP on routers is the routers ip address.
So the chandes of it working are slim.....however you dont have to use your HH on your BT broadband you can use another make/model.
One option to use with that router is a Draytek 120 ADSL modem, which does PPOA to PPOE.

Want stream Netflix to blueray via Airport Express wifi. The blueray finds my wifi but the wireless connection failed - said, Ensure DHCP server is enabled on router and restart router. Don't think I have DHCP server. Suggestions anyone?

Want to stream Netflix to blueray player via my existing Airport Express wifi. The player finds my wifi but the wireless connection fails - says, " Ensure DHCP server is enabled on router and restart router." I don't think I have a DHCP server. Suggestions anyone?

I can't speak specifically regarding LG, but the Whole Home feature on Direct TV (record a movie on one DVR and watch it on another TV in another location) just won't work with wireless, and I have a strong fast connection at 300 Mbps. Ethernet works perfectly.
Few audio/video products will accept "n" wireless at 5 GHz. I suspect that your LG accepts a 2.4 GHz signal, which would top out at 130 Mpbs.
If you are trying to stream High Definition video, especially at 1080P, my opinion would be that it is unlikely that you will be able to do so reliably using wireless.
Perhaps another user who has figured out how to do this will post with some input.

OS X server, DHCP Server and random blocked IPs

Hello !
I use a Mac Mini as a DHCP server for my wireless network. It is connected to internet through a wired modem and gives an IP (through Airport) to the computers that ask for it.
Everything works quite fine... Unless, sometimes, clients obtain an adress but cannot browse the web nor connect to local network. The ip is just "blocked".
If i try to use it on an other computer (manually), it just doens't work.
So, I must change the ip, by changing the DHCP Name of the computer (otherwise, the server always give the same adress), to fix the problem.
What is strange, is that a few time after, the incriminated ip works new ! Until it is down again...
My bootpd config file is the fallowing;
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>NetBoot</key>
<dict/>
<key>Subnets</key>
<array>
<dict>
<key>allocate</key>
<true/>
<key>dhcpdomainname</key>
<string>antoine.maille.priv</string>
<key>dhcpdomain_nameserver</key>
<array>
<string>81.253.149.1</string>
<string>80.10.246.3</string>
<string>10.0.0.1</string>
</array>
<key>dhcpldapurl</key>
<array>
<string>ldaps://Mac Mini/</string>
</array>
<key>dhcp_router</key>
<string>10.0.0.1</string>
<key>lease_max</key>
<integer>604800</integer>
<key>leasetimesecs</key>
<string>86400</string>
<key>name</key>
<string>DHCP WiFi</string>
<key>net_address</key>
<string>10.0.0.0</string>
<key>net_mask</key>
<string>255.255.255.0</string>
<key>net_range</key>
<array>
<string>10.0.0.10</string>
<string>10.0.0.100</string>
</array>
<key>selectedportname</key>
<string>en1</string>
<key>uuid</key>
<string>FEB30FD5-3749-480E-9FEB-BD2C20206431</string>
</dict>
</array>
<key>allow</key>
<array/>
<key>bootp_enabled</key>
<true/>
<key>deny</key>
<array/>
<key>detectother_dhcpserver</key>
<true/>
<key>dhcp_enabled</key>
<true/>
<key>oldnetbootenabled</key>
<false/>
<key>relay_enabled</key>
<true/>
<key>relayiplist</key>
<array/>
<key>timeServiceStarted</key>
<string>2008-11-26 22:59:19 +0100</string>
</dict>
</plist>
Do you have any idea of what I should do to fix that problem ?
Thanks !
alex

Brandon Macinnis wrote:
Dnar,
Thanks for the follow up bit about using the smbutil statshares command. I used that and could confirm that I am also able to force it to connect with smb2. Oddly though, in the stat share info it still says "AUTO_NEGOTIATE"
SMB_NEGOTIATE AUTO_NEGOTIATE
SMB_VERSION SMB_2.1
But maybe that just means something else and not the fact that it did not auto negotiate to SMB. I guess for now this will be what I have to do to use smb2.
I think in this case the AUTO_NEGOTIATE merely means it will auto negotiate a connection between SMB1, SMB2, and (from your data) also SMB2.1 this would have nothing to do with auto negotiating between SMB2 and AFP, which from this thread appears broken.
I also would like to thank Brandon for the tip about smbutil statshares, I had been looking for a simple way to tell what version of SMB was being used to test my NAS.
For everyone's benefit, it would appear from the above that whilst Apple advertise Mavericks as using SMB2 they have gone as far as implementing SMB2.1 and merely list it only as SMB2 for simplicity and due to the fact there is not a huge different between SMB2 and SMB2.1
See http://en.wikipedia.org/wiki/Server_Message_Block#SMB_2_and_3

Dhcp server won't admit my Arch Linux (though Win's have no problems)

1. Generally my dhcpcd works fine in every network (and always has, I have not changed anything substantial).
2. Currently I am in a network (for just a couple of weeks) in which it does not.
3. The network will ignore all my dhcp requests over both network devices, enp1s0 and wlp2s0 (ethernet and wifi)
4. When trying the same from Windows (dual boot), the dhcp client works brilliantly (i.e. the hardware is fine)
5. I can force entry into the cable network by simply assigning an IP address and setting netmask and gateway as was configured by dhcp when I tried from Windows
6. For wifi this does not work. More specifically it works for a brief moment if (and only if) I was connected from Windows immediately before and assign myself the same IP address (I can ping the gateway and also 8.8.8.8). After this moment the network apparently kicks me out (cannot ping anything any more, nothing answers). dhcpcd inform (dhcpcd -s <IP Adress>) does not fare better.
7. I tried changing some of the settings in dhcpcd.conf that have been given as reasons for similar problems in the forums, archwiki, or somewhere else, including exchanging 'duid' for 'clientid', and commenting out 'require dhcp_server_identifier'. Does not help. My dhcpcd.conf, see below.
8. dhclient does not work either.
What I want: Connect to the internet via wifi from Arch.
I guess this comes down to making the dhcp server believe my Arch was one of the Windowses it is used to. How do I do that?
I understand that dhcp does not involve clients revealing their operating systems to the servers; but some configurations are likely different between Arch and Windows. I am not used to working with Windows and have no idea how to access the dhcp client configuration settings there (if this is even possible) to get an idea what exactly is different. Here is my dhcpcd.conf - any ideas what exactly about it displeases the server so much or what I might change or add to make the server more pleasantly inclined?
dhcpcd.conf
hostname
clientid
#duid
persistent
option rapid_commit
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
option ntp_servers
#require dhcp_server_identifier
nohook lookup-hostname
noipv4ll
I would include the logs as well, but they are boring beyond belief, do not contain anything except for dhcpcd trying and failing with timeout.

Thanks, MoonSwan & ewaller,
MoonSwan wrote:Windows' IP address and network settings navigate to: Control Panel -> Network and Internet -> Network Connections -> Click on Device Here (WIFI or LAN) -> Properties and from there you should be able to see the settings you need to figure out what's going on in Windows.
Found that, There are a lot of "Advanced properties", for instance "Bandwidth Capacity" is set to "11b/g: 20MHz", "BSS Mode" is set to "802.11n Mode", "Fragmentation Threshold" to "2346" (whatever that may mean) ... etc. Unfortunately, I cant copy any of that; most of it also seems rather unimportant; also I left all this on its default setting when I followed the instructions on how to connect to this wifi on Windows.
However, here is some information I managed to squeeze out of the pathetic, pittyful Windows terminal which they call the "Comand Line"
C:\Windows\system32> ipconfig /all
<...>
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : <the network name>
Description . . . . . . . . . . . : <hardware description> 802.11b/g/n (2.4GHz)
Physical Address. . . . . . . . . : <the mac address>
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : <some ipv6> %13(Preferred)
IPv4 Address. . . . . . . . . . . : <the ipv4> (Preferred)
Subnet Mask . . . . . . . . . . . : <subnet mask>
Lease Obtained. . . . . . . . . . : Fri, 23. May 2014 19:47:10
Lease Expires . . . . . . . . . . : Fri, 23. May 2014 21:17:09
Default Gateway . . . . . . . . . : <gateway ip>
DHCP Server . . . . . . . . . . . : <some ip that is not part of the local subnet>
DHCPv6 IAID . . . . . . . . . . . : 319352249
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-9F-0F-D6-E0-DB-55-CF-26-6
DNS Servers . . . . . . . . . . . : <a few dns server ip's>
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : <some ipv6> (Preferred)
Link-local IPv6 Address . . . . . : <another ipv6> %12(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter 6TO4 Adapter:
Connection-specific DNS Suffix . : <the network name>
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : <some ipv6> (Preferred)
Default Gateway . . . . . . . . . : <another ipv6>
<yet another ipv6>
DNS Servers . . . . . . . . . . . : <the same ipv4 dns server ip's as above>
NetBIOS over Tcpip. . . . . . . . : Disabled
C:\Windows\system32> netsh wlan show all
Wireless System Information Summary
(Time: 23.05.2014 20:38:49 W. Europe Daylight Time)
=======================================================================
============================== SHOW DRIVERS ===========================
=======================================================================
Interface name: Wireless Network Connection
Driver : <hardware description> 802.11b/g/n (2.4GHz)
Vendor : Broadcom
Provider : Broadcom
Date : 21.01.2012
Version : 6.20.55.31
INF file : C:\Windows\INF\oem25.inf
Files : 5 total
C:\Windows\system32\DRIVERS\BCMWL664.SYS
C:\Windows\system32\bcmihvsrv64.dll
C:\Windows\system32\bcmihvui64.dll
C:\Windows\system32\drivers\vwifibus.sys
C:\Windows\system32\bcmwlcoi.dll
Type : Native Wi-Fi Driver
Radio types supported : 802.11n 802.11g 802.11b
FIPS 140-2 mode supported : Yes
Hosted network supported : Yes
Authentication and cipher supported in infrastructure mode:
Open None
Open WEP
Shared None
Shared WEP
WPA2-Enterprise TKIP
WPA2-Personal TKIP
WPA2-Enterprise CCMP
WPA2-Personal CCMP
WPA2-Enterprise Vendor defined
WPA2-Enterprise Vendor defined
Vendor defined Vendor defined
Vendor defined Vendor defined
Vendor defined TKIP
Vendor defined CCMP
Vendor defined Vendor defined
Vendor defined Vendor defined
WPA-Enterprise TKIP
WPA-Personal TKIP
WPA-Enterprise CCMP
WPA-Personal CCMP
Authentication and cipher supported in ad-hoc mode:
WPA2-Personal CCMP
Open None
Open WEP
IHV service present : Yes
IHV adapter OUI : [00 10 18], type: [00]
IHV extensibility DLL path: C:\Windows\System32\bcmihvsrv64.dll
IHV UI extensibility ClSID: {aaa6dee9-31b9-4f18-ab39-82ef9b06eb73}
IHV diagnostics CLSID : {00000000-0000-0000-0000-000000000000}
=======================================================================
============================= SHOW INTERFACES =========================
=======================================================================
There is 1 interface on the system:
Name : Wireless Network Connection
Description : 802.11b/g/n (2.4GHz)
GUID : 6d122ca5-cdc2-42d1-a1fb-3754098b19eb
Physical address : <the mac address>
State : connected
SSID : <ssid>
BSSID : <access point mac address>
Network type : Infrastructure
Radio type : 802.11n
Authentication : WPA2-Enterprise
Cipher : CCMP
Connection mode : Auto Connect
Channel : 1
Receive rate (Mbps) : 72
Transmit rate (Mbps) : 72
Signal : 83%
Profile : <ssid>
Hosted network status : Not available
=======================================================================
=========================== SHOW HOSTED NETWORK =======================
=======================================================================
Hosted network settings
Mode : Disallowed
Settings : <Not configured>
Hosted network status
Status : Not available
=======================================================================
============================= SHOW SETTINGS ===========================
=======================================================================
Wireless LAN settings
Show blocked networks in visible network list: No
Only use GP profiles on GP-configured networks: No
Hosted network mode allowed in WLAN service: No
Allow shared user credentials for network authentication: Yes
Block period: Not Configured.
Auto configuration logic is enabled on interface "Wireless Network Connection"
=======================================================================
============================== SHOW FILTERS ===========================
=======================================================================
Allow list on the system (group policy)
<None>
Allow list on the system (user)
<None>
Block list on the system (group policy)
<None>
Block list on the system (user)
<None>
=======================================================================
=========================== SHOW CREATEALLUSER ========================
=======================================================================
Everyone is allowed to create all user profiles.
=======================================================================
============================= SHOW PROFILES ===========================
=======================================================================
Profiles on interface Wireless Network Connection:
Group policy profiles (read only)
<None>
User profiles
All User Profile : <ssid>
<other profile names>
=======================================================================
========================== SHOW PROFILES NAME=* =======================
=======================================================================
Profile eduroam on interface Wireless Network Connection:
=======================================================================
Applied: All User Profile
Profile information
Version : 1
Type : Wireless LAN
Name : <ssid>
Control options :
Connection mode : Connect automatically
Network broadcast : Connect only if this network is broadcasting
AutoSwitch : Do not switch to other networks
Connectivity settings
Number of SSIDs : 1
SSID name : "<ssid>"
Network type : Infrastructure
Radio type : [ Any Radio Type ]
Vendor extension : Not present
Security settings
Authentication : WPA2-Enterprise
Cipher : CCMP
Security key : Absent
802.1X : Enabled
EAP type : Microsoft: Protected EAP (PEAP)
802.1X auth credential : Machine or user credential
Cache user information : Yes
<other profiles ...>
=======================================================================
======================= SHOW NETWORKS MODE=BSSID ======================
=======================================================================
Interface name : Wireless Network Connection
There are 4 networks currently visible.
SSID 1 : eduroam
Network type : Infrastructure
Authentication : WPA2-Enterprise
Encryption : CCMP
BSSID 1 : <other access point ssid>
Signal : 2%
Radio type : 802.11n
Channel : 11
Basic rates (Mbps) : 1 2 5.5 11
Other rates (Mbps) : 6 9 12 18 24 36 48 54
BSSID 2 : <other access point ssid>
Signal : 0%
Radio type : 802.11n
Channel : 11
Basic rates (Mbps) : 1 2 5.5 11
Other rates (Mbps) : 6 9 12 18 24 36 48 54
BSSID 3 : <access point ssid>
Signal : 87%
Radio type : 802.11n
Channel : 1
Basic rates (Mbps) : 1 2 5.5 11
Other rates (Mbps) : 6 9 12 18 24 36 48 54
BSSID 4 : <other access point ssid>
Signal : 0%
Radio type : 802.11n
Channel : 1
Basic rates (Mbps) : 1 2 5.5 11
Other rates (Mbps) : 6 9 12 18 24 36 48 54
SSID 2 : <...>
What I find odd is this "Taredo Tunneling Pseudo-Interface". As a matter of fact, I have not the slightest idea if this is happening inside this local Windows I have here or if this is something real in the network configuration (on the other side of the access point)... It apparently should tunnel IPv6 to IPv4 and/or vice versa. However, why would there be two connections over the same network interface (IPv6 and IPv4)...
What is odd as well is that the DHCP server is not part of the subnet my Windows is in. It just seems to announce IP, netmask, gateway to the Windows ... (the gateway is in the subnet). Could it be that the Linux dhcp client does not accept something like that. No, that's unlikely, right? dhcpcd -d should have reported this...
MoonSwan wrote:Btw, love the name,
Thanks. Likewise
MoonSwan wrote:it's nice to see such a name after seeing so many that are intentionally hurtful to others of any stripe in a rainbow.
Actually, I always felt that the Arch Forum is quite tolerant in this respect. (And so is reddit, but of course, you are right, there are places on the internet where you can run into a lot of assholes. Kind of like in the real world... Quite frustrating.)
ewaller wrote:I guess it could be a MAC problem. but I don't know.
Unlikely; on windows the mac address is the same.
ewaller wrote: Can you get to the router logs? Can you see if the router saw a solicitation?
no. and given their network configuration I don't suppose the IT people here would be very forthcoming if I asked them. Their helpdesk said that they couldn't help me since my laptop was not one of their computers.
ewaller wrote:Also, (just a sanity check) are you sure you are connected to the correct access point? But that does not make sense -- you said this happens on wired as well sad
Dang.
I am. It's WPA2 encrypted & I only have access data to this one wifi network. (To avoid confusing everyone with mentioning too many different things, I did not detail this in the original post. I am accessing it using wpa_supplicant running in a terminal; wpa_supplicant works fine says "connection succeeded" etc. So the problem is not in the WPA/ wifi-connection layer but really in the IP/dhcp layer.)
ewaller wrote:Is this a corporate environment? A school perhaps?
Yes, a university. They have someone working here who went through great lengths to make it difficult for people to connect to the internet.

ASA as DHCP server for WLC2106 and LAP

Hi,
First off i aplolgize for asking something that seems to have been asked before but i am getting conflicting answers and wanted someone to give a definitive answer.
Setup:
     ASA5505 ---------------- WS-C3750G -----------------WLC2106 -------------------------------AIR-LAP1131
(DHCP SERVER)           (simple config)          (dhcp proxy disabled)           (is requesting dhcp from ASA)
ASA5505 - ASA 8.2(1)
WLC2106 - 7.0.98.0 (tried 6.0.99.4 as well)
AIR-LAP1131 - 12.4(23c)JA
Problem:
The ASA5505 is giving addresses to multiple devices, i tested it with the AP plugged directly into the ASA and it worked great. The problem is that the WLC2106 seems to be altering the DHCP requests somehow and thus making the ASA5505 not respond to them. The AP gets an ip address and associates to the WLC if plugged into the 3750, or the ASA directly. Just not when plugged into the WLC2106 ports.
Research:
https://supportforums.cisco.com/message/1268269#1268269
https://supportforums.cisco.com/message/3037259#3037259
https://supportforums.cisco.com/message/1302468#1302468
https://supportforums.cisco.com/message/926529#926529
I have read quite a few posts with people basically saying you cannot use the ASA as the DHCP server with the WLC because of how the WLC relays the requests. BUT: (this is important) There are some documents that say with WLC version 4.2 and above you have the option of turning off dhcp proxy mode to enable bridging mode thus elminating the probem and all DHCP requests get forwarded without modification. Please see here for suggested solution to this issue:
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a0080af5d13.shtml#topic2
*Interoperability issues can exist between a controller with DHCP proxy enabled and devices acting as both a firewall and DHCP server. This is most likely due to the firewall component of the device as firewalls generally do not respond to proxy requests. To work around this issue, disable DHCP proxy on the controller.
Help please:
I have tried this but maybe im missing something. I have tried with proxy enabled and disabled. Can anyone verify this is supposed to work for me please? I input "config dhcp proxy disable" and verified proxy is now disabled. Yet i do not see any responces from my DHCP server to my AP's requests when going through the WLC. It works fine when plugging the AP into the ASA or 3750. DHCP server is working. Is the above suggested work around not a valid solution? Did i miss something? Do i need specific software versions on my devices? Is this a bug in my software versions?
Any help is greatly appreciated. Let me know if anyone has questions. Thanks,
Kyle

I do not see any debug output on the ASA5505 when the AP is connected through the WLC. Debug output from WLC2106 below:
(Cisco Controller) >show debug
MAC debugging .............................. disabled
Debug Flags Enabled:
dhcp packet enabled.
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >show dhcp proxy
DHCP Proxy Behaviour: disabled bootp-broadcast disabled
(Cisco Controller) >
(Cisco Controller) >*DHCP Socket Task: Nov 16 10:56:39.931: 00:1d:a1:ed:c8:d4 DHCP received op BOOTREQUEST (1) (len 310,vlan 0, port 8, encap 0xec00)
*DHCP Socket Task: Nov 16 10:56:39.932: 00:1d:a1:ed:c8:d4 DHCP processing DHCP DISCOVER (1)
*DHCP Socket Task: Nov 16 10:56:39.932: 00:1d:a1:ed:c8:d4 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Nov 16 10:56:39.932: 00:1d:a1:ed:c8:d4 DHCP   xid: 0x126b (4715), secs: 0, flags: 80
*DHCP Socket Task: Nov 16 10:56:39.932: 00:1d:a1:ed:c8:d4 DHCP   chaddr: 00:1d:a1:ed:c8:d4
*DHCP Socket Task: Nov 16 10:56:39.933: 00:1d:a1:ed:c8:d4 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Nov 16 10:56:39.933: 00:1d:a1:ed:c8:d4 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Nov 16 10:56:39.933: 00:1d:a1:ed:c8:d4 DHCP dropping REQUEST from STA with invalid mobility state 'Unassociated' (0)
*DHCP Socket Task: Nov 16 10:56:42.939: 00:1d:a1:ed:c8:d4 DHCP received op BOOTREQUEST (1) (len 310,vlan 0, port 8, encap 0xec00)
*DHCP Socket Task: Nov 16 10:56:42.940: 00:1d:a1:ed:c8:d4 DHCP processing DHCP DISCOVER (1)
*DHCP Socket Task: Nov 16 10:56:42.940: 00:1d:a1:ed:c8:d4 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Nov 16 10:56:42.940: 00:1d:a1:ed:c8:d4 DHCP   xid: 0x126b (4715), secs: 0, flags: 80
*DHCP Socket Task: Nov 16 10:56:42.940: 00:1d:a1:ed:c8:d4 DHCP   chaddr: 00:1d:a1:ed:c8:d4
*DHCP Socket Task: Nov 16 10:56:42.941: 00:1d:a1:ed:c8:d4 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Nov 16 10:56:42.941: 00:1d:a1:ed:c8:d4 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Nov 16 10:56:42.941: 00:1d:a1:ed:c8:d4 DHCP dropping REQUEST from STA with invalid mobility state 'Unassociated' (0)
*DHCP Socket Task: Nov 16 10:56:46.938: 00:1d:a1:ed:c8:d4 DHCP received op BOOTREQUEST (1) (len 310,vlan 0, port 8, encap 0xec00)
*DHCP Socket Task: Nov 16 10:56:46.938: 00:1d:a1:ed:c8:d4 DHCP processing DHCP DISCOVER (1)
*DHCP Socket Task: Nov 16 10:56:46.938: 00:1d:a1:ed:c8:d4 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Nov 16 10:56:46.938: 00:1d:a1:ed:c8:d4 DHCP   xid: 0x126b (4715), secs: 0, flags: 80
*DHCP Socket Task: Nov 16 10:56:46.939: 00:1d:a1:ed:c8:d4 DHCP   chaddr: 00:1d:a1:ed:c8:d4
*DHCP Socket Task: Nov 16 10:56:46.939: 00:1d:a1:ed:c8:d4 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Nov 16 10:56:46.939: 00:1d:a1:ed:c8:d4 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Nov 16 10:56:46.939: 00:1d:a1:ed:c8:d4 DHCP dropping REQUEST from STA with invalid mobility state 'Unassociated' (0)
*DHCP Socket Task: Nov 16 10:57:05.034: 00:1d:a1:ed:c8:d4 DHCP received op BOOTREQUEST (1) (len 310,vlan 0, port 8, encap 0xec00)
*DHCP Socket Task: Nov 16 10:57:05.035: 00:1d:a1:ed:c8:d4 DHCP processing DHCP DISCOVER (1)
*DHCP Socket Task: Nov 16 10:57:05.035: 00:1d:a1:ed:c8:d4 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Nov 16 10:57:05.035: 00:1d:a1:ed:c8:d4 DHCP   xid: 0x126c (4716), secs: 0, flags: 80
*DHCP Socket Task: Nov 16 10:57:05.035: 00:1d:a1:ed:c8:d4 DHCP   chaddr: 00:1d:a1:ed:c8:d4
*DHCP Socket Task: Nov 16 10:57:05.036: 00:1d:a1:ed:c8:d4 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Nov 16 10:57:05.036: 00:1d:a1:ed:c8:d4 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Nov 16 10:57:05.036: 00:1d:a1:ed:c8:d4 DHCP dropping REQUEST from STA with invalid mobility state 'Unassociated'
It keeps seeing the Discover messages but never gets any responce from the ASA. What does that message mean "dropping REQUEST from STA with invalid mobility state 'Unassociated'" ? I know the STA is the AP but why is it dropping the request?
Here is the debug output from the ASA:
ASA5505lab# show debug
debug dhcpd packet enabled at level 128
debug dhcpd event enabled at level 128
ASA5505lab#
DHCPD: checking for expired leases.
DHCPD: checking for expired leases.
DHCPD: checking for expired leases.
DHCPD: checking for expired leases.
DHCPD: checking for expired leases.
DHCPD: checking for expired leases.
(IT NEVER SEE'S ANY MESSAGES OR SHOWS ME ANY BLOCKED REQUESTS OR ANYTHING)
(Now if i move the AP to the PoE ports directly on the ASA5505 you will see the AP get an IP)
DHCPD: Server msg received, fip=ANY, fport=0 on inside interface
DHCPD: DHCPDISCOVER received from client 0100.1da1.edc8.d4 on interface inside.
DHCPD: Sending DHCPOFFER to client 0100.1da1.edc8.d4 (192.168.143.4).
DHCPD: Total # of raw options copied to outgoing DHCP message is 0.
DHCPD: broadcasting BOOTREPLY to client 001d.a1ed.c8d4.
DHCPD: Server msg received, fip=ANY, fport=0 on inside interface
DHCPD: DHCPREQUEST received from client 0100.1da1.edc8.d4.
DHCPD: Sending DHCPACK to client 0100.1da1.edc8.d4 (192.168.143.4).
DHCPD: Total # of raw options copied to outgoing DHCP message is 0.
DHCPD: broadcasting BOOTREPLY to client 001d.a1ed.c8d4.
ASA5505lab#
ASA5505lab# show dhcpd binding
IP address       Hardware address        Lease expiration        Type
192.168.143.4    0100.1da1.edc8.d4            3581 seconds    Automatic
192.168.143.5 0063.6973.636f.2d30.           1911 seconds    Automatic
                 3031.662e.3965.6234.
                 2e35.3034.302d.566c.
                 31
ASA5505lab#
ASA5505lab#
So the ASA5505 is working when the AP is plugged directly into the ASA or a 3750 on the same network. Only when connected through the WLC i do not see any messages on the ASA. Is there something else i need setup on the WLC2106 besides turning off dhcp proxy?
Thanks,

How to DHCP Server with NO ROUTER on Server Admin panel field?

Hi all!
I'm having a little problem.
I have two completely different networks, with different purposes, one is 10.0.10.X and the other is 192.168.10.X. My networks is like this:
Internet------Wifi Router (192.168.10.250) -----iMacs AirPoirt (192.168.10.X)
MacPro (10.0.10.100)-----iMacs Ethernet (10.0.10.X)
Great, is so simple. So I had a DHCP server (Windows blerg) on the 10.0.10.X (NOT MAC OS X SERVER) and everything works perfect, since on the Windows DHCP Server I'm not forced to fill the router/gateway and leaving it blank makes the iMacs have just one router/gateway from the 192.168.10.X lease from the Wifi Router.
Now I'm planning to migrate the DHCP Service to the Mac OS X Server (Snow Leopard Server), I fiddled a bit and found that I can't use DHCP Server on Mac OS Server leaving router field blank and if I type ANYTHING, my iMacs will NOT access the internet through 192.162.10.X since now there's two gateways (from 10.0.10.X that Server Admin panel forced me to fill and from 192.168.10.X that HAS to have one gateway and it's the correct one).
I've tried to fill with the 192.168.10.X gateway but throws a warning saying that is not on the same subnet.
I really don't want to re-route or mix the traffic for many reasons.
So I ask, is there any possible way to NOT fill or bypass or do anything to make DHCP Server service from Mac OS X Server not have a gateway/router?
The only way I'm managing to do it now is to use manually entered IPs on the iMacs, but it's 10 iMacs and I guess for some services like netboot etc I need DHCP.
Cheers,

Lets assume that before you had computers with both Ethernet and WiFi connections, they were able to access the Internet via WiFi and talk amongst themselves via Ethernet. The Ethernet addresses were not (in theory) accessible from the WiFi network and hence not accessible from the Internet. Presumably you intended this for security reasons.
If so, you were completely mistaken. Even if you turned on a Software firewall on each of these iMacs to in theory block traffic going between the two networks you still have a potentially insecure setup. This is because traffic can reach the iMacs via WiFi. Once hypothetical malicious traffic has invaded an iMac via WiFi it can take control over the computer and within that computer reach out via its Ethernet port to other Ethernet computers.
The only way to ensure complete security is not to have any link between the two networks at all. If one of the computers is linked to both then you have a potential path for attacks to travel across.
So what are you really trying to do? If you want two totally separate networks with one having absolutely no link to the outside world then this is simple and is as follows.
NETWORK1 Internet------Wifi Router (192.168.10.250) -----iMacs AirPoirt (192.168.10.X)
NETWORK2 MacPro (10.0.10.100)-----different iMacs Ethernet (10.0.10.X) with WiFi turned off
You could define the default gateway for NETWORK2 as being the DHCP server itself. No computer on NETWORK2 would be able to access the Internet and hence it would be totally secure.
If however you want all computers to be able to access the Internet then you need a link between them. Are you merely wanting to segregate WiFi traffic as it might be insecure and evesdropped on? If so then the following is a better approach
                         WiFi clients (192.168.10.x)
Internet ----- AirPort Extreme (192.168.10.250) ------ Hardware FireWall does NAT (10.0.10.1) ---- MacPro (10.0.10.100) ---- iMacs via Ethernet (10.0.10.x)
The WiFi clients would not be able to directly access your 10.0.10.x network as they are blocked by the FireWall. However if you have say a Laptop that you want ot use on WiFi but still access your server on your internal secure LAN you would do this by having the server run the VPN server component. The WiFi client would then connect via the VPN server and this would ensure all the network traffic going over the WiFi is encrypted using industry standard IPSec encryption. In this second scenario the MacPro (presumably your server) would have the FireWall as the default gateway, and the FireWall would have the Internet router as its default gateway. You could set the Firewall to forward VPN traffic to the server or use the second Ethernet port on the server to accept VPN traffic on the 192.168.10.x LAN.
This is my own setup is something like
                        AirPort
                           |
Internet router --- Public IP range --- (WAN) FireWall (LAN) --- LAN Switch --- Server Port1 for normal traffic
                                                 |(DMZ)                                    |
                                                 +----------------------------- Server Port2 for VPN

Bridging through built-in wireless to ethernet DHCP server

[originally posted here: Tiger Forums > Getting Online & Networking, where one suggestion was to try this forum]
I have a 1Gb ethernet LAN with my own DHCP, etc. servers, and an 802.11g WAP bridging to it using WPA2/AES. I've recently added two new Macs: an iMac connected to the ethernet and a MacBook connecting through its built-in wireless. This all works fine.
Since both Macs are 802.11n capable (with the addition of the $2 addon, which I've done), it occurred to me that I should be able to set up the built-in airport in the iMac as an 802.11n WAP that the MacBook could connect to as its preferred wireless network when the iMac's turned on, tripling it's connection speed to my LAN, and falling back to the 802.11g WAP when the iMac's not on.
I was able to do this pretty simply by setting up internet (LAN in my case) sharing on the iMac, and I could indeed get an 802.11n connection to it from the MacBook when the iMac was on, and fairly seamless failover to the 802.11g WAP when the iMac wasn't available.
Clearly, all the pieces are present to make my plan work, but there are two stumbling blocks:
1. I can't find a way to get the iMac to bridge directly to the ethernet, so that the central DHCP servers provide the configuration for the MacBook. I don't see an obvious way to allow DHCP, but not use the server built into the iMac (or configure it to hand out the addresses I want). It looks an awful lot like the iMac is NAT'ing the wireless to the ethernet, which is definitely not what I want.
Is there no way to configure the iMac's wireless as a passthrough (bridge) to the ethernet so it acts as a WAP (even if it only accepts one connection at a time)?
2. I have configured both Macs' wireless to connect to my WAP with WPA2/AES, and they do so just fine. When setting the iMac wireless up for internet sharing, why can't I set the same security options - it only offers me WEP, which I'm not willing to use.
I know the hardware can handle what I want, as can the BSD underpinnings of OS X (all of my LAN's servers run BSD variants), I just don't know how to configure it.
Can someone help?
Thanks.

>It looks an awful lot like the iMac is NAT'ing the wireless to the ethernet, which is definitely not what I want.
That's exactly what it does. The 'Internet Sharing' option enables NAT.
This may or may not be a problem, though - what is the MacBook missing by getting its configuration from the iMac rather than your regular DHCP server?
(by default, when you turn on internet sharing the OS starts up a DHCP server on the shared interface).
You might be able to get what you want by just turning on IP forwarding rather than the whole NATD/DHCPD package, but I'm not sure:
<pre class=command>sudo sysctl -w net.inet.ip.forwarding=1</pre>
but you'd have to try it to see.
> When setting the iMac wireless up for internet sharing, why can't I set the same security options - it only offers me WEP, which I'm not willing to use
I don't know the technical reason for it, but I seem to recall that computer-to-computer wireless networks always (and only) use WEP. I don't know if this is because WPA isn't possible or if they just haven't gotten around to adding it, but WEP is your only option.

No contact with DHCP server when using VPN Client

Pretty weird problem I discovered recently.
We use the VPN Client to connect to a 1841 router. Everything works fine except for one small thing.
The client do not send out _any_ traffic if the destination is the ip-address of the DHCP-server the client got its original ip-address from.
This is verified by Wireshark. A ping on the client do not produce any ESP packets towards the VPN concentrator. No matter what traffic you try actually.
Discovered this when wanting to use Remote Desktop towards the Windows Server that is the local DHCP server and was not able to connect. Then tested ping and still no response. That made me look closer and found out that I could not communicate at all with the DHCP server.
As I said, pretty weird.
Anyone else have seen this? Anyone have a solution? Right now I use OpenVPN instead when I need to control that server.
- Roger

Hi and thanks for responding.
Nothing here apart from being unable to send any packets to the dhcp-server. No problem sending to any other system on the same subnet. The same happens when I connect my pc to another subnet that is served by another dhcp-server. Then I can not connect to _that_ dhcp-server. I can then of course connect to the previous dhcp-server.
I mean _no_ packets are generated out the client at all if the destination are your dhcp-server. No problem with the packet being blocked by a firewall or anything like that. Ping another system on the same subnet as the dhcp-server and the client happily generates ESP packets and sends them to the vpn-concentrator.
I do not know if it was clear enough in the first post so I am saying it here: the vpn-concentrator gives out the ip for the vpn connection. The dhcp-server I can not connect to is the server that gives the client its ip-address _before_ starting up the vpn client.
We use this vpn system so the IT personell will be able to connect to restricted resources from their laptops anywhere in the network, also when using wireless.
This was discovered when one admin wanted to connect from his laptop to a server that also happened to be the dhcp-server that had given his laptop his ip address before he used vpn.
Should be easy enough for anyone else to test. Just ping your dhcp-server after starting the vpn connection. No RFC 1918 addresses of course, there must be a route from your vpn-concentrator to your dhcp-server and at least icmp echo must be open through any firewall/acl.
The vpn version is 4.8.00.0440 on Windows XP configured to not allow local LAN access. I might test this with other versions/OS'es when I have the time.
Regards,
- Roger

Can I use DHCP snooping and IOS DHCP server on the same switch stack

Hello,
I am shortly going to be deploying a Cisco CallManager solution for a customer whose network comprises stacks of Catalyst 3850 switches.
There is no separate core/server farm switch so the CallManager servers, voice gateways and IP phones will all plug into the same stack and be in the same VLAN (not my choice!).
For security we want to enable DHCP snooping and were planning on using the IOS DHCP server on the Catalyst switch stack.
Will this work? - when I enable DHCP snooping in networks with separate access layer switches I set the uplinks to the core as trusted links.
I am not sure whether DHCP snooping will work in this case. Do I need to set the VLAN interface on the switch as trusted, is this even possible?
Unfortunately I do not have access to a layer 3 switch to test this at the moment.
Thanks

Nope. That's the issue.
They'll sync on a third device acting as a hotspot, but the device sending a signal is not "on" the network it creates so the airport is all by itself on that network. At least that is what it looks like to me. Anyone have another take on it? Seems pretty silly that an iPad can put out a wifi signal, an Airport Express can receive a wifi signal, and yet there is no simple way to get them to communicate under this particular condition.

Can I use ASA to be a DHCP Server use in WLC wireless Client

I want to use ASA to be a DHCP Server for Wireless Client not it can't.
I check the debug log in WLC, I confirm the WLC have send the request to ASA.
In the ASA, it don't have any hits in the rule when the WLC send the DHCP relay request.
I have try don't use dhcp relay in WLC but don't success. Anybody have the same case with me? And Is the ASA can't support DHCP relay agent to request to get the IP Addr.
P.S. In the Network Design limitation so I can't use WLC to be DHCP Server.
Equipment:
ASA5510
WLC4402
How can I fix it.
Thank you very much

The issue is that the ASA doesn't accept DHCP requests from a relay agent, only broadcast DHCP requests. In the 4.2 version for the controllers there is now an option so you can change the way the controller forwards DHCP requests so that it is sent as a broadcast and not from a relay agent.

Can you use the Airport Express A1264 as an AP and a DHCP server at the same time?

Can you use the Airport Express A1264 as an Access Point and a DHCP server at the same time?
I would like to use it as a DHCP server and AP at the same time in my LAN (no internet, just local machines through a few switches). I was lead to belive this could be the case from a few networking friends that haven't been friendly enough to help me out setting it up.

I need it to act as a dLink/Cisco/Linksys/etc basic wifi router, in the fact that you can access it via wifi, and it will spit out DHCP addresses (192.168.1.xxx) to everything wired downstream of it.
I want to simultaniously provide a Wifi connection and a LAN connection at the same time
Thanks,
BRad

Can I use my WRT54G as a DHCP server only? I've got 5 dynamic IP's from Time Warner..

Hi everyone, I'm wondering if I can use my WRT54G as a DHCP server only only my network, without having to have any of my PC's plugged into it's router ports? I looked at the settings but I couldn't get it to work.
Here's why: I just got Time Warner Business Class cable internet which comes with 5 dynamic IP's. I want each computer, well 4 of them at least and 1 for the WRT54G, to have a unique IP when accessing the internet, and the other computers (5 more computers) to use the DHCP server in the WRT54G to get a NAT IP for use on the internet.
We play Diablo II on the internet and only 4 computers can be connected through 1 IP, so that limits us in my current configuration.
Current Equipment: One WRT54G, one Netgear GS116 16 port gigabit non-managed switch. One Time Warner Cable modem. Also attached to the network is one HP network printer, a Buffalo LinkStation NAS and a Zensonic Network DVD player.
Current config: Cable modem --> WRT54G --> Netgear switch.
Ideal config: Cable modem --> Netgear switch --> WRT54G.
With my current config, I am not taking advantage of the 5 dynamic IP's, but all the computers connected to the Netgear switch or the WRT54G can connect to the internet and the NAS.
So my ideal config (where I don't have to buy anything and where all the computers can print and access the NAS) is to connect all the computers and devices to the Netgear Switch and somehow force 4 of the computers and the WRT54G to get a dynamic IP from the cable modem, while the other computers and devices use the DHCP server on the WRT54G to get to the internet.
Is this possible?
I called Time Warner Cable and they weren't any help. I called the Linksys sales department and they weren't of much help either.
I suppose that I could purchase a new 8 port switch and attach 4 computers, the cable modem and the WRT54G to it. Then attach the Netgear to the WRT54G to accomodate the printer, NAS, and the other 5 computers. But in that senario, the 4 computers connected to the new switch can't print and can't reach the NAS. And geez, some computers would have to go through 3 devices to reach the internet, which has got to slow them down.
I did read about the Linksys EFG120 which has a DHCP server, but at $400 and only 120 gigs, it doesn't work for me.
I called Time Warner and the cost of more dynamic IP's is prohibitive, I'm already paying $79 a month for this internet and they want another $50 a month for 7 more dynamic IP's and that wouldn't help my NAS or my printer.
The cost of a 16 port gigabit switch with DHCP is an amazing $800 or so, which is out of the question.
Sorry for being so long winded and thanks for reading this far. I'm looking forward to any replies.

That is a hell of a setup. I don't know if it would be easier and cheaper to either buy a real router like a Cisco, get fixed IP addresses and a RV042, or buy 4 network cards for the four of the five computers which need the internet access for gaming.
O.K. First your setup:
1. You wire the modem to the 6-port switch.
2. You connect the remaining 5 ports with the WAN ports of 5 WRTs with DHCP on the WAN interface.
3. You configure each WRT with unique LAN IP addresses in the same subnet, e.g. 192.168.1.1/255.255.255.0, 192.168.1.2, 192.168.1.3, 192.168.1.4, 192.168.1.5.
4. You turn off all DHCP servers except on one, e.g. 192.168.1.1. That router will be the default router and internet connection for any client which gets dynamic LAN addresses (as fallback or guests, I would not configure the NAS or printer with DHCP addresses if you have everything else on static IP addresses). You can certainly disable all DHCP servers if you want, too.
5. Now you connect all WRTs with each other.
5a. You connect port 1 of the 1st WRT with port 1 of the 2nd.
You connect port 2 of the 2nd with port 1 of the 3rd.
Port 2 of the 3rd with port 1 of the 4th.
Port 2 of the 4th with port 1 of the 5th.
(Do not create a loop connecting port 2 of the 5th with port 2 of the 1st!!)
5b. You buy another switch and connect each port 1 of each router with this switch. This has the advantage that you don't have a long cascade between the 1st and the 5th router like in 5a.
6. You connect all devices to the LAN.
6a. If you did 5a, you will probably put each computer to the router which internet connection it uses. The NAS and printer could go anywhere.
6b. If you did 5b, you hopefully bought a 16 or 24 port switch. Then you plug simply everything into that switch. Otherwise you can certainly use the free ports of the WRTs like in 6a.
7. You configure all your devices with static IP addresses. For instance,
IP 192.168.1.11
netmask 255.255.255.0
gateway 192.168.1.1
For the DNS servers I would highly recommend to use the DNS servers of your ISP directly and not use the relay on 192.168.1.1.
The gateway address defines through which router the computer connects to the internet.
8. You may still have to configure port forwardings on the router to the game computer if required for the game.
An interesting alternative to this setup might be to buy 4/5 network cards for the 4/5 computers with direct internet access. Then you use the one network card to connect to your single LAN behind your single WRT. The other network card goes into the switch behind the modem and has direct internet access. You then have to tell Windows which of the network cards has the default gateway for the internet connection (to prevent routing all traffic through the LAN and the WRT to the internet). One game computer would have to be behind the WRT.

DNS/DHCP app no longer sees DNS/DHCP server.

When I moved the majority of my Netware 6 servers to OES-NW last year, I started using iManager to handle admin duties for DNS and DHCP.
With a planned move to OES-L coming up, I tried accessing both services using the DNS/DHCP java console.
While I am able to log into that console, I am unable to see my DNS/DHCP server or any of the expected components for either service (DHCP pools, zone records, etc...).
I have tried both the console that is installable from the server and the newer LDAP-based version.
I have tried both 32 and 64-bit versions on XP and Windows 7, respectively.
Since I want to move those services to OES/Linux and the java console is the only mechanism that can administrate the services on that platform, I am perplexed.
My needs are simple, and I could easily move those duties to a SUSE server or even a Windows server, but that is not my preference.
Any ideas on where to begin troubleshooting are welcome.

On 06.08.2012 21:56, gathagan wrote:
>
> When I moved the majority of my Netware 6 servers to OES-NW last year, I
> started using iManager to handle admin duties for DNS and DHCP.
>
> With a planned move to OES-L coming up, I tried accessing both services
> using the DNS/DHCP java console.
>
> While I am able to log into that console, I am unable to see my
> DNS/DHCP server or any of the expected components for either service
> (DHCP pools, zone records, etc...).
>
> I have tried both the console that is installable from the server and
> the newer LDAP-based version.
> I have tried both 32 and 64-bit versions on XP and Windows 7,
> respectively.
>
> Since I want to move those services to OES/Linux and the java console
> is the only mechanism that can administrate the services on that
> platform, I am perplexed.
> My needs are simple, and I could easily move those duties to a SUSE
> server or even a Windows server, but that is not my preference.
>
> Any ideas on where to begin troubleshooting are welcome.
You have more than one DNS-DHCP locator object in your tree, and the
console is picking up a/the empty one. Find the proper object (look at
the other tab in consoleone or imanager to see if it's connected with
servers zones and the like), and delete the superflouos ones.
This is an *extremely* common problem when OES gets introduced into a
tree, as it by default creates new locator objects in the server
container, if it's not configured otherwise.
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de

I want to block DHCP Server

Similar Messages

Maybe you are looking for