Roaming profiles only work on AD server???

[customgt]

Hello i got a SBS 2003 PDC.
I got a Win2k3 2003 server, that is not on the domain, but is on the same network.


I got a Win XP Pro computer that is on the SBS 2003 domain.

On the SBS, in AD i enter in the profile path \\win2k3server\Test

On the Win XP Pro i go to start/run/ \\win2k3server
It ask me for the user/pword, i enter it. I tnow has the key for that server saved.
I can read/write to the \Test folder from the client. All good.

When i logon/off it says the username/pword credentials are bad for the roaming profile and it doesnt sync.

Im at a loss here, ive tried everything I can think of. The win2k3server is actually going to be a Samba server. But i couldnt get it to work on that either, so I was trying to see if I could get it to work on anything, apparently not.
And I do not want it to be on the same domain as the SBS if possible.

Any ideas?

 

[customgt]

still havent figured this out

 

[lhuegele]

For the username are you entering it as "domain\username" or just using "username"?

Can you provide more information on what you are trying to accomplish?

 

[customgt]

Im just entering it as "username" because the win2k3 server is not on a domain.


Basicly we got a Win2k3 SBS PDC that all the computers log onto. We store our roaming profiles to this server. That all works great.

But what if I want to store the roaming profiles somewhere else. That is what im trying to accomplish.
And the computer that im trying to do this to is the Win2k3 standard server that is not on the domain.

 

[mrdenny]

The server that is hosting the roaming profiles should be a member of the domain so that domain credentials can be used. Otherwise any time a user changes there domain password they won't be able to access thier roaming profile until they change the password on that server as well.

What goal are you trying to reach by having it not be a member of the domain?

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[customgt]

Well im actually going to be storing them on a Linux Samba server. And I was going to try to do it without joining the Samba server to the domain.
The Samba server is at another location in another country where the other computers are at. The other location is connected via VPN.
It would be silly to sync the computers back to the other country. So I was going to have them save to the Samba server we built.

But i was just trying to do this at my location first with something not on the domain and i had a win2k3 standard server sitting here to try it on....

 

[mrdenny]

You'll want to add the Samba machine to the domain then to avoid the password change problem that I mentioned.

Do you have a domain controller there? If so it should be fairly easy to add it to the domain.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[customgt]

Yea our Win2k3 SBS is the PDC. Its in the USA.
The Samba is in another country but connected via VPN.

Ive read a few articles about joining a Samba to a windows domain. To be honost I have not joined a server to a domain before, only winxp pro clients....

 

[mrdenny]

Is there a DC in the remote office?

You'll have to google on how to add a Samba machine to the domain. I now just about nothing about linux.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[customgt]

no DC at the samba location.

I found a few docs on doing it. Ill have to have them put in another nic in the SAMBA as it has one with its own WAN IP not a LAN IP...

cool thanks for the help.