Apple Extreme 802.11ac: Allow DHCP renewal packets

I recently purchased an Apple Extreme 802.11ac router, as my trusty, old WRT54G running dd-wrt has finally died. I’m not too happy that this router doesn’t support stateful packet inspection — I need to know what my kids are viewing. Other than that, it’s been super easy to setup.

Anyway, my AT&T 3600HGV modem is running on (somewhat) bridge mode (see here), so I needed to allow my AirPort Extreme to accept DHCP renewal packets, so it didn’t keep trying to renew it’s public IP from AT&T. All you need to do is:


Save the settings, update, and that’s it.

Remotely reboot Linksys WRT54G

I had the need the reboot my Linksys WRT54G router remotely. Unfortunately, the web interface is not like DD-WRT where a reboot button is available; however, there IS a hidden page.

1. Login into the web admin page, which is by default:
2. Add reset.htm, as in
3. Click “Yes” to reboot.
4. Voila!

Another method is to back up your config, the restore it — but do this with caution!

PsTools communication errors

My friend Anthony was getting “access denied” and “logon failure” errors when trying to to run psexec (from one of the PsTools suite) from an XP machine on a domain to an XP machine in a workgroup.  It was something similar to:

PsInfo 1.34 – local and remote system information viewer
Copyright (C) 2001-2002 Mark Russinovich
Sysinternals –

Could not connect to machine_name:
Access is denied.


PsInfo 1.34 – local and remote system information viewer
Copyright (C) 2001-2002 Mark Russinovich
Sysinternals –

Couldn’t access machine_name:
Logon failure: unknown user name or bad password.

Here are the settings/steps I checked/took that resolved the issue:

1. ping – was able to ping the machine by hostname.  So no problem here.

2. net share – verified the ADMIN$ share was enabled.  Again no problem here.

3. Remote Registry service – verified the service was started because the PsTools suite makes use of RPC calls via port 445.  Was fine here.

4. Administrator password – verified the Administrator did not have an empty password.  Was set here.

5. Test account – created a test account to use for psexec (e.g., psexec \\computer_name notepad.exe -u test -p test).  Was available here.

6. Access hidden share – tried to access C$ and found that user name field grayed out.  This tipped off the problem – cool!

To fix it, I had to set the Network Access: Sharing and security model for local accounts security option Classic – local users authenticate as themselves.

Access it via Start > Run > secpol.msc > Local Policies > Security Options (see screenshot below).


Apparently, updates to Windows XP now sets this security option to Guest only – local users authenticate as Guest, which denies the ability to implicitly or explicitly use of a specific user name/password combo.

Hope this helps someone out there.  Peace.