Fix 0X000008F0: Alias Not Forwarding Error

I know this error is infuriating—you set up an alias, you expect messages to flow, and instead you get a cryptic code that means nothing. Let's cut straight to the fix.

The Quick Fix: Reset the Forwarding Entry

Open a command prompt as Administrator. Then run:

net stop messenger
net start messenger
net config messenger /forward:yes

After that, check your forwarding list:

net config messenger

You should see Forwarding: yes. If the alias still isn't forwarding, you might need to remove and re-add the forwarding entry. Here's how:

net name alias /delete
net name alias /add

Replace alias with the actual alias name that's failing. This clears out any corrupted forwarding state.

Then test with a quick message from another machine:

net send /domain:yourdomain "test"

Why This Works

The 0X000008F0 error maps to NERR_NameNotForwarded, which means the messenger service can't find a forwarding entry for that alias. The service stores these in memory, and sometimes that table gets out of sync—maybe after a network change, a service restart, or a botched update. Restarting the messenger service clears the table, and then the /forward:yes command re-enables forwarding globally. Deleting and re-adding the alias forces a fresh entry.

I've seen this happen most often on Windows Server 2008 R2 and Windows 7 machines that still use the legacy Messenger service for LAN alerts. It's not a modern protocol, but plenty of internal tools still rely on it.

Less Common Variations

Sometimes the fix isn't that straightforward. Here are other culprits I've run into:

Firewall Blocking Port 139/445

If the messenger service can't broadcast, forwarding fails. Check Windows Firewall rules for NetBIOS and SMB. Temporarily disable the firewall to test, but if that fixes it, add an inbound rule for TCP 139 and UDP 137-138 instead of leaving the firewall off.

Service Dependency Failure

The Messenger service depends on the NetBIOS interface. If that's disabled, you'll get this error. Open Services.msc, find Messenger, and confirm its dependencies are running:

NetBIOS Interface
Remote Procedure Call (RPC)

Registry Corruption

In rare cases, the forwarding configuration in the registry gets mangled. Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Messenger\Parameters

Look for ForwardName and ForwardAddress values. If they point to a nonexistent server or an invalid address, delete them and recreate them with the correct info. Back up the key first, obviously.

Prevention: Stop It From Coming Back

Once you've got it working, here's how to keep it that way:

Set the Messenger service to Automatic if it isn't already. Right-click the service, Properties, and change Startup type.
Document your forwarding aliases. If you ever need to rebuild a server, you'll know exactly what to recreate. I keep a small text file with all alias names and their target addresses.
Monitor the service health. Add a simple scheduled task that runs net config messenger daily and logs the output. If forwarding ever flips to no, you'll catch it early.
Keep the system patched. This error is old, but each Windows update can change service behavior. Test after major updates.

That's it. This error is annoying but usually a quick fix. Start with the service restart, then move to the alias re-add, and you'll be back in business in under five minutes.