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?

Similar Messages

  • Getting WDS Error

    Hi, I've been having a problem with my wireless network the past couple of weeks. I have an AEBSn set up as a base station and an AEBSg and Airport Express set up as remote units in different parts of the house. This configuration worked great until about 2 weeks ago. Someone uplugged the Airport Express and after it was plugged back in I have been getting an amber flashing light indicating a WDS error on the AEBSn unit.
    I look into Airport Utility and it sees all three units with the remote units coded green. At times, it seems to resolve itself and the status light goes green but after a few minutes it begins flashing amber again.
    I'm getting a good signal throughout the house, it just is annoying to see the amber flashing light.
    Thanks for any suggestions or hints.
    Bob

    There is no reason to suspect a "settings" problem here. My guess is that this error is being caused by an occasional drop in the wireless communication between the main and remote base stations.
    For a start, you might try pulling power to all base stations, then plug the main base station into power and waiting for it to reboot, followed by both remote base stations. That might force the entire network to work on a different channel with a better connection than current.

  • AEBS/relay/remote flashes WDS Errors

    I am trying to set up a remote connection from the office to the gym using 3 Airport Extreme Base Stations. I currently have all 3 in a room the main connected to the DSL modem, and the remote connected to the main via ethernet.
    The problem is that the main keeps flashing WDS Errors, then goes back to a Normal status. The relay would flash, then the remote. I removed the relay, and the remote seems to keep it Normal status better even as the main changes to WDS Error - it shows an error it is just for a blink. WDS Error is "This Apple wireless device is set up as part of a WDS network but no other Apple wireless devices were found." When ever the main changes status it drops it wireless clients.
    If I use the main in "Create wireless network" it seems to work fine.
    Anyone know why this might be happening? Can I just click ignore it since the remote is Normal most of the time?
    I have set up the network following Apples Designing AirPort networks guide available online http://manuals.info.apple.com/en/DesigningAirPort_Networks10.5-Windows.pdf . I have entered the airport id in the proper place and set the WDS Mode to the proper mode for each device.
    I have tried checking and unchecking the use interference robustness (makes no difference). I have checked and unchecked "Allow this network to be extended" and found there to be no difference. All three are set at Participate in a WDS network.
    I have tried every channel and there is no difference.
    Should the Wireless Mode on the relay/remote be Extend a wireless network? Should allow this network to be extended be checked or unchecked?
    Any more ideas will be appreciated. Time to enjoy the 4th!

    I have set on AEBS in the hall about 100 feet from the first. I am going though 2 steel framed drywalls and one block&brick wall. Still have about 1650kbps using iNetwork test. The problem has been getting into the gym. I can get from the hall through a glass window, courtyard, steel covered wooded door and into the kitchen. But the wall between the kitchen and gym is double thick with steel rods. I changed the location of the remote from the kitchen to the storage room, which houses the water heaters. The signal goes through the courtyard and a brick&block wall. The reading was about 400kbps and I am able to get through the wooden doors into the gym area with one bar showing on my Macbook.
    I guess I will have to try something different.

  • DHCP cofiguration error while installing SOA suit 10.1.3

    Hi can any one suggest how to resolve DHCP cofiguration error while installing SOA suit 10.1.3. I have win7 but getting this error . Please sort out................

    platGroup = WINDOWS
    Query Returned: true
    Calling Query soaNetQueries1.0 isDhcp
    Query Returned: true
    Calling Query soaNetQueries1.0 isLoopback
    Query Returned: false
    A DHCP configuration was detected on this host. The installer also detected that the local hostname and the network hostname differ. Please resolve the networking issues by referring the "Installing on DHCP Computers" section in the installation guide.
    Calling Query generalQueries10.1.0.3.0 getInstallType
    Query Returned: allProducts
    Calling Query generalQueries10.1.0.3.0 getInstallType
    Query Returned: allProducts
    Calling Query generalQueries10.1.0.3.0 getInstallType
    Query Returned: allProducts
    Calling Query generalQueries10.1.0.3.0 getInstallType
    Query Returned: allProducts
    *** Specify Database Connect Information Page***
    Warning:*** Alert: Do you really want to exit? ***
    User Selected: Yes/OK
    User Exit
    This is the error i am getting i have gone through docs also but did not able to resolve it i have window-7 platform can we install on this 10.1.3.........or i have to follow some other method as i am getting this error........

  • DHCP Service errors in Publisher

    We have thousand of the same DHCP Service errors below on the Publisher, but the DHCP service is disbled. Don't know if that is a bug in Window 2000. It is running on OS 2000.2.7sr8. Thanks.
    Event ID: 1008 Source: Perflib
    The Open Procedure for service "DHCPServer" in DLL "C:\WINNT\system32\perfctrs.dll" failed. Performance data for this service will not be available. Status code returned is data DWORD 0.

    Hi Binh,
    Have a look at this thread from January of this year. The excellent answers from Aaron and Steven from Cisco systems address this exact problem.
    http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=IP%20Communications%20and%20Video&topic=IP%20Telephony&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1dda5362/2#selected_message
    Hope this helps!
    Rob
    Please remember to rate helpful posts..........

  • WDS error message

    I am getting a WDS error message on my set up - saying station part of wds network but no other base stations found.
    The network works fine so i could just ignore but i am interseted to understand more and the manual 'designing n network' does not help me
    here is the set up: dsl modem>n base station>connected wirelessly to 3 aiport expresses (printer;itunes/hifi and ax in bedroom) and a g base station
    The error message says set up N base station as a 'bridge' but if i do that the ax's and g base station don seem to connect. The raeson I am using a n base station in this is that i want to use a shared hard drive on the network
    All thoughts gratefully received

    Hi xhoffman,
    This error can occur when you try to install Windows 7 or Windows Server 2008 R2 on a system if the following situation is true on your PC:
    You are installing by using Windows 7 or Windows Server 2008 R2 RTM media.
    Your system has an Intel storage controller that is configured to "RAID" mode in the BIOS. (This is a standard setting for many PC manufacturers).
    The hard drive you are installing to an "Advanced Format" disk.
    Please check your installation media and BIOS drive settings or download the appropriate drivers for your hard disk drive.
    You could also check your setupact.log and setuperr.log for more failure details
    https://technet.microsoft.com/en-us/library/hh825073.aspx?f=255&MSPPError=-2147217396
    For more information or advanced methods
    http://support.microsoft.com/en-us/kb/2466753
    Regards
    D. Wu

  • WDS error?

    anyone else having an issue to get an Airport express to extend their Airport Extreme Network?
    I did have 3 airport expresses located through out the house 1 master. and then 2 others for speakers. I replaced the master one with the new airport extreme. I got them connected and extended ok. until I went to set up the WPA2 passwords. as soon as I set up one of the express's as an WDS extender (with the password) the extreme comes back with WDS error
    but I can get the expresses to connect ok with the passwords as a wireless client
    Any idea's people??" (APPLEGUY)
    http://forums.macrumors.com/showthread.php?t=288640
    This was posted on another forum, but it was written so well and the exact problem/issue I am having....

    Make sure you read this article:
    Changing network security for a WDS network
    The point made in that article relevant to your problem is this one:
    "If you have a WDS network set up to use either no security, or 40 or 128-bit WEP, and you decide to upgrade the network security settings to WPA Personal, you will need to reset all of the base stations on the network, and then set up the WDS network again. "

  • Configure WDS error - The Network path was not found

    I'm trying to configure WDS on Server 2012 R2. The Server is a DC and hosting DHCP and DNS. When running through the wizard or via command line to configure WDS, I get a message saying "The network path was not found". The folder gets created,
    however there is no content in the folder.
    We are also getting the following event "An error occurred while trying to initialize provider from WDSMDMGR from C:\windows\system32\wdsmc.dll
    Any ideas?
    thanks.

    Hi,
    Since WDS is running on the same server with DHCP, did you set WDS not to listen to port 67 and configure DHCP option 60 PXEClient?
    These settings can be done via WDS installation wizard.
    Hope this helps.

  • WDS Error Event ID : 722

    WDS & DHCP configured in same server. I getting error in WDS log file. 
    An error occurred while trying to create the UDP endpoint for WDSTFTP provider on interface 10.146.8.5:69. This can happen if the network interface was disabled or changed, or some other application is already using the port. The provider  will not
    be able to receive requests on this interface. 
     Error Information: 0x2740 
    How to reslove it 
     

    Also, please review
    https://technet.microsoft.com/en-us/library/hh397405.aspx and make sure all steps are taken for running DHCP and WDS on the same server.
    Jeff

  • WDS error message Windows cannot be installed

    Hi I am new on the WDS environment, yesterday I installed the role on a Win 2012 server, added the DHCP config, the boot image and the install image from a windows 7 64 bit ISO and now when I try to push the install into a dell latitude E5530 I get an error
    message right at the end on the Windows 7 install saying that Windows cannot be installed in this hardware.
    What am I doing wrong?

    Hi xhoffman,
    This error can occur when you try to install Windows 7 or Windows Server 2008 R2 on a system if the following situation is true on your PC:
    You are installing by using Windows 7 or Windows Server 2008 R2 RTM media.
    Your system has an Intel storage controller that is configured to "RAID" mode in the BIOS. (This is a standard setting for many PC manufacturers).
    The hard drive you are installing to an "Advanced Format" disk.
    Please check your installation media and BIOS drive settings or download the appropriate drivers for your hard disk drive.
    You could also check your setupact.log and setuperr.log for more failure details
    https://technet.microsoft.com/en-us/library/hh825073.aspx?f=255&MSPPError=-2147217396
    For more information or advanced methods
    http://support.microsoft.com/en-us/kb/2466753
    Regards
    D. Wu

  • WLSE 2.11, snmp and wds errors

    Hello,
    I try to use WLSE to manage our AP1131,1231 with different IOS version.. Some AP are in WDS domain with a WLSM, others in WDS with an AP configured to be wds master, and other are standalone without wds configured.
    I have a lot of AP with error on WLSE, the most recurring ones are "Device was not reachable via SNMP" and "Inconsistent state found for query "interface.radio.basic"".
    WLSE says that some device were not reachable by SNMP but snmp community is configured with a good access-list. Moreover, when I test snmp reachability from WLSE (admin>appliance>connectivity tools>SNMP Query Tool) it works fine. So I do not understand why I have this fault.
    I do not understand the fault "Inconsistent state found for query "interface.radio.basic"", someone could help me perhaps ?
    And the last question, some AP without wds configured have "Parent WDS for the Access Point" = 0.0.0.0.. I do not understand why..
    If someone could help me for one of these troubles, it would be great
    Thank You,
    regards

    All these faults are explained in detail at: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cwparent/cw_1105/wlse/2_11/ts_gd/faults.htm
    including the "Inconsistent state found for query...

  • Server 2012 R2 DHCP authentication error (1046-DHCP)

    Hello all, here is my story, hope someone can help me solve it.
    Goal :
    Getting the DHCP running on windows server 2012 R2
    Current situation :
    We have two different domains in one forest (domain-A & domain-B).
    Domain-A has several w2k8r2 servers. In Domain-A we have two server 2008 R2 domain controllers (serverA1 & serverA2). On both servers the DHCP rule is installed and running.
    Domain-B has several w2k8r2 servers. In Domain-B we have two server 2008 R2 domain controllers. Both servers don’t have DHCP server role !
    We installed 2 w2k12R2 servers (server-b1 & server-b2)  in domain-B and promoted to domain controller. We installed the DHCP server role on server-b1 & server-b2 configured the failover. The domain function lever is still w2k8r2.
    The change :
    In domain-A we unauthorized the DHCP server-A1 & server-A2 and deleted the DHCP server role.
    Restarted server–A1 & server-A2 and checked if the DHCP server role is removed.
    In domain-B we restarted server-B1 & server-B2. We authorized the DHCP on server-B1 & server-B2.
    The error :
    The DHCP didn’t go online, it gives the following error message in the event viewer (this is the only error message about the DHCP server)
    Eventid 1046, DHCP-Server
    The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain Domain-B, has determined that it is not authorized to start. 
    It has stopped servicing clients.  The following are some possible reasons for this:
    This machine is part of a directory service enterprise and is not authorized in the same domain. 
    (See help on the DHCP Service Management Tool for additional information).
    This machine cannot reach its directory service enterprise and it has encountered another DHCP service on the network belonging to
    a directory service enterprise on which the local machine is not authorized.
    Some unexpected network error occurred.
    Tried solutions :
    1) checked the local network settings, the dns server is the one in the old forest (domain-A) this is correct !
    2) Checked with adsiedit.msc if there was still an entry that was looking at server-A1 & server-A2. Nothing found. 3) I unauthorized the 2 new servers (server-b1 and server-b2) I installed a new w2k12R2 server in domain-A1, installed the dhcp server role
    only. Tried to authorizes the dhcp server but the exact same error.
    looking forward to all the ideas, and the solution
    J
    Design is the Technology

    Hi,
    According to your description, when we installed a new windows server 2012 r2 in the domain A and only installed the DHCP role, the authorization was still not success. So please check if the unauthorized and authorized process was success. To verify if
    the DHCP servers have been authorized, please try to run netsh dhcp show server
    command, then we can see the DHCP server which was authorized. And you mentioned that you have checked with ADSIEdit to see if there was an entry. Yes, we can make full use of ADSIEdit. If a DHCP server was authorized successfully, there must be an
    entry about the DHCP server in the ADSIEdit. So please check if there are some entries in the ADSIEdit of all your DCs in the domain. Ensure that only one entry about this new windows server 2012 r2 in the ADSIEdit.
    If there are different in the several DCs, please try to use AD replication to make the data consistent.
    And we must log on the server as an administrator to complete this operation.
    To check the entry, please follow steps below,
    1. Start adsiedit.msc.
    2. Open the Configuration container.
    3. Expand Services.
    4. Expand Net Services.
    Best Regards,
    Tina

  • WDS error 1067 in SCCM

    I need some troubleshooting steps for the below .
    not WDS not getting connected error 1067 in SCCM
    when pxe enabled wds getting disabled

    Hi,
    Please refer to the link below:
    SC Configuration Manager 2012 R2 OS Deployment Error at Windows Deployment Services
    http://www.microsofttranslator.com/bv.aspx?from=tr&to=en&a=http%3A%2F%2Fsocial.technet.microsoft.com%2Fwiki%2Fcontents%2Farticles%2F22949.sc-configuration-manager-2012-r2-os-deployment-error-at-windows-deployment-services-tr-tr.aspx
    In that case,the solution is install the Hotfix KB2905002.
    Below is the link to download and install this Hotfix.
    http://support.microsoft.com/kb/2905002
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Spa922 dhcp option error

    Cisco 881 Router config:
    ip dhcp excluded-address 10.1.0.129 10.1.0.130
    ip dhcp pool PHONES
       network 10.1.0.128 255.255.255.192
       domain-name blabla.com
       dns-server 10.0.2.11 10.0.2.24
       default-router 10.1.0.129
       option 42 ip 10.0.2.29 10.0.2.35
       option 150 ip 10.1.0.3
       option 66 ascii 10.1.0.3
       lease 31
    I have linksys spa922 phone with firmware 6.1.5(a) and some spa303, spa502..
    All the devices understand tftp options from dhcp server, but spa-922 not.
    I have log on debug server:
    Nov  6 09:03:09 10.1.0.131 System started: [email protected], reboot reason:H0
    Nov  6 09:03:09 10.1.0.131 System started: [email protected], reboot reason:H0
    Nov  6 09:03:09 10.1.0.131  subnet mask:    255.255.255.192
    Nov  6 09:03:09 10.1.0.131  gateway ip: 10.1.0.129
    Nov  6 09:03:09 10.1.0.131  dns servers(2):
    Nov  6 09:03:09 10.1.0.131 10.0.2.11
    Nov  6 09:03:09 10.1.0.131 10.0.2.24
    Nov  6 09:03:09 10.1.0.131
    Nov  6 09:03:10 10.1.0.131 IDBG: st-0
    Nov  6 09:03:10 10.1.0.131 src/dict_tftp.c: dictParseServerScp: 1501 script too short
    Nov  6 09:03:10 10.1.0.131 ---------- g_dict_enable[0]: 0, : -2621441
    Nov  6 09:03:10 10.1.0.131 syslog-ng[1328]: Error processing log message: <Embedded Msg>:   save param: 441 = 255 441
    Nov  6 09:03:10 10.1.0.131 DDE12 0 0
    Nov  6 09:03:10 10.1.0.131 dictTftpNum: 0
    Nov  6 09:03:10 10.1.0.131 paylen: 0
    Nov  6 09:03:10 10.1.0.131 Dict_N> Dict flash[1] err happened, check errcode1=1
    Nov  6 09:03:10 10.1.0.131 DICT_verify: 1
    Nov  6 09:03:10 10.1.0.131 Dict_N> Dict flash[1] err happened, check errcode2=1
    Nov  6 09:03:10 10.1.0.131 paylen: 0
    Nov  6 09:03:10 10.1.0.131 Dict_N> Dict flash[0] err happened, check errcode1=1
    Nov  6 09:03:10 10.1.0.131 DICT_verify: 1
    Nov  6 09:03:10 10.1.0.131 Dict_N> Dict flash[0] err happened, check errcode2=1
    Nov  6 09:03:10 10.1.0.131 3.0 deadbeef 48879
    Nov  6 09:03:10 10.1.0.131 DDE11 0 0
    Nov  6 09:03:10 10.1.0.131 DDE13 0 0
    Nov  6 09:03:10 10.1.0.131 [SCAPS]WaitTime:10
    Nov  6 09:03:10 10.1.0.131 [SCAPS]WaitTime:10
    Nov  6 09:03:11 10.1.0.131 [SCAPS]WaitTime:20
    Nov  6 09:03:11 10.1.0.131 [SCAPS]WaitTime:20
    Nov  6 09:03:12 10.1.0.131 [SCAPS]WaitTime:40
    Nov  6 09:03:12 10.1.0.131 [SCAPS]WaitTime:40
    Nov  6 09:03:14 10.1.0.131 [SCAPS]WaitTime:80
    Nov  6 09:03:14 10.1.0.131 [SCAPS]WaitTime:80
    Nov  6 09:03:14 10.1.0.131 Resolving 10.1.0.3
    What is the reason that the device does not accept dhcp option correctly?

    It is possible that SPA922 is using other option than SPA303. So at the first, you must found what option is triggering
    src/dict_tftp.c: dictParseServerScp: 1501 script too short
    error. Use option 150 but not option 66 and vice versa. It should reveal what option will cause the error.
    Also, you should catch the DHCP server's response packet. It's nice to know Cisco 881's configuration, but the bug may be in Cisco 881 itself. If it's response is malformed (in option used by SPA922 but ignored by SPA303, or SPA303 may be more resistent to bug than SPA922) then it's waste of time to play with SPA922's configuration.

  • DHCP Import Error

    I am exporting and importing from one DHCP Win2k3 server to another DHCP Win2k3 server. Exporting is no problem, but when I try to import the second DHCP server scope information, I receive the following errors: "Error while imiporting option "6." This option conflicts with the existing option ""
    I have two DHCP servers that I need to import into our single DHCP server, one goes in fine, but when importing the second set, I recieve the error above. I deleted the DHCPdb and imported the second DHCP server information, went just fine, but when importing the second DHCP server it gives the error above.
    Services Stopped and unauthorized before imports still recieve the same error. If I import only one DHCP server information it goes fine.
    Also the scopes are all different, so I am not importing duplicated information, if I were I would receive duplicate or scope already exist, but I don't.
    Any assistance would be much appreciated.
    Thank you,
    Hawaiiangirl96813

    Hello,
    did you complete follow this article:
    http://support.microsoft.com/kb/325473
    If another way is choosen, please give some more details about.Best regards
    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.

Maybe you are looking for