Connectivity - Legacy vb6 dcom client / server application

[adagio62]

I am new to this site and not sure if this where I should be...

I am debugging connectivity with a legacy vb6 activex dcom application using windows 7 pro 32 bit as the client.
The client has been running under 2000 and xp with no issues for years, and am now attempting to use windows 7 pro before replacing our remaining xp pro machines. Client and server run locally on windows 7 pro, but when pointed to a windows 2003 server the activex exe launches on the server, hangs for around 30 secs and then appears to time out(callbacks are attempted but I believe are being denied).. Nothing in the windows logs.. This appears to be some sort of permissions/security issue I suspect. Is there a way to set logging levels for dcom under windows 7 ? Or, if you if you have other sugestions I would greatly appreciate, I need to get this solved quickly..

Thanks in advance..

 

[cluberti]

By default, the browser runs as a low-IL process in Windows Vista and higher, and as such has very limited access to the local filesystem, registry, COM, and RPC/Pipes. You might want to try placing the site that loads the activex control into the trusted sites list, as sites that load from trusted sites are loaded in a medium-IL process, which is the same level of security as all other processes started by a user on a Vista or Win7 system.