"Windows cannot locate your roaming profile"

Hello,

Let me give you a quick reference of the problems that I am having.

We have 3 Dell servers. One is our PDC one is file server and the third
server is running ProjectWebAccess. All servers are running server 2003.

It seems that since we started to use Microsoft server 2003. We have
inherited the problems of: "Windows cannot locate the server copy of your
roaming profile"

I have been tryiing to solve this issue for the past year and 1/2.

We recently aquired the new Dell server 2800 that is also running server
2003 and project web access.
What I have been able to notice that I have 3 servers is that the file
server and projectwebaccess is that we loose connection to both this servers
at different times of the day. It hasnt been too much of a deal to have to
re-start computers around the office 5 to 6 times a day to be able and load
roaming profiles, but now that we are using one server for timecards, that
just cant happen, employees need to fill out their timecards, and project
managers need to be able to load their projects. But the connection to the
servers brake, it seems most times at the same time.

I had already posted this problem here before and was given this article to
read and work with, but it didnt solved my problem.
http://support.microsoft.com/kb/898060/

My file server has service pack 1 installed, I have installed the "Hotfix"
and it didnot solve the issue.

The server running ProjectWebAccess after reading the above articles and
several bumps on my head from hitting it on the wall. I erased the server,
did not installed server 2003 service pack one, re-installed everything that
is needed for ProjectWebAccess and I am still having the same problem.Keep
loosing connection for up to 1/2 hour at the time
I have also uninstalled KB893066 from my XP PRO desktop.

Please help me,

your truly,

Joe Hernandez
UPDATE: Oliver O'Boyle sugested

The issue is probably related to lack of connectivity to your Active
Directory Forest.

I would focus mostly on the server that is acting as your domain controller.
Ideallly, you should have 2 DCs in a network anyway. This is for redundancy.
If you are able to do this, I recommend it. If not, then you risk losing
your AD, and will be more prone to problems like this.

Just out of curiosity though, have you tried replacing the ethernet cable to
your DC? Have you tried using a different switch port (if you are using a
hub, you could be hacing other issues as well).

Oliver

--------------I dont think its the domain controller, when we go
authenticate we receive the message "windows cannot locate your roaming
profile....." but what is interesting is that even though we are working with
a temp profile I can still go the file server and access only the folders
that I have rights to, same with the rest of the staff, so we are being
granted permision, and 2 other servers become unavailable.

It could be the name resolution issue. what do you receive if you using net view \\servername? Or check this link,

roaming profile errors
"Windows cannot locate the server copy of your roaming profile" · "Windows cannot
update your roaming profile". Related Topics ...
http://www.chicagotech.net/winissues...ngprofile0.htm

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Joe Hernandez" <(E-Mail Removed)> wrote in message news:B6772E5C-6299-426F-B471-(E-Mail Removed)...
Hello,

Let me give you a quick reference of the problems that I am having.

We have 3 Dell servers. One is our PDC one is file server and the third
server is running ProjectWebAccess. All servers are running server 2003.

It seems that since we started to use Microsoft server 2003. We have
inherited the problems of: "Windows cannot locate the server copy of your
roaming profile"

I have been tryiing to solve this issue for the past year and 1/2.

We recently aquired the new Dell server 2800 that is also running server
2003 and project web access.
What I have been able to notice that I have 3 servers is that the file
server and projectwebaccess is that we loose connection to both this servers
at different times of the day. It hasnt been too much of a deal to have to
re-start computers around the office 5 to 6 times a day to be able and load
roaming profiles, but now that we are using one server for timecards, that
just cant happen, employees need to fill out their timecards, and project
managers need to be able to load their projects. But the connection to the
servers brake, it seems most times at the same time.

I had already posted this problem here before and was given this article to
read and work with, but it didnt solved my problem.
http://support.microsoft.com/kb/898060/

My file server has service pack 1 installed, I have installed the "Hotfix"
and it didnot solve the issue.

The server running ProjectWebAccess after reading the above articles and
several bumps on my head from hitting it on the wall. I erased the server,
did not installed server 2003 service pack one, re-installed everything that
is needed for ProjectWebAccess and I am still having the same problem.Keep
loosing connection for up to 1/2 hour at the time
I have also uninstalled KB893066 from my XP PRO desktop.

Please help me,

your truly,

Joe Hernandez
UPDATE: Oliver O'Boyle sugested

The issue is probably related to lack of connectivity to your Active
Directory Forest.

