高定了，还是MSDN的一位高手告诉我的，TMD的MS,2000和XP的缺省工作组策略不同导致的。Did you log on both machine with "craig" user account?
in the work group environment, you need to make sure that you have same
named user account on both machine with same password.if not, DCOM will fail to authenticate you.
and there is one more thing to consider.
On XP Pro, because of the default security setting for "sharing and
security model for local accounts", this remote debugging is not allowed by default.
Below is the steps to change this setting:
1. run "Local Security Settings" in Administrator tools.
2. select "Security settings\Local policies\Security options.
3. change "Network access : Sharing and Security model for local
accounts" from "Guest only - local users authenticate as Guest" to
"Classic - local users authenticate as themselves".
4. After this, need to reboot machine.
* this change should be applied onto the both machines for remote
debugging.
After you make the setting change, you will be able to do remote debugging
with same name user accounts on both machines. However, ***there is a concern with security with this change***. Because
you changed default setting of security model, it can expose:
- unexpected file sharing
- unexpected DCOM components sharing.
Before you make this change, any kind of connection from remote machine to
your machine was guaranteed as "Guest", but after this change, he/she could
be authenticated with your local user account. So, like the case of
Debugging, if you are sharing out a folder or DCOM object, there is a
possibility that any matched user(same user name and same password) on
other
machine could access your shared objects. I strongly recommend that, if you want to use this work-around, you need to
make sure that all user accounts have strong passwords, or you had better
setup network-Island for the debugging machines to prevent any malicious
attack.thanks
Min
in the work group environment, you need to make sure that you have same
named user account on both machine with same password.if not, DCOM will fail to authenticate you.
and there is one more thing to consider.
On XP Pro, because of the default security setting for "sharing and
security model for local accounts", this remote debugging is not allowed by default.
Below is the steps to change this setting:
1. run "Local Security Settings" in Administrator tools.
2. select "Security settings\Local policies\Security options.
3. change "Network access : Sharing and Security model for local
accounts" from "Guest only - local users authenticate as Guest" to
"Classic - local users authenticate as themselves".
4. After this, need to reboot machine.
* this change should be applied onto the both machines for remote
debugging.
After you make the setting change, you will be able to do remote debugging
with same name user accounts on both machines. However, ***there is a concern with security with this change***. Because
you changed default setting of security model, it can expose:
- unexpected file sharing
- unexpected DCOM components sharing.
Before you make this change, any kind of connection from remote machine to
your machine was guaranteed as "Guest", but after this change, he/she could
be authenticated with your local user account. So, like the case of
Debugging, if you are sharing out a folder or DCOM object, there is a
possibility that any matched user(same user name and same password) on
other
machine could access your shared objects. I strongly recommend that, if you want to use this work-around, you need to
make sure that all user accounts have strong passwords, or you had better
setup network-Island for the debugging machines to prevent any malicious
attack.thanks
Min
解决方案 »
免费领取超大流量手机卡，每月29元包185G流量+100分钟通话, 中国电信官方发货