views:

128

answers:

3

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 system.

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?

A: 
John Breakwell
Hi John,Actually I already read through all of those. The only solution I haven't tried is establishing a bidirectional trust relationship between domains, and that's because that's not an option in our environment (or so I'm being told by the people in charge of that aspect of the environment).Thus far I've added the necessary DWORD key/values in the registry, rebooted the server, given as open permissions as I can on the MSMQ system, and still no dice.
Matt R.
A: 
John Breakwell
It's an exception on the remote read. The registry change has been made to the server on which the queue exists.Win7 --READ--> Q on Win2K3 with Registry Modification
Matt R.
A: 

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.

Matt R.
Well, that sucks. Who are you working with at MS?
John Breakwell
The support engineer was Imelda, who informed me that the patch for this will likely be part of Windows 2008 SP3.
Matt R.