DHCP start at x.x.x.45 to x.x.x.90 , witch subnetmask?

Hi, I can't find the answer.
Here is my situation,
Linksys- router as Gateway to the internet. IP-192.168.2.254
OSX-Server provinding Mail, web DHCP and so on. IP-192.168.2.11
Some Machines with static IP from 192.168.2.12 to 192.168.2.40
And some machines with static IP from 192.168.2.100 to 192.168.2.110
I want the DHCP to serve numbers between 192.168.2.45 to 192.168.2.90
So that the static IP's are out of the range.
My problem is that DHCP is not working properly.
These are the errors;
Nov 13 13:57:32 eps-amsterdam bootpd[1191]: can't open /etc/bootptab
Nov 13 13:57:32 eps-amsterdam bootpd[1191]: server name eps-amsterdam.eps
Nov 13 13:57:32 eps-amsterdam bootpd[1191]: interface en0: ip 192.168.2.11 mask 255.255.255.0
Nov 13 13:57:32 eps-amsterdam bootpd[1191]: subnets: Failed to convert 'nbover_tcpip_nameserver': Invalid IP address
I Think it must be the subnetmask but I don't know witch number to use.
In the DHCP setup teh settings are these;
Starting IP 192.168.2.12
Ending IP 192.168.2.90
Subnet Mask 255.255.255.0
Router 192.168.2.254
What am I doing wrong?

"Hmm... Do you have DNS entries for "server-leopard" ?"
No I don't have an entrie for that.
Would it be easier if I change the Sharing name to eps-amsterdam?
eps-amsterdam:~ edvandermeer$ nmblookup -U eps-amsterdam.eps -R server-leopard
querying server-leopard on 192.168.2.11
192.168.2.11 server-leopard<00>
eps-amsterdam:~ edvandermeer$ dig server-leopard.eps-amsterdam.eps
; <<>> DiG 9.4.2-P2 <<>> server-leopard.eps-amsterdam.eps
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48603
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;server-leopard.eps-amsterdam.eps. IN A
;; AUTHORITY SECTION:
eps. 3600 IN SOA eps-amsterdam.eps. ed.eps. 2008111701 86400 3600 604800 3600
;; Query time: 8 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Nov 17 14:20:30 2008
;; MSG SIZE rcvd: 89
.eps is a private domain
Ed

Similar Messages

  • Automatically starting DHCP on second ethernet interface in Solaris 8?

    Hello,
    In my current setup, I have a Solaris 8 server with two ethernet interfaces - elxl0, which is connected to my internal network and has a static IP, and elxl1, which is connected to a cable modem and gets its address via DHCP.
    When I reboot the machine, it brings both interfaces up, but does not start DHCP on elxl1 automatically. I have an empty /etc/hostname.elxl1, which I thought was supposed to tell the OS to use DHCP for that interface. I have to manually tell the interface to get an address using ifconfig auto-dhcp start.
    Is there a way to tell the OS to use DHCP for elxl1 without disturbing elxl0? It would make things significantly more convenient for me, since now I have to manually start DHCP, and then reload my IP Filter NAT rules.
    Any assistance you could provide would be greatly appreciated. Thanks!
    - Brad Williams

    I figured it out.
    What you have to do is add a file, /etc/dhcp.<interface>, in order to make this work. In my example, the file would be "/etc/dhcp.elxl1".

  • Dhcp on 8.4(4)

    We had upgraded 3 of our firewalls in the last week. Those were ASA 5510s
    and were running on 8.2(2)16 before. They were upgraded to 8.4(4) last week. We have
    Wireless Access Points in the external segment (outside firewall) and after the firewall
    was upgraded, we saw that 3 of our wireless APs could not get IPs (the DHCP server resides
    in internal LAN segment), while the other three APs got IPs. Rebooting the firewall also
    did not help. We then downgraded the firewall to 8.2(2)16 and all 6 APs immediately got
    IPs. Is there a bug related to DHCP relay on 8.4(4)?
    Thanks,
    Kashish

    I upgraded three ASAs (1 5505 and two 5510) to 8.4(4)3 and on all three ASAs which were providing DHCP services to connected networks stopped working.  Users could not get DHCP addresses from the ASAs running 8.4.4.3.
    I did packet captures from the desktop, basically I see the DHCP requests leaving the desktop, but no replies from the ASA.
    I downgraded the ASA to 8.4(4)1 and DHCP immediately starting working again. 
    I then upgraded back to 8.4.4.3.  DHCP failed again.  Downgraded the ASA to 8.4.4.1, then DHCP started working again. 
    Looks like a bug with ASA 8.4.4.3 and DHCP.

  • DHCP SERVER

    I am trying to set up DHCP on a sparc 10 server running solaris 8.I can successfully configure dhcp through dhcp config but when I try to start the dhcp server deamon I get this error message( error binding to udp socket address already in use).Any help with this problem would be greatly appreciated.

    Hi,
    kill -HUP inetd_pid
    kill bootd daemon
    netstat -a should not show an idle (or anything) on 67 or 68 UDP
    /etc/init.d/dhcp start
    Revert back.
    Thanks,
    Senthilkumar
    SUN - DTS

  • DHCP Client does not send host name to DHCP Server

    Hello,
    I installed Solaris 10 on VirtualBox and I cannot ping/ssh/telnet the virtual machine by its host name (even from the host computer) but only by it's ip.
    I tried everything I could find on internet with no success (I don't want to add the hostname in every hosts file on every computer because it's not really professionnal)
    I followed what said here: http://docs.oracle.com/cd/E26505_01/html/E27061/eyhuv.html#scrolltoc
    Can someone has an idea of what I can do or why this does not work.
    I installed a virtual Windows7 and an Ubuntu, and it worked perfectly.
    Any help would be grantly appreciated.
    Thank you
    Here is my current configuration:
    Oracle VM VirtualBox 4.3.8 (I choose "Oracle 10 10/09 and later (64 bit))
    Oracle Solaris 10 1/13
    Network: bridge with RealTek interface
    NB: I don't have access to dhcp server on my netgear router (access is disabled by my ISP)
    Files in /etc:
    dhcp.e1000g0 (empty)
    nodename (contains "thorgal")
    nsswitch.conf has following lines:
    hosts: files dns # Added by DHCP
    ipnodes: files dns # Added by DHCP
    networks:   files
    protocols:  files
    rpc:        files
    ethers:     files
    netmasks:   files
    bootparams: files
    hostname.e1000g0 (contains "inet thorgal")
    /etc/inet/hosts:
    ::1             localhost
    127.0.0.1       localhost loghost
    192.168.0.17    thorgal # Added by DHCP
    /etc/default/dhcpagent:
    REQUEST_HOSTNAME=yes
    PARAM_REQUEST_LIST=1,3,6,12,15,28,43
    .v6.PARAM_REQUEST_LIST=7,12,23,24,27,29
    I also try "ifconfig e1000g0 dhcp release" with no success
    the debugging of dhcpagent:
    # pkill -x dhcpagent
    # /sbin/dhcpagent -d1 -f &
    1088
    # ifconfig e1000g0 dhcp start
    /sbin/dhcpagent: debug: insert_pif: e1000g0: sdumax 1500, hwtype 1, hwlen 6
    /sbin/dhcpagent: debug: set_packet_filter: set filter 805869f (DHCP filter)
    /sbin/dhcpagent: debug: get_smach_cid: getting default client-id property on e1000g0
    /sbin/dhcpagent: debug: in state INIT; allowing start command on e1000g0
    /sbin/dhcpagent: debug: ipc_action_start: started start (command 4) on e1000g0
    /sbin/dhcpagent: debug: set_smach_state: changing from INIT to INIT_REBOOT on e1000g0
    /sbin/dhcpagent: debug: dhcp_selecting: host thorgal
    /sbin/dhcpagent: info: configure_v4_lease: setting IP netmask to 255.255.255.0 on e1000g0
    /sbin/dhcpagent: info: configure_v4_lease: setting IP address to 192.168.0.17 on e1000g0
    /sbin/dhcpagent: warning: configure_v4_lease: no IP broadcast specified for e1000g0, making best guess
    /sbin/dhcpagent: info: configure_v4_lease: using broadcast address 192.168.0.255 on e1000g0
    /sbin/dhcpagent: info: configure_v4_timers: e1000g0 acquired lease, expires Fri Mar 21 21:33:05 2014
    /sbin/dhcpagent: info: configure_v4_timers: e1000g0 begins renewal at Fri Mar 21 09:33:05 2014
    /sbin/dhcpagent: info: configure_v4_timers: e1000g0 begins rebinding at Fri Mar 21 18:33:05 2014
    /sbin/dhcpagent: debug: set_smach_state: changing from INIT_REBOOT to PRE_BOUND on e1000g0
    /sbin/dhcpagent: info: added default router 192.168.0.1 on e1000g0
    /sbin/dhcpagent: debug: set_smach_state: changing from PRE_BOUND to BOUND on e1000g0
    /sbin/dhcpagent: debug: configure_bound: bound e1000g0
    /sbin/dhcpagent: debug: ipc_action_finish: finished start (command 4) on e1000g0: 0

    During the Solaris installation process, you told it what the hostname was going to be and that you wanted that environment to exist with a dynamic IP address instead of a specific address that you desired.
    When Solaris boots it broadcasts that hostname and waits for a DHCP server to be quasi-intelligent enough to award an IP address based upon a pre-configured list inside that DHCP server.   Hostname ABC would always get IP address 123 on subnet rst, hostname DEF would always get IP address 456 on subnet xyz, and so on and so on.
    That's the fundamental process for proper (and thus secure) DHCP.
    All your other environments (Windows, Debian, Ubuntu) are what might be thought of as "hacked for convenience" to get around that sort of network configuration.  They take the lazy way to exist.  That partial networking setup is good enough for a home network but would be miserably insecure in a corporate environment.  Those choices are operating environments that are nice for end-user desktops but aren't Enterprise Class.
    My suggestion?
    Review the IP address range in your Netgear router's setup.
    It is likely something like 192.169.0.1 through 192.168.0.50 and can be customized.
    You probably don't have 50 devices on your network and probably will never have 50 simultaneous devices on your network.
    ... just do a reconfigure reboot and set your Solaris to use a static IP of 192.068.0.45
    Then reboot and I predict your issue that prompted this forum thread will be gone.
    That's how I've done it at home for many years, even when installing Solaris to bare metal (no virtualization).

  • DHCP service not working

    Hello,
    I have airport express base station and I have set it up to give DHCP IP addresses to wireless clients as I don't have any DHCP server in the ethernet LAN.
    But the Airport doesn't give out IP addresses at all.
    In the Internet tab, I have selected connect using Ethernet and Connection sharing: "Distribute range of IP addresses".
    In the TCP/IP tab, I have given a valid manual IP to the base station.
    In the DHCP tab, I have specified the DHCP start/end addresses.
    Now when the wireless clients try to connect they only get limited connectivity and if I give a manual IP to the client he/she gets the internet connectivity.
    Can anybody guide me what could be causing this? I have airport utility 5.5.3.

    "Distribute a range of IP addresses" is a rarely used setting, which would only be used if your service provider has furnished you with a specific bank of IP addresses to use.
    Try using the "Share a public IP address" setting for Connection Sharing and the AirPort Express will hand out IP addresses automatically to connected clients.

  • Clients not getting DHCP in VRF

    Good morning -
    We have devices in the global routing table (not in a VRF) getting DHCP addresses without issue. The SVI is configured as such:
    interface Vlan2301
    description BLUE
    ip address 172.19.68.1 255.255.255.0
    ip helper-address 10.4.16.222
    interface Vlan2512
    description RED
    vrf forwarding RED
    ip address 10.217.5.1 255.255.255.0
    ip helper-address 10.4.16.222
    Clients in BLUE are getting DHCP but clients in RED are not. If I statically assign an address I have connectivity and can reach the DHCP server (which is also DNS server; with a static IP in VLAN 2512 I can do name resolutions for example).
    I am at a bit of a loss. Is there anything special I need to do for VRF IP HELPER-ADDRESS configuration? A capture on my firewall interface shows the DHCP server is trying to reply - it is like the helper-address is not forwarding the dhcp reply (or is not getting it)
    11:11:52.915180 IP (tos 0x0, ttl 254, id 17478, offset 0, flags [none], proto UDP (17), length 337)
        10.217.5.1.67 > 10.4.16.222.67: BOOTP/DHCP, Request from xx, length 309, hops 1, xid 0xb53a220c, Flags [none]
              Gateway-IP 10.217.5.1
              Client-Ethernet-Address xx [|bootp]
    11:11:52.918761 IP (tos 0x0, ttl 124, id 28096, offset 0, flags [none], proto UDP (17), length 344)
        10.4.16.222.67 > 10.217.5.1.67: BOOTP/DHCP, Reply, length 316, xid 0xb53a220c, Flags [none]
              Your-IP 10.217.5.12
              Server-IP 10.4.16.222
              Gateway-IP 10.217.5.1
              Client-Ethernet-Address xx [|bootp]
    Any ideas?

    Good morning -
    I have a pair of 6513 in a VS40 (VSS quad sup) connected via L3 MEC to a VSS pair of 4500X. Active to Active and Standby to Standby connected in a L3 MEC port-channel that is also a vnet trunk:
    (Core)
    interface Port-channel5
    description Distribution Uplink
    no switchport
    vnet trunk
    ip dhcp snooping limit rate 100
    ip address 172.20.68.1 255.255.255.252
    ip ospf message-digest-key 1 md5 XXX
    spanning-tree guard root
    (4500 Distribution)
    interface Port-channel1
    description Core Uplink
    vnet trunk
    ip arp inspection trust
    ip address 172.20.68.2 255.255.255.252
    ip ospf message-digest-key 1 md5 XXX
    The interfaces are all using LACP mode Active inside the channels
    On the 4500 we have a global routing table and a vrf. Both have helper addresses pointing to the DHCP server which is extranet service behind the 6513 Core.
    interface Vlan2301
    description Global Routing Table
    ip address 172.19.68.1 255.255.255.0
    ip helper-address 10.4.16.222
    interface Vlan2512
    description VRF
    vrf forwarding RED
    ip address 10.217.5.1 255.255.255.0
    ip helper-address 10.4.16.222
    DHCP for the Global Routing Table subnet works. DHCP for the VRF does not.
    What is interesting is if we shut down the link that is connected to the standby 4500 (Te2/1/1) DHCP starts to work for the VRF.
    Using <debug ip dhcp server packet detail> at the 4500 here is what I am seeing.
    When both links are up and DHCP is failing for the VRF:
    Mar 10 20:02:02.419: DHCPD: BOOTREQUEST from 0100.1a6b.3a56.13 forwarded to 10.4.16.222.
    Mar 10 20:02:10.473: DHCPD: Reload workspace interface Vlan2512 tableid 3.
    Mar 10 20:02:10.473: DHCPD: tableid for 10.217.5.1 on Vlan2512 is 3
    Mar 10 20:02:10.474: DHCPD: client's VPN is RED.
    Mar 10 20:02:10.474: DHCPD: using received relay info.
    When I shut the Te2/1/1 link down in the L3 MEC at the 4500 DHCP starts to work for the VRF RED:
    Mar 10 20:04:41.354: DHCPD: BOOTREQUEST from 0100.1a6b.3a56.13 forwarded to 10.4.16.222.
    Mar 10 20:04:41.369: DHCPD: Reload workspace interface Port-channel1.2002 tableid 3.
    Mar 10 20:04:41.369: DHCPD: tableid for 172.20.68.2 on Port-channel1.2002 is 3
    Mar 10 20:04:41.369: DHCPD: client's VPN is .
    Mar 10 20:04:41.369: DHCPD: forwarding BOOTREPLY to client 001a.6b3a.5613.
    Mar 10 20:04:41.369: DHCPD: no option 125
    Mar 10 20:04:41.369: DHCPD: broadcasting BOOTREPLY to client 001a.6b3a.5613.
    Mar 10 20:04:41.369: DHCPD: no option 125
    Mar 10 20:04:44.808: DHCPD: Reload workspace interface Vlan2512 tableid 3.
    Mar 10 20:04:44.808: DHCPD: tableid for 10.217.5.1 on Vlan2512 is 3
    Mar 10 20:04:44.808: DHCPD: client's VPN is RED.
    It is like there is a bug that is treating the L3 MEC as a L2 MEC when both links are present; or the VNET trunk is not being processed correctly.
    Has anyone else used a L3 MEC with a VRF and a DHCP helper with success? Is this a bug?
    03.05.01.E is the code we are running on the 4500X-32(SPF+)
    This is also with TAC but I thought I would share with the community in case anyone else has a similar environment or if Cisco experts want to comment.

  • 4500X L3 MEC + VRF + DHCP issue

    Good morning -
    I have a pair of 6513 in a VS40 (VSS quad sup) connected via L3 MEC to a VSS pair of 4500X. Active to Active and Standby to Standby connected in a L3 MEC port-channel that is also a vnet trunk:
    (Core)
    interface Port-channel5
    description Distribution Uplink
    no switchport
    vnet trunk
    ip dhcp snooping limit rate 100
    ip address 172.20.68.1 255.255.255.252
    ip ospf message-digest-key 1 md5 XXX
    spanning-tree guard root
    (4500 Distribution)
    interface Port-channel1
    description Core Uplink
    vnet trunk
    ip arp inspection trust
    ip address 172.20.68.2 255.255.255.252
    ip ospf message-digest-key 1 md5 XXX
    The interfaces are all using LACP mode Active inside the channels
    On the 4500 we have a global routing table and a vrf. Both have helper addresses pointing to the DHCP server which is extranet service behind the 6513 Core.
    interface Vlan2301
    description Global Routing Table
    ip address 172.19.68.1 255.255.255.0
    ip helper-address 10.4.16.222
    interface Vlan2512
    description VRF
    vrf forwarding RED
    ip address 10.217.5.1 255.255.255.0
    ip helper-address 10.4.16.222
    DHCP for the Global Routing Table subnet works. DHCP for the VRF does not.
    What is interesting is if we shut down the link that is connected to the standby 4500 (Te2/1/1) DHCP starts to work for the VRF.
    Using <debug ip dhcp server packet detail> at the 4500 here is what I am seeing.
    When both links are up and DHCP is failing for the VRF:
    Mar 10 20:02:02.419: DHCPD: BOOTREQUEST from 0100.1a6b.3a56.13 forwarded to 10.4.16.222.
    Mar 10 20:02:10.473: DHCPD: Reload workspace interface Vlan2512 tableid 3.
    Mar 10 20:02:10.473: DHCPD: tableid for 10.217.5.1 on Vlan2512 is 3
    Mar 10 20:02:10.474: DHCPD: client's VPN is RED.
    Mar 10 20:02:10.474: DHCPD: using received relay info.
    When I shut the Te2/1/1 link down in the L3 MEC at the 4500 DHCP starts to work for the VRF RED:
    Mar 10 20:04:41.354: DHCPD: BOOTREQUEST from 0100.1a6b.3a56.13 forwarded to 10.4.16.222.
    Mar 10 20:04:41.369: DHCPD: Reload workspace interface Port-channel1.2002 tableid 3.
    Mar 10 20:04:41.369: DHCPD: tableid for 172.20.68.2 on Port-channel1.2002 is 3
    Mar 10 20:04:41.369: DHCPD: client's VPN is .
    Mar 10 20:04:41.369: DHCPD: forwarding BOOTREPLY to client 001a.6b3a.5613.
    Mar 10 20:04:41.369: DHCPD: no option 125
    Mar 10 20:04:41.369: DHCPD: broadcasting BOOTREPLY to client 001a.6b3a.5613.
    Mar 10 20:04:41.369: DHCPD: no option 125
    Mar 10 20:04:44.808: DHCPD: Reload workspace interface Vlan2512 tableid 3.
    Mar 10 20:04:44.808: DHCPD: tableid for 10.217.5.1 on Vlan2512 is 3
    Mar 10 20:04:44.808: DHCPD: client's VPN is RED.
    It is like there is a bug that is treating the L3 MEC as a L2 MEC when both links are present; or the VNET trunk is not being processed correctly.
    Has anyone else used a L3 MEC with a VRF and a DHCP helper with success? Is this a bug?
    03.05.01.E is the code we are running on the 4500X-32(SPF+)
    This is also with TAC but I thought I would share with the community in case anyone else has a similar environment or if Cisco experts want to comment.

    Hi,
    I have tested the dhcp server and vrf on Cisco 3640 and it is working without VRF under the ip dhcp pool. Please ensure that you have configured routing for the dhcp-relay agent(VLAN facing dhcp client on 3750 in your case).

  • DHCP on OES11 Cluster

    Hello,
    I have some problems to get DHCP Service running in a Cluster Evironment (OES11 SP1, NSS Volume). The Ressource is up and running, but the DHCP Service wont load.
    LDAPS session successfully enabled to 10.0.181.36:636
    Error: Cannot find LDAP entry matching (&(objectClass=dhcpServer)(cn=DHCP_CLUSTER-DNSDHCP-SERVER))
    Configuration file errors encountered -- exiting
    The standard command rcnovell-dhcp start did work. So it looks like the rights or seomthing else is missing on the cluster volume /media/nssDHCP...
    Maybe I am misunderstanding the doc as well. It states in the DHCP Linux Guide:
    8.3.3. hot wo use a different user - it states that it would use the dhcpd user , but no such user was created. Do I need to create it manually?
    Thanks for your help!
    Regards Jrgen

    Hi,
    If I recall correctly from my setup, I had to create a user and LUM enable it, and match the UID to the local account.
    See here: http://www.novell.com/documentation/...a/bbe81cc.html
    Let us know how it goes.
    Cheers,

  • DHCP WDS Error

    Hi. Im having a problem where I get the error 'An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network segment'when booting from a standard WDS boot.wim image taken
    from a Windows 7 DVD.
    I am using Server 2008 R2 and am adding the drivers to the boot using WDS, but also have the problem if the drivers are injected beforehand using DISM.
    When the error occurs I can shift + F10 and IPCONFIG and see it HAS picked up an internal IP from DHCP. Seems maybe it is timing out before it gets the IP?
    As per some fixes I have read I enabled RSTP on my switches but that didnt help.
    I have included the end of setupact.log to see if any of you have any ideas.Seems to be failing but as I say, the network IS initialized as I can see the internal IP assigned by DHCP when running IPCONFIG.
    I dont suppose theres any way of increasing the timeout?
    Thanks.
    2011-04-11 17:26:31, Info       [0x0b0022] WDS    StartNetworking: Trying to start networking.
    2011-04-11 17:26:31, Info                  WDS    Network service dhcp not running or could not be queried: 264d00 1 1
    2011-04-11 17:26:31, Info                  WDS    Network service lmhosts not running or could not be queried: 264e18 1 1
    2011-04-11 17:26:31, Info                  WDS    Network service lanmanworkstation not running or could not be queried: 264d00 1 1
    2011-04-11 17:26:31, Info                  WDS    Network service bfe not running or could not be queried: 264e18 1 1
    2011-04-11 17:26:31, Info                  WDS    Network service ikeext not running or could not be queried: 264d00 1 1
    2011-04-11 17:26:31, Info                  WDS    Network service mpssvc not running or could not be queried: 264e18 1 1
    2011-04-11 17:27:24, Info                  WDS    Installing device pci\ven_14e4&dev_1691&subsys_04aa1028 X:\WINDOWS\INF\oem37.inf succeeded
    2011-04-11 17:27:25, Info                  WDS    No computer name specified, generating a random name.
    2011-04-11 17:27:25, Info                  WDS    Renaming computer to MININT-VN2P876.
    2011-04-11 17:27:25, Info                  WDS    Acquired profiling mutex
    2011-04-11 17:27:25, Info                  WDS    Service winmgmt disable: 0x00000000
    2011-04-11 17:27:25, Info                  WDS    Service winmgmt stop: 0x00000000
    2011-04-11 17:27:25, Info                  WDS    Service winmgmt enable: 0x00000000
    2011-04-11 17:27:25, Info                  WDS    Released profiling mutex
    2011-04-11 17:27:25, Info                  WDS    Acquired profiling mutex
    2011-04-11 17:27:25, Info                  WDS    Install MS_MSCLIENT: 0x0004a020
    2011-04-11 17:27:25, Info                  WDS    Install MS_NETBIOS: 0x0004a020
    2011-04-11 17:27:25, Info                  WDS    Install MS_SMB: 0x0004a020
    2011-04-11 17:27:25, Info                  WDS    Install MS_TCPIP6: 0x0004a020
    2011-04-11 17:27:26, Info                  WDS    Install MS_TCPIP: 0x0004a020
    2011-04-11 17:27:26, Info                  WDS    Service dhcp start: 0x00000000
    2011-04-11 17:27:26, Info                  WDS    Service lmhosts start: 0x00000000
    2011-04-11 17:27:26, Info                  WDS    Service ikeext start: 0x00000000
    2011-04-11 17:27:26, Info                  WDS    Service mpssvc start: 0x00000000
    2011-04-11 17:27:26, Info                  WDS    Released profiling mutex
    2011-04-11 17:27:26, Info                  WDS    Spent 967ms installing network components
    2011-04-11 17:27:28, Info                  WDS    Spent 2247ms installing network drivers
    2011-04-11 17:27:38, Info                  WDS    QueryAdapterStatus: no operational adapters found.
    2011-04-11 17:27:38, Info                  WDS    Spent 10140ms confirming network initialization; status 0x80004005
    2011-04-11 17:27:38, Info                  WDS    WaitForNetworkToInitialize failed; ignoring error
    2011-04-11 17:27:38, Info                  WDS    GetNetworkingInfo: WpeNetworkStatus returned [0x0]. Flags set:   
    2011-04-11 17:27:38, Error      [0x0b003f] WDS    StartNetworking: Failed to start networking. Error code [0x800704C6].[gle=0x000000cb]
    2011-04-11 17:27:38, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server
    on this network segment.]

    Thanks for the reply. I have came across the post about removing setup.exe etc but thats a nasty hack and Id rather get the thing working properly.
    For my own testing to prove I had added the drivers correctly I booted off a base boot.wim with no drivers injected. There was no IP when running IPCONFIG. End of setupact.log shows
    2011-04-13 09:09:20, Info WDS Spent 936ms installing network components
    2011-04-13 09:09:23, Info WDS Spent 2355ms installing network drivers
    2011-04-13 09:09:23, Error [0x0b003e] WDS QueryAdapterStatus: no adapters found.[gle=0x000000cb]
    2011-04-13 09:09:23, Info WDS Spent 0ms confirming network initialization; status 0x80004005
    2011-04-13 09:09:23, Info WDS WaitForNetworkToInitialize failed; ignoring error
    2011-04-13 09:09:23, Info WDS GetNetworkingInfo: WpeNetworkStatus returned [0x0]. Flags set:
    2011-04-13 09:09:23, Error [0x0b003f] WDS StartNetworking: Failed to start networking. Error code [0x800704C6].[gle=0x000000cb]
    2011-04-13 09:09:23, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: An error occurred while starting networking: a matching network card driver was not found in this image. Please have your Administrator add the network driver for this machine to the Windows PE image on the Windows Deployment Services server.]
    Next, I injected the latest Broadcom drivers into another base boot.wim file. IPCONFIG shows an IP address. End of setupact.log shows
    2011-04-13 09:17:38, Info WDS Spent 936ms installing network components
    2011-04-13 09:17:40, Info WDS Spent 2309ms installing network drivers
    2011-04-13 09:17:50, Info WDS QueryAdapterStatus: no operational adapters found.
    2011-04-13 09:17:50, Info WDS Spent 10140ms confirming network initialization; status 0x80004005
    2011-04-13 09:17:50, Info WDS WaitForNetworkToInitialize failed; ignoring error
    2011-04-13 09:17:50, Info WDS GetNetworkingInfo: WpeNetworkStatus returned [0x0]. Flags set:
    2011-04-13 09:17:50, Error [0x0b003f] WDS StartNetworking: Failed to start networking. Error code [0x800704C6].[gle=0x000000cb]
    2011-04-13 09:17:50, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network segment.]
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : minint-2eljtfg
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : correct.co.uk
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . : correct.co.uk
    Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
    Physical Address. . . . . . . . . : 78-2B-CB-93-11-F8
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::a098:117a:a1fd:a4b9%2(Preferred)
    IPv4 Address. . . . . . . . . . . : 10.0.0.78(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Wednesday, April 13, 2011 9:17:57 AM
    Lease Expires . . . . . . . . . . : Thursday, April 21, 2011 9:17:57 AM
    Default Gateway . . . . . . . . . : 10.0.0.66
    DHCP Server . . . . . . . . . . . : 10.0.0.21
    DHCPv6 IAID . . . . . . . . . . . : 41429963
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-37-93-19-78-2B-CB-93-99-F8
    DNS Servers . . . . . . . . . . . : 10.0.0.21
    10.0.0.6
    NetBIOS over Tcpip. . . . . . . . : Enabled
    See the difference? 'no adapters found' vs 'no operational adapters found'.
    However this time I did notice that when I typed IPCONFIG straight away after the error message poped up it only showed an IPV6 address. Then when I tried 1 second later it had picked up the DHCP address.
    Seems that the network card takes some time to initialize and the deployment setup is too impatient and falls over?

  • DHCP not providing IP's to stations!

    Hi, im trying to figure this out for days but cant make it work!
    i've set up a MacOSX Server 10.5, its working fine for print and file sharing, i wanted it alos to control the IP address for all the computers connected to same network so in near future i start using Open Directory, and i dont want to provide manual IP's.
    in OSX Server Admin Application, i set the DHCP providing it with starting ip's, end ip's, mask, router, dns, and in System Preferences/Network/Ethernet i also set same IP for the server, same mask, router, dns as set in DHCP, start the DHCP i see nothing changes in computer client, they keep generating the Bonjour IP's, or if i put a normal router in the network they immidiatly get the IP's from the router, so why from the Router and not from OSX Server?
    in the Admin page of DHCP seetings, in Log, it says that machine (with MAC addresses) trying to obtain DHCP address.. if it knows theres a computer trying to get its IP from the server, why its not providing it??
    and if i have a router and a server in same network, how do i make computers get the ip's from the server and not from router?
    is there a step by step manual out there to "correctly" configure DHCP? and then Open Directory?
    i've manage to run DNS correctly, cuz i tested pinging to both ip and server name and both gave correct results...
    Thanks

    You may have already done this, but it isn't clear from the post, so it's worth checking...
    i also set same IP for the server, same mask, router, dns as set in DHCP
    I assume that you mean you set a different IP address, right?
    You cannot set your server to have a static IP address that's within the DHCP range.
    For example, if you're using 192.168.1.x/255.255.255.0 as your network/subnet mask then you might have your router at 192.168.1.1 and your server at .2. You could then define the DHCP range as something like 192.168.1.101 - 192.168.1.200.
    That would give you 100 dynamic IP addresses in the subnet that do not conflict with manually-configured devices such as the router, server, etc.
    if i have a router and a server in same network, how do i make computers get the ip's from the server and not from router?
    You turn off the DHCP server in the router. While it is possible to have multiple DHCP servers in a subnet, it is vastly more complicated and not generally recommended.

  • DHCP failover

    I have two oes11 servers setup doing dns & dhcp. Services are set up
    w/ identical zones, subnets, pools, etc. DNS is fine, and dhcp starts
    & works properly on each server.
    When I setup the failover option, the server that's set to be primary
    keeps dhcp running while the secondary one goes to unused.
    During this time, no machines will receive a dhcp address.
    In watching /var/log/messages, I see this in the secondary failover
    server:
    Failover CONNECT from ccg-dns2: unknown failover relationship name.
    This shows up on the primary failover server:
    failover peer ccg-dns2: I move from recover to startup
    failover peer ccg-dns2: I move from startup to recover
    Primary server is ccg-dns1 with a failover peer of ccg-dns2, secondary
    is ccg-dns2 with a failover peer of ccg-dns1.
    If I take the failover peer out of the services, dhcp returns to
    working properly.
    Any ideas? Suggestions?
    Stevo

    Originally Posted by hpfeil
    Make sure the failover object is the same. I got the same error on my test environment. So, I think it should be like this:
    Service1
    - failoverxyz
    Service2
    -failoverxyz
    -Hans
    Good tip Hans, thanks,
    As I'm actually also looking into setting this up for some larger existing setups.... wondering if it would not be quickest to add the failover object to the existing service and configure the existing pools to use that failover object.
    Then export the existing DHCP service and reimport it into a new service and point it to be serviced by a second DHCP server that was setup.
    Also, the port that should be used for the failover primary port/listener. The TID mentions there is no standardized port... Though different sources mention port 647 has been defined for this purpose.
    Might be a good thing to put that in the TID as well as documentation to use as suggested port. To much options are not always a good thing :)
    So I'm curious which port you guys used and for what reason...?
    Cheers,
    Willem

  • NAT & DHCP on C1760 with switch/InterVLAN routing

    Hello,
    trying to achieve following (see also Connection diagram.txt attachment):
    There is satellite link, which goes to receiver.
    Receiver is connected to Cisco 1760 router via switch. From router on serial interface there is one way outgoing satellite link.
    On switch between receiver and router resides customers with public and private IP addresses, which can access Internet. Here I do not have problems, using DHCP for assigning private and NAT on stick, everything just works.
    Problem is too achieve NAT working on switch (WIC-4ESW), which is inserted into Cisco1760.
    Most important that other DHCP pool should be assigned here, we need to use other NAT pool (to split public IP assigned).
    DHCP started to work, NAT is working only one way - from private to public IP address.
    When reply comes to public IP which should be translated again, it does not.
    I see that packets come on VLAN40 interface (see also configuration file of router), but do not see translation happening.
    Right now in configuration NAT for VLAN40 is done using NAT on stick.
    I also have tried plain NAT (using serial0/0 as NAT outside, no policy route on VLAN40) - result is same.
    May be tried to achieve is practically not possible?
    Thanks!

    Hello,
    looking at the configuration of your router, I do not see access list 110, which should be matched in your route map:
    access-list 10 permit 192.168.200.0 0.0.0.255
    access-list 11 permit 192.168.100.0 0.0.0.255
    access-list 100 permit ip any 193.100.100.0 0.0.0.3
    access-list 100 permit ip 192.168.200.0 0.0.0.255 any
    route-map NAT_Internet permit 10
    match ip address 110
    set ip next-hop 192.168.1.2
    Can you check if this is a typo ?
    Regards,
    GP

  • Disable dhcp proxy for PPP VPN (outside DHCP server + NPS)

    Hi,
    Our VPN setup is to authenticate / authorize via RADIUS to a Microsoft NPS server / Active Directory and use our internal DHCP server to receive its information. We are running a Cisco 2811, with firmware release k9 15.1- 4.M5.
    However, we have been having some issues with our setup for a dial-in VPN. We managed to get almost everything working.
    The user can dial in and authenticate and it even builds the proper PPTP tunnel. However, the client machine when it sends out a DHCP requests seems to get forced to proxy through the Cisco router. Thus what the DHCP server sees is a encoded MAC address from the cisco all the time and sees the client as being the cisco router not the VPN client/user. This is rather frustrating, as in Active directory DNS tables it will show up as the router having x number of different IP addresses and the end client doesn't show up at all.
    I have tried utilizing a bunch of different configuration options to test, all with the same outcome.
    Utilizing "ip helper-address <dhcp server>", didn't work to forward correct. Thent trying to turn of all DHCP services, with the global command of "no service dhcp", didn't change any result. Neither did setting a global command of "ip dhcp-server <dhcp server>".
    What i am trying to acchive is that the cisco does NOT mess with the dhcp request and just allows it to pass through.
    Anyone have any idea?
    Here are the parts of the current configuration in respect to this:
    no service dhcp
    aaa new-model
    aaa authentication login CONSOLE local
    aaa authentication ppp default group radius local
    aaa authorization network default if-authenticated
    aaa session-id common
    no ip domain lookup
    ip domain name <domain>
    ip name-server xxx.xxx.xxx.xxx
    ip dhcp-server xxx.xxx.xxx.xxx
    vpdn enable
    vpdn-group 1
    ! Default PPTP VPDN group
    accept-dialin
      protocol pptp
      virtual-template 1
    interface Virtual-Template1
    ip unnumbered FastEthernet0/1    <-Internal Interface
    no ip proxy-arp
    ip nat inside
    no ip virtual-reassembly in
    peer default ip address dhcp
    ppp encrypt mppe auto required
    ppp authentication pap chap ms-chap ms-chap-v2
    radius-server host xxx.xxx.xxx.xxx
    radius-server key <private key>
    And the problem that i am seeing when running a debug on dhcp:
    *Jan 15 09:01:46.558: DHCP: proxy allocate request
    *Jan 15 09:01:46.558: DHCP: new entry. add to queue, interface Virtual-Access5
    *Jan 15 09:01:46.558: DHCP: Client socket is opened
    *Jan 15 09:01:46.558: DHCP: SDiscover attempt # 1 for entry:
    *Jan 15 09:01:46.558: DHCP: SDiscover: sending 284 byte length DHCP packet
    *Jan 15 09:01:46.558: DHCP: SDiscover 284 bytes
    *Jan 15 09:01:46.562: DHCP: XID MATCH in dhcpc_for_us()
    *Jan 15 09:01:46.990: DHCP: Received a BOOTREP pkt
    *Jan 15 09:01:46.990: DHCP: offer received from <DHCP SERVER>
    *Jan 15 09:01:46.990: DHCP: SRequest attempt # 1 for entry:
    *Jan 15 09:01:46.990: DHCP: SRequest- Server ID option: <DHCP SERVER>
    *Jan 15 09:01:46.990: DHCP: SRequest- Requested IP addr option: 192.168.10.100
    *Jan 15 09:01:46.990: DHCP: SRequest: 296 bytes
    *Jan 15 09:01:46.990: DHCP: SRequest: 296 bytes
    *Jan 15 09:01:46.994: DHCP: XID MATCH in dhcpc_for_us()
    *Jan 15 09:01:46.994: DHCP: Received a BOOTREP pkt
    *Jan 15 09:01:46.994: DHCP: Sending notification of ASSIGNMENT:
    *Jan 15 09:01:46.994:   Address 0.0.0.0 mask 0.0.0.0
    *Jan 15 09:01:46.994: DHCP Proxy Client Pooling: ***Allocated IP address: 192.168.10.100
    *Jan 15 09:01:46.994: DHCP: look up prim DNS for Vi5 from lease good ret: <DNS server 1>
    *Jan 15 09:01:46.998: DHCP: look up prim NBNS for Vi5 from lease any ret: fail
    *Jan 15 09:01:46.998: DHCP: look up sec DNS for Vi5 from lease good ret: <DHCP Server>
    *Jan 15 09:01:46.998: DHCP: look up sec NBNS for Vi5 from lease any ret: fail
    *Jan 15 09:01:47.018: DHCP: look up prim DNS for Vi5 from lease good ret: <DNS server 1>
    *Jan 15 09:01:47.018: DHCP: look up sec DNS for Vi5 from lease good ret: <DHCP Server>
    *Jan 15 09:01:47.038: DHCP: look up prim DNS for Vi5 from lease good ret: <DNS server 1>
    *Jan 15 09:01:47.038: DHCP: look up sec DNS for Vi5 from lease good ret: <DHCP Server>
    *Jan 15 09:01:56.826: DHCP: Interface Virtual-Access5 going down. Releasing: 192.168.10.100
    *Jan 15 09:01:56.826: DHCP: start holddown for 192.168.10.100
    *Jan 15 09:01:56.826: DHCP: Holddown and T1 remain 1792 sec
    As one can see even with the configuration to turn of any proxy or dhcp, the cisco router still try's to interject and proxy the request, aka:
    DHCP: proxy allocate request
    If anyone has any idea, please let me know
    Thanks
    S.

    Hello Stephen.
    How is this behaviour in 7.5? It's weird because in the individual interfaces you might change the value, but it doesn't get accepted. So it still seems that it's a global setting... but then: why showing this item to be changed on each interface?
    Kind regards,
    Flavio.

  • Ipw2200 / dhcp

    Hello Arch-Community.
    I today tried out Arch Linux, and wow, i have to say i was quite impressed. Easy to install, easy to use - till now. Well, it still is.
    It is the first distribution where i got the ipw driver working "out of the box". Thumbs up for this ...
    Anyway, there is one problem left:
    If i receive the IP-Address of my WLAN with DHCP, starting the network and the interface during bootup, i have the following problem:
    - The Network goes up (i'm using AcerHK to activate the sw-radio switch).
    - I get an IP-Address
    - I can ping, i can surf
    - Just for some secs / about a minute. After this, my wireless network disappears of "ifconfig", well, as if it never received an Address.wlan_eth1=lly, the interface has already been working.
    If i boot up normally, activating the drivers (acerhk, ipw), and getting the IP manually with DHCP, it works very fine.
    What could this be? I'm using 0.7 (current).
    Following additional information:
    - AcerHK as sw-switch
    - ipw2200 (Intel Centrino 2200BG)
    - arch 0.7 (current)
    the /etc/conf.d/wireless
    wlan_eth1="eth1 mode managed essid LocalGNet"
    WLAN_INTERFACES=(eth1)
    I added the following information to /etc/rc.conf
    eth1="dhcp"
    INTERFACES=(lo eth1)
    Of course, i made a script loading AcerHK on boot
    #!/bin/bash
    . /etc/rc.conf
    . /etc/rc.d/functions
    case "$1" in
    start)
    stat_busy "Starting AcerHK driver"
    if [ ! -f /proc/driver/acerhk/wirelessled ]; then
    modprobe acerhk
    else
    echo "AcerHK driver seems to be already running"
    fi
    if [ -f /proc/driver/acerhk/wirelessled ]; then
    echo 1 > /proc/driver/acerhk/wirelessled
    stat_done
    else
    stat_fail
    fi
    stop)
    stat_busy "Stopping AcerHK driver"
    if [ -f /proc/driver/acerhk/wirelessled ]; then
    echo 0 > /proc/driver/acerhk/wirelessled
    rmmod acerhk
    stat_done
    else
    echo "AcerHK driver seems not to be running"
    stat_fail
    fi
    restart)
    $0 stop
    sleep 1
    $0 start
    echo "usage: $0 {start|stop|restart}"
    esac
    exit 0
    Any idea what could cause this? Any suggestions?
    STiAT

    Okay, i gave it a shot right now, since i arrived at home.
    Compiled 0.19, put the new firmware in the right place.
    Still the same.
    I think there's nothing wrong with it at all...
    The behaviour is like when he wouldn't receive the IP via DHCP, it also drops the interface back to inactive. As if there is no status returend by the dhcpcd at startup time to ifconfig... and so ifconfig drops the interface within 30 secs (dhcp timeout?). i dont know anything of the internals of Arch (yet), since i'm very new to the distribution.
    STiAT

