Hell. I'm running WBEMTEST from a PC to connect to another one with WXP
SP2 and even:
1. The firewall is down.
2. Applied the commands:
netsh firewall set service RemoteAdmin enable
netsh firewall add portopening protocol=tcp port=135 name=DCOM_TCP135
3. Did the workaround suggested in:
http://support.microsoft.com/kb/909444
4. Ran the workaround in: http://support.microsoft.com/kb/884573
5. Added the account I use to access by Wbemtest with to the Default
Lauch Permissions with Full Control.
6. Checked up the registry
:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\forceguest
were set to 0.
missing?!?!?!?Are you looking for SQL Server Integration Services help?|||
Did you ever get a response or resolution to this?
Hopefully, your system isn't still DOA 7-8 months later.
We have exactly the same issue with a brand-new server running WinServer 2003x64 R2
Have installed/reinstalled the entire OS three times now. The solution I guess is to do yet another reinstall and then not install the rogue security patch but that would leave us vulnerable to whatever the security patch was trying to fix and who knows what future M/Soft update won't do something similar?
|||Are you having SSIS problems when trying to connect to the SSIS service via Management Studio?http://www.ssistalk.com/2007/04/13/ssis-access-is-denied-when-connection-to-remote-ssis-service/
No comments:
Post a Comment