Lanwench
Fri Mar 28 08:31:36 PDT 2008
Nick <Nick@discussions.microsoft.com> wrote:
> Hi
>
> Thanks for the response.
>
> This was a hurried post, as I'm not currently at the network location.
> I will check the Events log.
> I can tell you that when for example I try to view the events log of
> the client PC from the Server, I get the following message:
> "Unable to Connect to the Computer ****. The error was The network
> path was not found"
>
> I can ping the client from the server though, and vice verser.
How was this PC joined to the domain? Is it in the correct SBS OU in ADUC?
>
> Doesn't seem to effect the general running of the day to day usage,
> but as mentioned, the Company Web will not show on the client PC (I
> get the standard "Internet Explorer cannot display the webpage
> etc.."), and the Roaming Profiles are not working. (Checked the
> setting for the Roaming Profile setup, and all is consistent with the
> other client settings)
Make sure your DNS settings are correct and specify only the internal/SBS
server IP, no public IPs. Also, the primary DNS suffix mustmatch your AD
domain name.
You ought to have DHCP running on the SBS box....
>
> As a last resort, I may just rebuild the client PC and start from
> scratch., as recent new installations on the network have all been ok.
>
> I'll investigate the Event Log for some clues, and get back with the
> results.
>
> Thanks
Sure. Make sure this PC has SP2 and all other patches. Check rsop.msc
output.
My roaming profiles boilerplate is below, just in case it helps.
>
********************
General tips:
1. Set up a share on the server. For example - d:\profiles, shared as
profiles$ to make it hidden from browsing. Make sure this share is *not* set
to allow offline files/caching! (that's on by default - disable it)
2. Make sure the share permissions on profiles$ indicate everyone=full
control. Set the NTFS security to administrators, system, and users=full
control.
3. In the users' ADUC properties, specify \\server\profiles$\%username% in
the profiles field
4. Have each user log into the domain once - if this is an existing user
with a profile you wish to keep, have them log in at their usual
workstationand log out. The profile is now roaming.
5. If you want the administrators group to automatically have permissions to
the profiles folders, you'll need to make the appropriate change in group
policy. Look in computer configuration/administrative templates/system/user
profiles - there's an option to add administrators group to the roaming
profiles permissions. Do this *before* the users' roaming profile folders
are created - it isn't retroactive.
********************
Notes:
Make sure users understand that they should not log into multiple computers
at the same time when they have roaming profiles (unless you make the
profiles mandatory by renaming ntuser.dat to ntuser.man so they can't change
them, which has major disadvantages),. Explain that the 'last one out wins'
when it comes to uploading the final, changed copy of the profile. If you
want to restrict multiple simultaneous network logins, look at LimitLogon
(too much overhead for me), or this:
http://www.jsifaq.com/SF/Tips/Tip.aspx?id=8768
********************
Keep your profiles TINY. Via group policy, you should be redirecting My
Documents (at the very least) - to a subfolder of the user's home directory
or user folder. Also consider redirecting Desktop & Application Data
similarly..... so the user will end up with:
\\server\users\%username%\My Documents,
\\server\users\%username%\Desktop,
\\server\users\%username%\Application Data.
[Alternatively, just manually re-target My Documents to
\\server\users\%username% (this is not optimal, however!)]
You should use folder redirection even without roaming profiles, but it's
especially critical if you *are* using them.
If you aren't going to also redirect the desktop using policies, tell users
that they are not to store any files on the desktop or you will beat them
with a
stick. Big profile=slow login/logout, and possible profile corruption.
********************
Note that user profiles are not compatible between different OS versions,
even between W2k/XP. Keep all your computers. Keep your workstations as
identical as possible - meaning, OS version is the same, SP level is the
same, app load is (as much as possible) the same.
*********************
If you also have Terminal Services users, make sure you set up a different
TS profile path for them in their ADUC properties - e.g.,
\\server\tsprofiles$\%username%
********************
Do not let people store any data locally - all data belongs on the server.
********************
The User Profile Hive Cleanup Utility should be running on all your
computers. You can download it here:
http://www.microsoft.com/downloads/details.aspx?familyid=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en
********************
Roaming profile & folder redirection article -
http://www.windowsnetworking.com/articles_tutorials/Profile-Folder-Redirection-Windows-Server-2003.html
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Nick <Nick@discussions.microsoft.com> wrote:
>>> I have a small network of 8 computers connected to Windows 2003 SBS.
>>> All Client PC's are running XP Pro.
>>>
>>> One of the client Pc's is able to log in to the network, but cannot
>>> connect to the "Company Web" page. I've also noticed that from the
>>> server, I can't connect to the "Event Viewer", and other services
>>> directly to the problematic PC.
>>> The Roaming Profile also doesn't transfer from this particular PC
>>> and to the Server.
>>>
>>> Although I can view all the shares available on the Server from the
>>> client PC, there is some sort of connectivity problem. I have
>>> checked the Firewall settings, and that seems fine.
>>>
>>> Any help\guidance would be appreciated.
>>>
>>> Thanks!
>>
>> Hi - when you post, it helps if you post exact error messages. Also,
>> look up your event log errors at www.eventid.net.
>> A connectivity problem from client to server will not be a Windows
>> firewall problem on the client, as that blocks only inbound traffic.