Maybe you are looking for

  • Run Windows from an external drive......

    I want to boot Windows from an external drive. Why would Apple not allow this to be done. It makes no sence to me at all. You would still have to run Windows from the intel-Mac. To make you waste good MacOS space on the internal drive is a shame. I k

  • Replace function - special characters

    Hi All,        If my column is encountering special characters I would like to replace with blank. Special characters may vary from record to record. Sometimes it is @ sometimes $,!,,$,^,<,&,<,>,?,",{,},+,_,),(. Do we have any function same like repl

  • Reciever's voice

    in my handset nokia e51 the voice frome where we hear the the voice of the caller is coming so low and the volume label is already full so please suggest me what to do? i want to know one more thing that can i change the fonts of my mobile becze i ha

  • Photoshop Elements for Mac OSX 10.5.6 Version?

    I'm confused. Is there an Elements for Mac in Version 7. I called the sales line and they told me that for a Mac I would choose Version 6 for Mac??? Is Version 7 for Windows equal to Version 6 for Mac? Thanks!

  • Satellite C855-1LG - where to find the appropriate keyboad driver?

    Hello I've very recently acquired a Satellite C855-1LG. I used it yesterday for the first time and i realised that the digital part of the keyboard (on the right) is not working even when the "verr. num." key is on. I tried to look for drivers since