Server is running Win2003
Work server on a domain IP is 192.168.50.5 and my home ip is 192.168.60.X.
My server at work has a shared called Files and it's shared to a domain
group. I have a VPN connection from my house to the office.

On any of my XP machines from home, I can go to \\192.168.50.5\Files and it
will let me login. My login would be something like domain\administrator
with the domain admin pw and I'm in. When I do this in Win7, I can not get
in and the Diagnose tells me it's because of credentials and the error code
I'm getting is (0x80004005). I've looked this up on Google but all I'm
getting is something about Media Player but I do see someone asking the same
question with Vista and never got an answer. I've never played with Vista.
I'm moving all my users from XP to Win7.

Thanks!

"pvong" <vonger@*dot*com> wrote in message
news:#zCHYYzkKHA.4772@newsgroup

> Server is running Win2003
> Work server on a domain IP is 192.168.50.5 and my home ip is 192.168.60.X.
> My server at work has a shared called Files and it's shared to a domain
> group. I have a VPN connection from my house to the office.
>
> On any of my XP machines from home, I can go to \\192.168.50.5\Files and
> it will let me login. My login would be something like
> domain\administrator with the domain admin pw and I'm in. When I do this
> in Win7, I can not get in and the Diagnose tells me it's because of
> credentials and the error code I'm getting is (0x80004005). I've looked
> this up on Google but all I'm getting is something about Media Player but
> I do see someone asking the same question with Vista and never got an
> answer. I've never played with Vista. I'm moving all my users from XP to
> Win7.
>
> Thanks!
>

When you make a VPN connection, you simply set up an IP connection. It is
not like a login on a LAN. You do not log in to the domain. Even if you
specify a domain username, this is used only to verify that you have
permission to connect by VPN. If you try to map a share, the credentials
used will be the ones you used to log in to your local machine, not the ones
you used to make the VPN connection.

The best idea is to use the "net use" command to map the share. This allows
you to enter a username and password for the share.

Work and home are connected by hardware VPN. The appliance at work is
always connected to my appliance at home so I'm not logging in to the VPN
because it's always there. I'll try the "net use" and see if that will
work.

Thanks!
Phil


"Bill Grant" <not.available@newsgroup> wrote in message
news:u5D5bs2kKHA.2188@newsgroup

>
>
> "pvong" <vonger@*dot*com> wrote in message
> news:#zCHYYzkKHA.4772@newsgroup

>> Server is running Win2003
>> Work server on a domain IP is 192.168.50.5 and my home ip is
>> 192.168.60.X. My server at work has a shared called Files and it's shared
>> to a domain group. I have a VPN connection from my house to the office.
>>
>> On any of my XP machines from home, I can go to \\192.168.50.5\Files and
>> it will let me login. My login would be something like
>> domain\administrator with the domain admin pw and I'm in. When I do this
>> in Win7, I can not get in and the Diagnose tells me it's because of
>> credentials and the error code I'm getting is (0x80004005). I've looked
>> this up on Google but all I'm getting is something about Media Player but
>> I do see someone asking the same question with Vista and never got an
>> answer. I've never played with Vista. I'm moving all my users from XP to
>> Win7.
>>
>> Thanks!
>>

>
> When you make a VPN connection, you simply set up an IP connection. It
> is not like a login on a LAN. You do not log in to the domain. Even if you
> specify a domain username, this is used only to verify that you have
> permission to connect by VPN. If you try to map a share, the credentials
> used will be the ones you used to log in to your local machine, not the
> ones you used to make the VPN connection.
>
> The best idea is to use the "net use" command to map the share. This
> allows you to enter a username and password for the share.