IGD Connection Failed?

I believe this is the Server Manager daemon trying to autoconfigure your AirPort Base Station's port mapping. (New feature in 10.5 server for standard or workgroup configs.) It's complaining that the AirPort Base Station is rejecting the password serveradmind found in your system's keychain.

--J^T

Message was edited by: J^T

Message was edited by: J^T

I am seeing this in my 10.5.1 server log as well.

Any idea on how to make it go away?

I do remember during server configuration I was asked if I wanted to auto confugure my AirPort base station -- but I said "No" or "Skip".

Any update to this one? I'm having the same issue on my Leopard server 10.5.1

Same here

I think I understand the meaning of this message. I'm looking (as are the others on this post) for a resolution to the issue.

Specifically, I've installed my server remotely and was never prompted for a password to my AEBS (Airport Extreme Base Station). I've seen other postings where admins installed their AEBS after installing Leopard Server and similarly never saw the initial prompt for the AEBS password.

What we need is information on how to give Leopard Server this information or how to make it stop trying. Ideally, I'd like to know both pieces of information. Right now, I'd like to know where this Keychain information is stored, who needs permissions to it, and what does it look like. Any help?

After much digging through documentation, I think I've found the answer:

The server can configure port mapping automatically on an AirPort Base Station that
has the default password (public). If the base station has a different password, you can
enter it while setting up the server locally, and the server will be able to configure port
mapping on the base station. If you set up your server remotely, it will be able to
configure port mapping automatically as long as your base station uses the default
password.…

Automatic configuration of an AirPort Base Station requires that the setting IPv6 Mode
be set to Tunnel in the AirPort Utility application (located in /Applications/Utilities/).
The AirPort Base Station must be set up to share an Internet connection with
computers connected to it by Ethernet.

Only standard and workgroup configurations of Leopard Server configure an AirPort
Base Station automatically. An advanced configuration of Leopard Server leaves port
mapping to the administrator.

I'd be curious to hear if this worked for you. I had the same issue initially. I reconfigured the AirPort Base Station to the default password, but now I get the following:

server servermgrd[90]: Unable to access the Airport Password item

Any clues on what that might mean? It just keeps repeating every 15 minutes or so....

I haven't been able to install the latest server software upgrade (probably because of this)

Thanks,

Ed

I figured out a fix for this problem (at least for me). The issue was that I had my Airport Extreme with the "public" password while I set up the server, and then changed back to a secure password later. I didn't realize that the server would try to access it later.

The password is stored and can be changed in the keychain belonging to the Administrator account created during server setup.

While signed in as the Administrator, go to Applications -> Utilities -> Keychain Access. Under System Keychain, there should be an entry for your Airport Base Station. You can go in and change the password to the correct one.

Any guide on how to configure this or turn it off? I just bought a Time Capsule; I'm seeing both the "IGD connection failed: password not accepted" and "synch needed /private/etc/nat/autoportmap.plist" messages every minute in my server logs, and I'm seeing a linked "authorization failed" message in my Time Capsule every minute logs. Searching through the Server documentation does not make it clear how to resolve this.

I would much rather turn this off than let my Server install configure my Time Capsule.

I don't want this turned on either. I have an extreme here that I had to spend 2 hrs on the phone with Apple to get around a bug where the airport just locks up hard due evidently to rogue IPv6 traffic. (there's a giant thread on this somewhere around here, involves either downgrading the firmware one point or disabling IPv6 support) So I don't want the server even attempting to touch it now that I've finally got it stable. Especially hearing that it's related to IPv6. Last thing I need now is for my server to login to the APX and turn IPv6 back on and cause it to start crashing again.

If anyone figures out how to configure this behavior (besides reinstalling server!) please let us know.

I can pretty much confirm - at least for me - that this does not work. I changed my password on the base station, then tracked down the three passwords in the admin keychains matching "airport" and changed them to match.

Error still shows up every 15 seconds or so in the system log.

The fix oban89 suggested didn't work for me, too.
I corrected the password stored in my keychain's element of kind "AirPort base station password" named with the name I gave to my Airport Extreme base station but I still get this lines in my system log:

Jun 10 17:44:36 myservername servermgrd\[62\]: Port mapping operation attempted for 1 port(s)
Jun 10 17:44:36 myservername servermgrd\[62\]: 0 : Adding a mapping for port 80 for TCP
Jun 10 17:44:36 myservername servermgrd\[62\]: synch needed /private/etc/nat/autoportmap.plist
Jun 10 17:44:36 myservername servermgrd\[62\]: servermgr_calendar: created default calendar virtual host
Jun 10 17:44:41 myservername servermgrd\[62\]: servermgr_ipfilter:ipfw config:Notice:Flushed IPv4 rules
Jun 10 17:44:41 myservername servermgrd\[62\]: servermgr_ipfilter:ipfw config:Notice:Flushed IPv6 rules
Jun 10 18:14:44 myservername servermgrd\[62\]: Unable to access the Airport Password item
Jun 10 18:14:44 myservername servermgrd\[62\]: synch needed /private/etc/nat/autoportmap.plist
Jun 10 18:14:46 myservername servermgrd\[62\]: IGD Connection Failed: password not accepted
Jun 10 18:15:43 myservername servermgrd\[62\]: synch needed /private/etc/nat/autoportmap.plist
Jun 10 18:15:45 myservername servermgrd\[62\]: IGD Connection Failed: password not accepted
Jun 10 18:16:43 myservername servermgrd\[62\]: synch needed /private/etc/nat/autoportmap.plist

…and so on.
Moreover, my system (Mac OS X 10.5.3 Server) almost never shuts down correctly. It gets stuck with the spinning grey circle and I have to turn it off holding down the power button… but this is another story.

The server keeps a list of what it thinks the portmappings should be at /etc/nat/autoportmap.plist.
If you set the syncTime value in that file to the current date, it should stop trying to sync the portmappings until that file changes again.

- Leland

Thanks for the tips Leland!
Sadly, this doesn't solve the original issue, that is "how to get the automatic portmapping working"… :/