I would focus mostly on the server that is acting as your domain controller.
Ideallly, you should have 2 DCs in a network anyway. This is for redundancy.
If you are able to do this, I recommend it. If not, then you risk losing
your AD, and will be more prone to problems like this.

Just out of curiosity though, have you tried replacing the ethernet cable to
your DC? Have you tried using a different switch port (if you are using a
hub, you could be hacing other issues as well).

Oliver

--------------I dont think its the domain controller, when we go
authenticate we receive the message "windows cannot locate your roaming
profile....." but what is interesting is that even though we are working with
a temp profile I can still go the file server and access only the folders
that I have rights to, same with the rest of the staff, so we are being
granted permision, and 2 other servers become unavailable.

Robert

Thanks for your answer.

Its not a VPN issue, the problem is the servers run fine for most of the
day, and no one has issues pulling out the projectwebaccess page or get in
the file server. there are few times a day when all of the sudden I cannot
open the projectserver main page or access files to the file server. but I go
to the actual servers I can logon to projectwebaccess or look into the files
and folders of the file server. So this tells me the services are still
running, can edit create and do whatever I want with the server, it is just
those few times that we cant, it seems the lose of connection happens for up
to one hour, and then without restarting servers or rebooting anything all of
the sudden life is great, everyone can access anything they want.
Interestingly enought when this happens its does not happens company wide,
sometimes my IT side kick will be able to logon to projectwebaccess or to the
file server and I cant and few other people in the company same thing.
Very weird

Thanks

Joe Hernandez

"Robert L [MS-MVP]" wrote:

> It could be the name resolution issue. what do you receive if you using net view \\servername? Or check this link,
>
> roaming profile errors
> "Windows cannot locate the server copy of your roaming profile" · "Windows cannot
> update your roaming profile". Related Topics ...
> http://www.chicagotech.net/winissues...ngprofile0.htm
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "Joe Hernandez" <(E-Mail Removed)> wrote in message news:B6772E5C-6299-426F-B471-(E-Mail Removed)...
> Hello,
>
> Let me give you a quick reference of the problems that I am having.
>
> We have 3 Dell servers. One is our PDC one is file server and the third
> server is running ProjectWebAccess. All servers are running server 2003.
>
> It seems that since we started to use Microsoft server 2003. We have
> inherited the problems of: "Windows cannot locate the server copy of your
> roaming profile"
>
> I have been tryiing to solve this issue for the past year and 1/2.
>
> We recently aquired the new Dell server 2800 that is also running server
> 2003 and project web access.
> What I have been able to notice that I have 3 servers is that the file
> server and projectwebaccess is that we loose connection to both this servers
> at different times of the day. It hasnt been too much of a deal to have to
> re-start computers around the office 5 to 6 times a day to be able and load
> roaming profiles, but now that we are using one server for timecards, that
> just cant happen, employees need to fill out their timecards, and project
> managers need to be able to load their projects. But the connection to the
> servers brake, it seems most times at the same time.
>
> I had already posted this problem here before and was given this article to
> read and work with, but it didnt solved my problem.
> http://support.microsoft.com/kb/898060/
>
> My file server has service pack 1 installed, I have installed the "Hotfix"
> and it didnot solve the issue.
>
> The server running ProjectWebAccess after reading the above articles and
> several bumps on my head from hitting it on the wall. I erased the server,
> did not installed server 2003 service pack one, re-installed everything that
> is needed for ProjectWebAccess and I am still having the same problem.Keep
> loosing connection for up to 1/2 hour at the time
> I have also uninstalled KB893066 from my XP PRO desktop.
>
> Please help me,
>
> your truly,
>
> Joe Hernandez
> UPDATE: Oliver O'Boyle sugested
>
> The issue is probably related to lack of connectivity to your Active
> Directory Forest.
>
> I would focus mostly on the server that is acting as your domain controller.
> Ideallly, you should have 2 DCs in a network anyway. This is for redundancy.
> If you are able to do this, I recommend it. If not, then you risk losing
> your AD, and will be more prone to problems like this.
>
> Just out of curiosity though, have you tried replacing the ethernet cable to
> your DC? Have you tried using a different switch port (if you are using a
> hub, you could be hacing other issues as well).
>
> Oliver
>
> --------------I dont think its the domain controller, when we go
> authenticate we receive the message "windows cannot locate your roaming
> profile....." but what is interesting is that even though we are working with
> a temp profile I can still go the file server and access only the folders
> that I have rights to, same with the rest of the staff, so we are being
> granted permision, and 2 other servers become unavailable