Time Capsule DHCP & VoIP Phones

Hi,
We have just received our Time Capsule yesterday. It is responsible for providing an Internet connection with DHCP to all our computers and VoIP phones in the office.
Before the time capsule, we have been running a the same setup with an Airport Express for many months without any problems. Now, some of the phones stop receiving incoming calls 1-5 minutes after being booted. A reboot will fix the problem for 1-5 more minutes and then incoming calls cannot be received anymore again.
I saw on this forum that the TC may be assigning the same IP address for more than one device. Could it be the problem? We have reverted to the Airport Express for now and we will have to return the TC if it doesn't accommodate the phones.
Can anyone help? I would also like to be able to see the list of DHCP leases on the TC to be able to troubleshoot this. Thanks.

let me know when you resolve this , I just decided to run my voips using my netgearGS 108 switch connected to my modem and then to time capusule from GS 108 lan port to Wan port of TC , my packet 8 phone and fax just work fine with this set up but took me over two days to figure it out I did not want to play around with port forwarding since I am not a techie. My TC is now set on wireless and I have shut of the wireless on my .2. wire 3800 HGV modem for money i think a TC is worth it

Similar Messages

Time Capsule DHCP settings

My BT Home Hub 2 started playing up so I replaced it with a Draytek Vigor 120. I have managed (somehow) to get it to work and have internet access despite the Vigor saying that I don't.
The Time Capsule DHCP is assigning IP addresses of 10.0.#.# instead of 192.168.#.# - any ideas how to change this format?
Thanks.

A consumer device with an LED labeled as an essential funtion but is actually redundant? This is why Apple should do their own ADSL modem...
It is not redundant.. The internet LED will light when the draytek is used as router.. it then handles the routing.. but the UK version has removed that option.. this is correct because the internet is not controlled then by the modem.. only dsl sync. The router that does authentication, actually is the internet device..
Apple have never made anything beyond dial up modems and they will never make adsl modems.. which are going to eventually be phased out hopefully as we go to fibre or vdsl.
A bridged modem is not generally accessible from a router.. the WAN port of the router is pppoe encapsulated not normal IP addressing.

Time Capsule DHCP (with Netgear DGN3500)

Hi
I have tried, inconsistently for months, to figure out the best setup for my home network.
1. I'll try to describe what I have at the moment:
i. A Netgear DGN3500 which acts as a modem (connects to adsl phone socket in wall), and a wire/less router. The netgear broadcasts a wireless network (SSID: "712 2.4GHz") and is also connected to my Time Capsule via ethernet cable. The netgear acts as a DHCP server, providing address from 192.168.3.3 - 192.168.3.9. The netgear has a static lan ip address of 192.168.3.1.
ii. My Time Capsule (connected to the internet via netgear modem via ethernet) is currently in "DHCP only" mode. The TC has a static IP address of 192.168.3.2 and provides via DHCP a range of addresses from 192.168.3.10 - 192.168.3.200. The TC also broacasts 2 wireless networks, one in 2.4GHz mode (SSID: "712 2.4GHz") and another in 5GHz mode (SSID: "712 5GHz"). Radio mode and channels are all set to "Automatic".
2. Ok. Let me explain what I've tried to achieve here.
I want to roam around my home without having to worry about wireless signal or ip addresses etc. So the idea is that I can be in my bedroom (closest to the netgear) and surf the web on my iphone/macbook pro using an ip address provided by the netgear's DHCP server, then walk into my living room (closer to the TC) and swicth to an IP address provided by the TC's DHCP server and continue surfing the web on my iphone/macbook pro without losing signal strength.
3. My problem is this:
When swicthing between routers/wlans/ip adrresses/etc. from my living room to my bedroom (ie. when swicthing between the TC and the netgear), the process is almost seamless. However, when I switch the other way around, from the netgear near my bedroom to the TC in my living room, it takes more than a few minutes for the correct IP address to be served to the iphone/macbook pro and I find that I can't connect to the internet (except via 3G on my iphone) until it sorts itself out, after clicking the "Renew DHCP lease" a hundred times, or disabling and enabling wireless on my iphone/macbook pro a hundred times. It's baffling to me why it works (quickly) in one direction but not the other.
4. What I have done, that also didn't work:
Most forum posts have suggested that the TC should simply be left in "bridge mode". I did this too. It worked (or rather didn't) in exactly the same way as I described above. The only difference, unless I'm mistaken, was that the netgear was the exclusive DHCP sever and provided the full range of IP addresses. It did indeed do this via the TC (via ethernet) as well, but also just as slowly.
Help.

I agree with Bob.. the problem is the TC is setup not in bridge not in router.. it is in fairy land.. it has to be bridge or router to work properly.. otherwise the Netgear as the primary router has no idea what IP address the device is that wirelessly connects to the TC.. and the TC cannot route the connection correctly because it isn't a router. (watch the arp table if available in the netgear or list of clients and in the TC from a computer open the advanced, log, wireless clients, in a computer, then as you roam you will see where the iphone is showing up.)
A few points.. again what Bob says about sticking with Apple products is probably true.. Apple wireless provides some details PC world doesn't.. eg country. It is also roaming which will never work as well in mixed product environment.
Are there spaces in the SSID? That is again a no no in the PC world. Even if you don't use PC's the Netgear is not designed primarily for Macs.
I would set SSID, and all the names of devices.. short.. straight alphanumeric.. no spaces.
I would also lock channels on at least one device.. two routers set to auto channel leads to chaos.. but I would lock both.. for 2.4ghz there are only three non-overlapping channels, 1, 6 and 11.
Use as much space as possible.. so 1 on the netgear and 11 on the TC.
Solution might also be to buy a Airport Extreme or Express and plug it into the netgear and turn off its wireless. Stick with Apple on Apple.. it does work better.

Configuring Time Capsule for VOIP?

I am trying to connect a VOIP phone to a Time Capsule. I was able to connect it to the internet and configure the phone, but can't make calls. I think it may be a firewall issue, and my provider says that I need to enable SIP Signaling on some specific ports and also open a media port on some specific ports. Is there a way to do this?
My system is that I have aDSL service connected to a Netgear DM111PSP. The Time Capsule is connected to this modem. And, I have connected my VOIP phone to the Time Capsule. Is this a sensible way to connect? Should I be looking at anything else besides opening the ports?
Thanks!
George

The problem is the TC is not upnp enabled.. Apple use a different system to open ports.. but it also matters if the TC is working in bridge or router and the netgear is bridge or router.. ie .. tell us exactly what is working as the main router.. is the TC using pppoe client to connect via the netgear.. if not it should be bridged.
You cannot get voip working behind double NAT.

How can I make my new AirPort Time Capsule with VOIP?

I purchased an AirPort Time Capsule because of the modem capability. The modem we have from the phone company isn't very good.
Now I have a little problem. I forgot we have our phone over internet and I cannot figure out how to set it all up.
Any ideas for my latest problem? I'd run back to the store/genius bar, but it's a ferry ride away and I'm not sure it would do any good to go back because all my phone "stuff" (cords, etc) wall jacks, is all here.
Current set up is this:
Modem box has ethernet (yellow) cable going from it to imac. It also has blue cable going from it to ATA Router (smaller black box). Each box (white larger "modem" box, and black smaller ATA Router) have a phone cord going from wall (2 separate jacks) to the box. And obviously each has it's own power cord.
I tried moving all plugs from white modem box to AP TC, but there really isn't a phone jack on back of APTC. It clicked in place in one of the <--> ports, but I'm getting a flashing amber light on the front, and no internet connection.
Any ideas for my latest issue?? I know so much more about computers than I ever wanted to know, but it obviously isn't enough.
Thanks!

I purchased an AirPort Time Capsule because of the modem capability.
There is no modem in the airport routers.. they are all plain ethernet routers.
It sounds like you have adsl modem.. and I would just leave it alone.
But if you want to play and your ISP supports PPPOE and the modem allows bridging or bridge mode.. then you can bridge the modem and use TC to establish the link to the ISP.. on the internet tab use PPPOE and put in your ISP username and password.
You can then plug the ATA into one of the LAN ports of the TC.
Overall this is probably not a great idea.
Exactly what modem are you talking about .. make and model from the base please?? Who is your ISP?
What model is the ATA? Actual model numbers from it please.
Generally you will plug the TC into the modem and use simple bridge mode.
Even though the airport wizard might attempt to take over as main router.. please do the setup manually and choose bridge mode.
See Airport Utility shows "unexpected error - please try again" when connecting to Time Capsule

Time Capsule, DHCP not providing correct gateway address

I have gone back and forth between my AP Extreme and Time Capsule and have determined that Time Capsule is not providing the proper gateway address to my wireless clients. Instead of providing the correct gw address it provides the address I assigned the base station. This is contrary to my Airport Extreme which provides the proper gw address to my wireless clients. Sounds like a bug in the DHCP base station software. Any thoughts?

I have a very similar problem. I originally had cable broadband and a Airport Extreme (AE) upgraded to 7.3.1 all worked fine. The AE was being used as a DHCP server to distribute the dynamic IP address provided by the ISP. I then replaced the AE for a Time Capsule (TC) and installed a new 802.11n Airport Express. I upgraded the TC and AExpress to 7.3.1. The TC was setup identically to the now replaced (disconnected and switched off) AE.
Unfortunately the TC failed to work as a DHCP server. It did not recognize the ISP provided dynamic IP address and replaced it with an 'Invalid' IP address which of course meant no internet access. I then replaced the TC with the original AE (identically set up) and all worked fine, including the AExpress.
While I wait for Apple to fix the TC firmware I am running the AE as the DHCP Server and the TC as a wireless bridge to the AExpress. Time Machine is recognizing Time Capsule and backups from two macs are working fine.

Time Capsule DHCP

Hi!
Please excuse my ignorance ahead of time. My buddy wants to set up a (mostly CAT 5 wired) home network. His Time Capsule is upstairs on the main floor, but his switch for his CAT 5 cabling is downstairs in the basement (PC, TIVO, ets will all be plugged into it). He wants to continue to use his Time Capsule as his wireless router.
So that beign said, can we hook up his DSL into his Time Capsule upstairs, then run CAT 5 downstairs to his switch and attach the rest of his LAN into that switch?
Will the Time Capsule then act as both his wireless and wired router?
How many IP Addresses will it hand out?
Thanks ahead of time!
Peace
Roger

Hello rdw5150. Welcome to the Apple Discussions!
So that beign said, can we hook up his DSL into his Time Capsule upstairs, then run CAT 5 downstairs to his switch and attach the rest of his LAN into that switch?
Yes.
Will the Time Capsule then act as both his wireless and wired router?
Yes.
How many IP Addresses will it hand out?
The default DHCP IP address range is from 10.0.1.2 - 10.0.1.200, but you could extend this to 10.0.1.254.

Restart every day time capsule (DHCP)

My time capsule worked pefect until a few days ago. From now on I have to restart almost every day my "time Capsule". Because it lost the connection with my provider.
After the restart it works again perfectly for about 24:00 hr.
I thought it could be due to the IP. I have a DHCP connection. But the IP of the provider changes only every 06 months and on my capsule i still have the correct IP.
Aditional information I upgraded the firmware also a few day ago.
Is there some one who have the same problem?

My time capsule worked pefect until a few days ago. From now on I have to restart almost every day my "time Capsule". Because it lost the connection with my provider.
After the restart it works again perfectly for about 24:00 hr.
I thought it could be due to the IP. I have a DHCP connection. But the IP of the provider changes only every 06 months and on my capsule i still have the correct IP.
Aditional information I upgraded the firmware also a few day ago.
Is there some one who have the same problem?

Time capsule stuck on phone

I have an odd problem with our 9 month old TC. If my iPhone 5s is connected it wont let any other connected device access the Internet. If it does it is pitifully slow with huge latency issues. (greater than 1000ms). I am baffled at this issue. I have reconfigured things several times to try and figure out why. The lack of logging is HIGHLY frustrating. The current setup looks like this:
I have the Motorola DSL router set up as the dhcp server with the TC in bridge mode. I needed to do this so I could monitor traffic in case the phone was doing something weird. I have tried several configurations with the same results. The guest network is enabled. Firmware is current 7.7.3. No jail broken devices in the house.
The traffic on the iPhone does not look suspicious when I monitor both inbound and outbound.
A Point I'm not sure is relevant but wanted to include was the TC was configured from the iPhone in question using the airport utility. I noticed accessing the TC from the iPhone doesnt require a password but does from any other device Using the airport utility.
this form for entering this post From the iPad was horrible. No text in safari, and no editing in another browser.
Thanks for for any help.

The guest network is enabled.
The Guest Network will not work correctly if the TC is in bridge mode. Remove the check mark from the box next to enable guest network, as you will not be able to use this option with a router "upstream" from the TC on the network.
The Guest Network feature assumes that you will be using a simple modem....not a modem/router or gateway on the network.
Would probably be a good idea to reset the TC back to factory defaults and set it up again.

My Working Solution: 1 Time Capsule + 2 AEBs on One Network

Over the past two weeks, I have probably spent 10+ hours messing around with one Time Capsule and 2 AEBs in an attempt to create a single roaming network. I tried everything and I searched for hours on the forums for solutions. Thanks to many others for posting tid bits here and there, I was at least able to try things I hadn't tried before. In the end, I never found a perfect answer and I even spent time on the phone with Apple. Finally, after coming close to throwing every one of these devices at the wall, I took at step back and waited a few days and came up with a solution that works perfectly for me - as of today, it's been three days without any glitch. Keep in mind though that I have the luxury of having a wired house and I have the option of running ethernet cable from one device to the other as my mechanism for "extending" the network. What I needed was the ability to walk around the house freely with wireless devices such as our iPhone, MacBook Air and my work laptop...
What I don't know is whether or not the approach I took has performance issues or if it's supported by Apple or if I am in for a sudden surprise so take my solution for what it's worth... Here is what I did...
*General Advice for Clearing out AEB/TC Settings*
- Power device on - wait till it goes through a solid and then a slow blinking amber light
- Once the device has powered up, do a hard reset (new models - push reset for 5 seconds until it blinks rapidly
- Wait until the full power up cycle completes - slow blinking amber light
- Unplug the device, wait a few seconds and plug back in, waiting until full cycle
I can not stress how important above is - just doing a hard reset will NOT clear out all your settings and you will be left with random crap that could impact your setup. This was one of the key pieces I was missing and a great apple tech helped me out
Also - start simple... no printer hookup, no extra network devices, just one computer, one TC/AEB and the internet. Add on from there. Based on this, I setup things as follows
1. Time Capsule - verified internet, etc
2. AEB #1 - again verified internet, etc.
3. AEB #2
Finally, the latest TC/AEB updates provided by Apple did appear to help - not sure exactly how but the process of setting up my 2nd AEB was easier and I ran into many less issues...
*Internet Solution:*
- Comcast Cable Modem
- Hooked up directly to the WAN port of my Time Capsule
- DHCP based solution, per Comcast setup
*Time Capsule*
- Version 7.3.1
- Acts as my main Hub, DNS Server and Router
- Name: used three words all separated with - (no spaces). Ex: my-time-capsule
- Wireless Mode
-- Create a wireless Network
-- Network Name: Z-Autobahn
-- Yes to Allow network to be extended
-- 802.11n only (5 GHZ)
-- Security WPA2 Personal
-- Under Options: Changed Multicast to 24Mbps
- Internet
-- Used Ethernet, DHCP as Comcast requires
-- Connection Sharing: Share a public IP Address
- DHCP
-- Leveraged default network / submasks 10.0.1.1 as my router, dishing out 10.0.1.2 and beyond
-- Reser*ved two DHCP reservations - one for each AEB 10.0.1.2 and 10.0.1.1
*AEB #1*
Here is the key difference - I did NOT use WDS or the Extend Network option. I had problem after problem with these options and although I can not confirm, I believe both of these leverage wireless to extend your range vs. ethernet. I also believe this is the reason folks say to NOT use the WAN port with this type of configuration
Base Station
- Named similar to TC: my-aeb-mb (where mb was a location identifier)
- WAN port is hooked up directly to one of the LAN ports of my Time Capsule
- Wireless Mode
-- Create a wireless Network (NOT WDS or Extend)
-- Network Name: Z-Autobahn (same as TC settings)
-- Yes to Allow network to be extended
-- 802.11n only (5 GHZ)
-- Security WPA2 Personal (exact same security setup and password)
-- Under Options: Changed Multicast to 24Mbps
- Internet
-- Used Ethernet and Manually
-- IP Address: 10.0.1.2 (matches what I reserved from the DHCP settings of time capsule)
-- Subnet Mask: 255.255.255.0 (vs. default 255.255.0.0)
-- DNS Server 10.0.1.1
-- Connection Sharing: off (Bridge Mode)
*AEB #2*
I followed the exact same process as AEB #1 with the exception of the following 2 settings
- Name: my-aeb-lr
- IP Address: 10.0.1.3 (matches what I reserved from DHCP settings of time capsule)
*Other Random Thoughts*
Prior to setting up above, I experienced a ton of issues - network would drop, an AEB would disappear, random instability, you name it. Above setup has worked well for a few days now.
I also have a bit of a more complex setup - there is actually a full switch running in between the TC and the AEBs but this should be irrelevant. I just happen to have a full wired house. I am sure someone will ask my the **** I even borrowed with above - the answer is simple. Ports are great when you know exactly where your computer or network device is going to be BEFORE your house is built.
All my machines (with the exception of my work laptop) are setup with a WINS workgroup called "workgroup" so that I can share between my macs and my pcs. You don't need to mess with this if you are all mac.
*Quick Note on Windows XP*
By default, Windows XP does NOT support WPA2 which means you can't use a true 802.11n solution at 5ghz. You can download a hot fix for SP2 from Microsoft. The KB article is: 893357 and can be downloaded from here: http://support.microsoft.com/kb/893357. This is NOT an issue with Windows Vista.
Finally - I am not a network expert but I work in the SW industry. I would love to get thoughts from someone that is really experienced in networking to help me understand if I did something that is screwed up. Things seem to work for me.

I realized I only used the abbreviation AEB vs. Airport Extreme. Caught this after the 15 minute edit restriction. Added in case folks are searching by Airport Extreme. In addition, the solution I setup is a Roaming Network solution vs. "one network". Enjoy!

Can Time capsule be used a normal router?

and I would like all my macs to connect to the internet as well. Is this possible? thanks

To answer your original question, yes Time Capsule can be used as a normal router. Think of it as a router with a built in hard drive. And yes all your Macs can connect to it to share Internet.
Now as for your second question, how are you accessing the Internet right now? Because you can't connect the Time Capsule to your phone jack on the wall. I'm assuming you're using some kind of DSL. If so, then you need to connect your DSL modem to the Time Capsule, not Time Capsule to your phone wall jack. Then you'll be able to share and connect with all your Macs. Make sense?
Time Capsule has ethernet ports (bigger "phone" jack), take the ethernet cable from your DSL modem and plug it into the WAN ethernet port of the Time Capsule.
If you're on dial-up, then you can't share Internet with all your Macs. (Actually you could, but it's going to be painfully slow and not worth it)

Time Capsule not discoverable on some devices

I have a very odd situation, my time capsule is only able to be dicovered by some of the devices I am using. Up until recently I had no problems at all, my iMac, Mac Mini, 2 iPad 2, 2 iPhone 4S', and my Xbox 360 were all able to see and connect to the Time Capsule no problem.
A few days ago one of the iPhone's started acting up and could not discover the Time Capsule anymore, her phone has had issues though before so I thought it was in isolated thing. Came home today and my XBox 360 or my iPhone 4S said it couldn't find the Time Capsule,
Checked the settings, and the Time Capsule wasn't their, the Mac Mini, our iMac and my iPad 2 see it fine, and connect to it nrormally. The Xbox 360 as well as both iPhone 4S' can see other networks and connect to them just fine as well.
I reset the Time Capsule to factory settings, and reconfigured it, issue persists, even reset my iPhone to factory default it will find my ATT UVerse modem/router that the Time Capsule is connected and it can connect just fine to that (which everything else can as well) but still cannot find the Time Capsule at all for any reason,
My major concern is that this is going to get worse and other devives will slowly stop being able to discover or connect to this Time Capsule as well.
Any ideas? This one stumps me like crazy.

Ok,
What model exactly is your TC.. A1xxx from the rubber base?
How old about?
Too much auto.
1. Auto wireless channels on both the uverse and the TC doesn't work that well.. fix channels manually.
Ie use channel 6 for the uverse and channel 11 for the TC at 2.4ghz. You can also fix the 5ghz although it is less of a problem as the uverse doesn't use it.
Channel 1 seems to often not work with the iphones.. i wonder if bluetooth is using it. ??? Anyway avoid it.
2. Naming is bad. Change the TC name and wireless names to meet SMB standard. Which the Uverse does.. and has no issues.
Names are short, 20 characters at most. .try to keep to 10 or less.
No spaces.. spaces are illegal and apple replaces them with dashes anyway.
No apostrophe or any other non-alphanumeric value.. stick to pure numbers and letters.
3. Use only WPA2 AES or Personal security in the TC. All alphanumeric password.
4. Decide if you want to use roaming network. I think it is a good idea.
Use identical names on uverse and TC.. identical security settings.. different channels, as per 1.
This is the apple doco for roaming.. I have suggested the same only with different products. And one difference in manually set channels.
http://support.apple.com/kb/ht4260
5. If you continue to have issues.. take the firmware back to 7.6.1 or even earlier 7.5.2 is excellent on Gen3 or earlier TC. Do not use 7.6.3.. it is a dog.

Time Capsule Placement

Hello everyone,
I recently had to switch offices... so I'm in the process of moving stuff around.
I had to put my Time Capsule on top of a table right nex to my desk... could this be harmful in any way? I mean, having it so close (3 feet away just bellow shoulder level) to where I'm stiing?
Sorry if the question seems too basic or "naive", but I want to be sure.
Also, should I avoid placing other electronics right next to the Time Capsule? (cordeless phone, bluetooth speaker, bluetooth radio (iHome)
Thanks!

Keep any other electronic devices as far away as possible from the Time Capsule.
If you have a cordless phone, you are picking up far more radiation from that device than the Time Capsule.

Est-il possible de connecter un téléphone VoIP sur un port LAN de Time Capsule ?

Est-il possible de connecter un téléphone VoIP sur un port LAN de Time Capsule ? Genre Gigaset A 510 IP ou C 610 IP.

Paolo,
Tu as completement raison...
J'ai des problemes de visions qui agissent differemment de temps a autre.
Oui.. ce sont des partis completement independents, donc sans limitations...
Je remet ma "patch" noir sur mon oeil..
Desole' pour la confusion..
R

DHCP - Cannot add text option for VOIP phones in OES Linux

While working through this, I solved the issue, but decided to post this anyway as it may help others to find these sorts of errors.
I'm working on migrating from NetWare 6.5sp8 to OES11sp2. Client has Shoretel VOIP phones. Existing NetWare-based DHCP has no problem. Option 156 has been configured to give out the required text information that Shoretel phones require.
Problem is that I could not get the OES11 DHCP to run with that option. Nor could I migrate the existing option over - the Migration Tool (in OES11) says it successfully migrates DHCP, but I cannot start the dhcpd daemon. Error is that it failed, and in the rc.dhcpd.log file I see an error:
LDAP Line 26: unknown option dhcp.Shoretel_Boot.
LDAP Line 26: unexpected end of file
LDAP: cannot parse dhcpService entry 'cn=newdhcpservice,o=LIBRARY'
Configuration file errors encountered -- exiting
If I look in the file (created when LDAP reads DHCP config from eDirectory apparently) dhcp-ldap-startup.log I can see the problem entry at line 26:
option Shoretel_Boot "FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,L AYER default-lease-time 259200 ;
This option does NOT show up in the newdhcpservice option when I look at it in ConsoleOne, or DSBROWSE, or DNS/DHCP Management Console.
This option DOES show up in the DNS/DHCPManagement Console if I look at the DHCP (NetWare) tab and look at Other DHCP Options for some of the configured subnets, but it actually has different text from the above, specifically:
FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,LAYER2 TAGGING=1,VLANID=9
Note that it does not have a " character anywhere in the entry. This option is configured as a Global DHCP text option.
Novell TID 7009464 mentions the issue, though not for Option 156. In that TID there is this:
"Situation #2
Migrate a working DHCP server with DHCP options that are of type "Text" to an OES server.
Load the DHCP server service... it fails to load and gives similar errors to the ones listed above."
Under resolution the TID says to delete and recreate the dhcp service object without the text option and it will load. That doesn't work for me as I still get an LDAP error pointing to the Shoretel_Boot unknown option. (I dare not try deleting it from the NetWare DHCP config and risk breaking the client's phone system).
One of the options in the TID to fix this is to re-enter the data using the DNS/DHCP Management Console - but that didn't work.
Here is the answer:
First, the log files are misleading. The error message points to not being able to read the newdhcpservice object entry - but the problem was elsewhere. In fact the problem showed up in the logs even when there were no option 156 entries at all in any object inside the newdhcpservice or the newdhcpservice object itself. The problem existed in the NetWare configuration of the object for one of the dhcp subnets.
Specifically, there was an illegal character in the text entry for option 156 - the # character was in there, like this:
FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,LAYER# 2TAGGING=1,VLANID=9
If you look at the error log entry for syntax error you can see that the option 156 text stopped at the # symbol, and then default-lease-time was appended to the end.
Removing the # symbol got things working.
Craig Johnson
(former Novell partner / sysop)

On 30/08/2014 21:16, phxazcraig wrote:
> While working through this, I solved the issue, but decided to post this
> anyway as it may help others to find these sorts of errors.
>
> I'm working on migrating from NetWare 6.5sp8 to OES11sp2. Client has
> Shoretel VOIP phones. Existing NetWare-based DHCP has no problem.
> Option 156 has been configured to give out the required text information
> that Shoretel phones require.
>
> Problem is that I could not get the OES11 DHCP to run with that option.
> Nor could I migrate the existing option over - the Migration Tool (in
> OES11) says it successfully migrates DHCP, but I cannot start the dhcpd
> daemon. Error is that it failed, and in the rc.dhcpd.log file I see
> an error:
>
> LDAP Line 26: unknown option dhcp.Shoretel_Boot.
> LDAP Line 26: unexpected end of file
> LDAP: cannot parse dhcpService entry 'cn=newdhcpservice,o=LIBRARY'
> Configuration file errors encountered -- exiting
>
>
> If I look in the file (created when LDAP reads DHCP config from
> eDirectory apparently) dhcp-ldap-startup.log I can see the problem entry
> at line 26:
>
> option Shoretel_Boot
> "FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,L AYER default-lease-time
> 259200 ;
>
>
> This option does NOT show up in the newdhcpservice option when I look at
> it in ConsoleOne, or DSBROWSE, or DNS/DHCP Management Console.
>
> This option DOES show up in the DNS/DHCPManagement Console if I look at
> the DHCP (NetWare) tab and look at Other DHCP Options for some of the
> configured subnets, but it actually has different text from the above,
> specifically:
>
> FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,LAYER2 TAGGING=1,VLANID=9
>
> Note that it does not have a " character anywhere in the entry. This
> option is configured as a Global DHCP text option.
>
> Novell TID 7009464 mentions the issue, though not for Option 156. In
> that TID there is this:
> "Situation #2
> Migrate a working DHCP server with DHCP options that are of type
> "Text" to an OES server.
> Load the DHCP server service... it fails to load and gives similar
> errors to the ones listed above."
>
> Under resolution the TID says to delete and recreate the dhcp service
> object without the text option and it will load. That doesn't work for
> me as I still get an LDAP error pointing to the Shoretel_Boot unknown
> option. (I dare not try deleting it from the NetWare DHCP config and
> risk breaking the client's phone system).
>
> One of the options in the TID to fix this is to re-enter the data using
> the DNS/DHCP Management Console - but that didn't work.
>
> Here is the answer:
> First, the log files are misleading. The error message points to not
> being able to read the newdhcpservice object entry - but the problem was
> elsewhere. In fact the problem showed up in the logs even when there
> were no option 156 entries at all in any object inside the
> newdhcpservice or the newdhcpservice object itself. The problem
> existed in the NetWare configuration of the object for one of the dhcp
> subnets.
>
> Specifically, there was an illegal character in the text entry for
> option 156 - the # character was in there, like this:
>
> FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,LAYER# 2TAGGING=1,VLANID=9
>
> If you look at the error log entry for syntax error you can see that the
> option 156 text stopped at the # symbol, and then default-lease-time was
> appended to the end.
>
> Removing the # symbol got things working.
>
> Craig Johnson
> (former Novell partner / sysop)
Thanks for taking the time to post the above as I'm sure it will help
someone else in the future.
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

Time Capsule DHCP & VoIP Phones

Similar Messages

Maybe you are looking for