![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
|
If you use it as the COM+ identity, does it work? If I understand correctly the question, I use this account for my COM+ component. I set up this component as Server application and changed identity from Interactive user to this domain account. I thought, it would be the trick of impersonation ( I set to Packet/Impersonate) of user - no it does not work. My domain account has Admin rights on both boxes - my Win2Pro and another (where shares are - both: $ and public), that COM+ is accessing. Victor "Klaus H. Probst" <usenet001 (AT) vbbox (DOT) com> wrote in message news:OrR2BoHyEHA.3104 (AT) TK2MSFTNGP15 (DOT) phx.gbl... "VK" <vk (AT) nowhere (DOT) net> wrote in message news:4xTkd.66570$fF6.30308322 (AT) news4 (DOT) srv.hcvlny.cv.net... Yes, I do. I see the icon spinning in Component Services control center when I call the method. OK, just checking. I use my own domain account to make sure it has permissions to read/write on the network share. If you use it as the COM+ identity, does it work? Maybe, I am missing any Service Pack? Well, I'd make sure you have the latest of everything but a simple thing like should work regardless. Does it matter if I try this component on Win2K Workstation, not Server? No, they behave exactly the same. The other thing I could think of is maybe a firewall that's blocking traffic from one server to another? FWIW, I'm running W2KPro here and I just tried a simple COM+ app under a domain account and I can access the c$ share on my Windows 2003 server after making the account an admin on the box. -- Klaus H. Probst, MVP http://www.vbbox.com/ |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |