Access To Message Queue System Denied Windows 7 Reading Windows 2003 - Windows 2008

I have an application that reads/writes from/to message queues on remote application servers. The clients usually run on machines outside of the servers' domains/forests with no trust setup.

In Windows XP this was no problem, but with the introduction of Windows 7 it stopped working.

After some research I found the suggested Registry tweak for the server (the NewRemoteReadServerAllowNoneSecurityClient DWORD in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters\Security fix) and implemented that, but the software still throws an exception that access was denied to the Message Queuing 开发者_如何学Pythonsystem.

The message queuing system on our test server is wide open, with full control for both the EVERYONE and ANONYMOUS LOGIN accounts.

What am I missing?

I've been dealing with Microsoft support for a little over a week and they have confirmed that this is a bug in Windows 7 and in Windows Server 2008. I'll come back and add more details about when they expect a fix or workaround when I have that information, but for the time-being it appears that this is simply a bug and unworkable.

Try these blog posts:

http://blogs.msdn.com/b/johnbreakwell/archive/2010/03/24/understanding-how-msmq-security-blocks-rpc-traffic.aspx

http://blogs.msdn.com/b/johnbreakwell/archive/2008/06/27/cross-forest-msmq-you-need-to-be-trusting.aspx

http://blogs.msdn.com/b/johnbreakwell/archive/2008/04/29/clear-the-way-msmq-coming-through.aspx

http://blogs.msdn.com/b/johnbreakwell/archive/2008/02/14/how-do-i-send-msmq-messages-between-domains.aspx

Cheers

John Breakwell

Plumbersmate.EU

Could you clarify if you are having problems sending or receiving? Sending and receiving use different network protocols and problems are resolved with completely different approaches. As you mention that the application throws an exception then I will assume you get Access Denied on Remote Read operations only.

It sounds like the NewRemoteReadServerAllowNoneSecurityClient problem. You wrote "Thus far I've added the necessary DWORD key/values in the registry, rebooted the server," - which machine(s) did you change the setting on?

Cheers

John Breakwell