Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > Windows Small Business Server > 2000 Can't see SB server

Reply
Thread Tools Display Modes

2000 Can't see SB server

 
 
Bitbob
Guest
Posts: n/a

 
      08-12-2005
I am running an SBS2003 server and about 25 computers most of which are XP
installs. The xp installs work fine when I set up users and outlook 2003. The
2000 machines see the SBS server and can access it but when I try to set up
Outlook 2003 for a user that is logged onto the 2000 machine it gets just so
far and then displays an error message that it cannot find the user folders
on the SBS server? The installation fails at this point. The two 2000
machines I need to set up respond in an identical fashion during an outlook
2003 install. Any Ideas??????????????
 
Reply With Quote
 
 
 
 
Lanwench [MVP - Exchange]
Guest
Posts: n/a

 
      08-12-2005


In news:3ABC022A-09CE-4F0D-95A5-,
Bitbob <> typed:
> I am running an SBS2003 server and about 25 computers most of which
> are XP installs. The xp installs work fine when I set up users and
> outlook 2003. The 2000 machines see the SBS server and can access it
> but when I try to set up Outlook 2003 for a user that is logged onto
> the 2000 machine it gets just so far and then displays an error
> message that it cannot find the user folders on the SBS server? The
> installation fails at this point. The two 2000 machines I need to set
> up respond in an identical fashion during an outlook 2003 install.
> Any Ideas??????????????


How did you add this computer to the domain, and is it identical in terms of
DNS config to the XP box that works? Have you checked the event logs on the
clients? Are they both fully patched (Windows and Office) ?

Also, don't use roaming profiles if you have mixed client OS versions. Not
sure if that's relevant.


 
Reply With Quote
 
Bitbob
Guest
Posts: n/a

 
      08-13-2005
I used the add computer wizard in sbs to add the computer. The DNS is set to
the sbs server. Both are up to date with service packs. No roaming profiles.
Other ideas?

"Lanwench [MVP - Exchange]" wrote:

>
>
> In news:3ABC022A-09CE-4F0D-95A5-,
> Bitbob <> typed:
> > I am running an SBS2003 server and about 25 computers most of which
> > are XP installs. The xp installs work fine when I set up users and
> > outlook 2003. The 2000 machines see the SBS server and can access it
> > but when I try to set up Outlook 2003 for a user that is logged onto
> > the 2000 machine it gets just so far and then displays an error
> > message that it cannot find the user folders on the SBS server? The
> > installation fails at this point. The two 2000 machines I need to set
> > up respond in an identical fashion during an outlook 2003 install.
> > Any Ideas??????????????

>
> How did you add this computer to the domain, and is it identical in terms of
> DNS config to the XP box that works? Have you checked the event logs on the
> clients? Are they both fully patched (Windows and Office) ?
>
> Also, don't use roaming profiles if you have mixed client OS versions. Not
> sure if that's relevant.
>
>
>

 
Reply With Quote
 
Lanwench [MVP - Exchange]
Guest
Posts: n/a

 
      08-13-2005


In news:32558E2F-DD25-4731-839B-,
Bitbob <> typed:
> I used the add computer wizard in sbs to add the computer. The DNS is
> set to the sbs server. Both are up to date with service packs. No
> roaming profiles. Other ideas?


Delete and recreate the Outlook profile on each, and see if it works.

>
> "Lanwench [MVP - Exchange]" wrote:
>
>>
>>
>> In news:3ABC022A-09CE-4F0D-95A5-,
>> Bitbob <> typed:
>>> I am running an SBS2003 server and about 25 computers most of which
>>> are XP installs. The xp installs work fine when I set up users and
>>> outlook 2003. The 2000 machines see the SBS server and can access it
>>> but when I try to set up Outlook 2003 for a user that is logged onto
>>> the 2000 machine it gets just so far and then displays an error
>>> message that it cannot find the user folders on the SBS server? The
>>> installation fails at this point. The two 2000 machines I need to
>>> set up respond in an identical fashion during an outlook 2003
>>> install. Any Ideas??????????????

>>
>> How did you add this computer to the domain, and is it identical in
>> terms of DNS config to the XP box that works? Have you checked the
>> event logs on the clients? Are they both fully patched (Windows and
>> Office) ?
>>
>> Also, don't use roaming profiles if you have mixed client OS
>> versions. Not sure if that's relevant.



 
Reply With Quote
 
Bitbob
Guest
Posts: n/a

 
      08-13-2005
Already tried that several times !!

"Lanwench [MVP - Exchange]" wrote:

>
>
> In news:32558E2F-DD25-4731-839B-,
> Bitbob <> typed:
> > I used the add computer wizard in sbs to add the computer. The DNS is
> > set to the sbs server. Both are up to date with service packs. No
> > roaming profiles. Other ideas?

>
> Delete and recreate the Outlook profile on each, and see if it works.
>
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >>
> >>
> >> In news:3ABC022A-09CE-4F0D-95A5-,
> >> Bitbob <> typed:
> >>> I am running an SBS2003 server and about 25 computers most of which
> >>> are XP installs. The xp installs work fine when I set up users and
> >>> outlook 2003. The 2000 machines see the SBS server and can access it
> >>> but when I try to set up Outlook 2003 for a user that is logged onto
> >>> the 2000 machine it gets just so far and then displays an error
> >>> message that it cannot find the user folders on the SBS server? The
> >>> installation fails at this point. The two 2000 machines I need to
> >>> set up respond in an identical fashion during an outlook 2003
> >>> install. Any Ideas??????????????
> >>
> >> How did you add this computer to the domain, and is it identical in
> >> terms of DNS config to the XP box that works? Have you checked the
> >> event logs on the clients? Are they both fully patched (Windows and
> >> Office) ?
> >>
> >> Also, don't use roaming profiles if you have mixed client OS
> >> versions. Not sure if that's relevant.

>
>
>

 
Reply With Quote
 
Lanwench [MVP - Exchange]
Guest
Posts: n/a

 
      08-13-2005


In news:76281FED-4D71-4A1E-BD01-,
Bitbob <> typed:
> Already tried that several times !!
>

Please post the exact steps you took, and the exact error message you get.

> "Lanwench [MVP - Exchange]" wrote:
>
>>
>>
>> In news:32558E2F-DD25-4731-839B-,
>> Bitbob <> typed:
>>> I used the add computer wizard in sbs to add the computer. The DNS
>>> is set to the sbs server. Both are up to date with service packs. No
>>> roaming profiles. Other ideas?

>>
>> Delete and recreate the Outlook profile on each, and see if it works.
>>
>>>
>>> "Lanwench [MVP - Exchange]" wrote:
>>>
>>>>
>>>>
>>>> In news:3ABC022A-09CE-4F0D-95A5-,
>>>> Bitbob <> typed:
>>>>> I am running an SBS2003 server and about 25 computers most of
>>>>> which are XP installs. The xp installs work fine when I set up
>>>>> users and outlook 2003. The 2000 machines see the SBS server and
>>>>> can access it but when I try to set up Outlook 2003 for a user
>>>>> that is logged onto the 2000 machine it gets just so far and then
>>>>> displays an error message that it cannot find the user folders on
>>>>> the SBS server? The installation fails at this point. The two
>>>>> 2000 machines I need to set up respond in an identical fashion
>>>>> during an outlook 2003 install. Any Ideas??????????????
>>>>
>>>> How did you add this computer to the domain, and is it identical in
>>>> terms of DNS config to the XP box that works? Have you checked the
>>>> event logs on the clients? Are they both fully patched (Windows and
>>>> Office) ?
>>>>
>>>> Also, don't use roaming profiles if you have mixed client OS
>>>> versions. Not sure if that's relevant.



 
Reply With Quote
 
Bitbob
Guest
Posts: n/a

 
      08-16-2005
Lanwrench: To install the outlook client from sbs we use the wizard to send
out the install startup on the 2000 client and the first user to log on
follows the prompts to set up outlook for his profile. The install gets to
the point where it goes out to check for the user profile on the sb-server
and returns with an error message that it cannot find the users folder on the
server{which is where it is supposed to be} and thus cannot continue with the
outlook install. The 2000 client was install using the install computer
wizard and appears in the domain list of computers and the user is listed in
the users list in the users folder. Do you need the blow by blow of the 2003
install or the sbs client software wizard? Thanks

"Lanwench [MVP - Exchange]" wrote:

>
>
> In news:76281FED-4D71-4A1E-BD01-,
> Bitbob <> typed:
> > Already tried that several times !!
> >

> Please post the exact steps you took, and the exact error message you get.
>
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >>
> >>
> >> In news:32558E2F-DD25-4731-839B-,
> >> Bitbob <> typed:
> >>> I used the add computer wizard in sbs to add the computer. The DNS
> >>> is set to the sbs server. Both are up to date with service packs. No
> >>> roaming profiles. Other ideas?
> >>
> >> Delete and recreate the Outlook profile on each, and see if it works.
> >>
> >>>
> >>> "Lanwench [MVP - Exchange]" wrote:
> >>>
> >>>>
> >>>>
> >>>> In news:3ABC022A-09CE-4F0D-95A5-,
> >>>> Bitbob <> typed:
> >>>>> I am running an SBS2003 server and about 25 computers most of
> >>>>> which are XP installs. The xp installs work fine when I set up
> >>>>> users and outlook 2003. The 2000 machines see the SBS server and
> >>>>> can access it but when I try to set up Outlook 2003 for a user
> >>>>> that is logged onto the 2000 machine it gets just so far and then
> >>>>> displays an error message that it cannot find the user folders on
> >>>>> the SBS server? The installation fails at this point. The two
> >>>>> 2000 machines I need to set up respond in an identical fashion
> >>>>> during an outlook 2003 install. Any Ideas??????????????
> >>>>
> >>>> How did you add this computer to the domain, and is it identical in
> >>>> terms of DNS config to the XP box that works? Have you checked the
> >>>> event logs on the clients? Are they both fully patched (Windows and
> >>>> Office) ?
> >>>>
> >>>> Also, don't use roaming profiles if you have mixed client OS
> >>>> versions. Not sure if that's relevant.

>
>
>

 
Reply With Quote
 
Lanwench [MVP - Exchange]
Guest
Posts: n/a

 
      08-17-2005


In news:64395CBE-2F29-48A1-85EF-,
Bitbob <> typed:
> Lanwrench: To install the outlook client from sbs we use the wizard
> to send out the install startup on the 2000 client and the first user
> to log on follows the prompts to set up outlook for his profile. The
> install gets to the point where it goes out to check for the user
> profile on the sb-server and returns with an error message that it
> cannot find the users folder on the server{which is where it is
> supposed to be} and thus cannot continue with the outlook install.
> The 2000 client was install using the install computer wizard and
> appears in the domain list of computers and the user is listed in the
> users list in the users folder. Do you need the blow by blow of the
> 2003 install or the sbs client software wizard? Thanks


No, that should be enough. Did you apply all Windows updates & Office 2003
patches (SP1, etc)?
Also - can you can ping the Exchange server by its NetBIOS name and get a
reply in the format of the FQDN, indicating that your query was resolved via
DNS?

I usually run all apps once as an admin, myself.
Might try to temporarily put Domain Users in the local administrators group,
log in as a user, and delete / recreate the profile. Do this in Control
Panel | Mail...make sure all you have is the Exchange server in the profile.

Also - event log errors on the client might help, if all this fails.

>
> "Lanwench [MVP - Exchange]" wrote:
>
>>
>>
>> In news:76281FED-4D71-4A1E-BD01-,
>> Bitbob <> typed:
>>> Already tried that several times !!
>>>

>> Please post the exact steps you took, and the exact error message
>> you get.
>>
>>> "Lanwench [MVP - Exchange]" wrote:
>>>
>>>>
>>>>
>>>> In news:32558E2F-DD25-4731-839B-,
>>>> Bitbob <> typed:
>>>>> I used the add computer wizard in sbs to add the computer. The DNS
>>>>> is set to the sbs server. Both are up to date with service packs.
>>>>> No roaming profiles. Other ideas?
>>>>
>>>> Delete and recreate the Outlook profile on each, and see if it
>>>> works.
>>>>
>>>>>
>>>>> "Lanwench [MVP - Exchange]" wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> In news:3ABC022A-09CE-4F0D-95A5-,
>>>>>> Bitbob <> typed:
>>>>>>> I am running an SBS2003 server and about 25 computers most of
>>>>>>> which are XP installs. The xp installs work fine when I set up
>>>>>>> users and outlook 2003. The 2000 machines see the SBS server and
>>>>>>> can access it but when I try to set up Outlook 2003 for a user
>>>>>>> that is logged onto the 2000 machine it gets just so far and
>>>>>>> then displays an error message that it cannot find the user
>>>>>>> folders on the SBS server? The installation fails at this
>>>>>>> point. The two 2000 machines I need to set up respond in an
>>>>>>> identical fashion during an outlook 2003 install. Any
>>>>>>> Ideas??????????????
>>>>>>
>>>>>> How did you add this computer to the domain, and is it identical
>>>>>> in terms of DNS config to the XP box that works? Have you
>>>>>> checked the event logs on the clients? Are they both fully
>>>>>> patched (Windows and Office) ?
>>>>>>
>>>>>> Also, don't use roaming profiles if you have mixed client OS
>>>>>> versions. Not sure if that's relevant.



 
Reply With Quote
 
Bitbob
Guest
Posts: n/a

 
      08-22-2005
Well we have finally tried everything you suggested to no avail. But we did
find a lot of prblems in the Windows2000 logs---

ype Date Time Source Category Event User Computer
Information 8/22/2005 9:29:28 AM Windows Update Agent Installation
19 N/A FUJI-SERVER
Error 8/22/2005 8:40:20 AM Netlogon None 5788 N/A FUJI-SERVER
Error 8/22/2005 8:40:20 AM Netlogon None 5789 N/A FUJI-SERVER
Warning 8/22/2005 8:17:07 AM Srv None 2013 N/A FUJI-SERVER
Error 8/22/2005 8:12:14 AM Netlogon None 5719 N/A FUJI-SERVER
Warning 8/22/2005 8:12:08 AM MrxSmb None 3034 N/A FUJI-SERVER
Warning 8/22/2005 8:12:07 AM MrxSmb None 3034 N/A FUJI-SERVER
Information 8/22/2005 8:10:42 AM Tcpip None 4201 N/A FUJI-SERVER
Information 8/22/2005 8:10:30 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/22/2005 8:10:30 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/22/2005 8:10:30 AM nvatabus None 2 N/A FUJI-SERVER
Error 8/22/2005 8:11:54 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/22/2005 8:11:54 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/22/2005 8:11:54 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/22/2005 8:11:54 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/22/2005 8:11:48 AM eventlog None 6005 N/A FUJI-SERVER
Information 8/22/2005 8:11:48 AM eventlog None 6009 N/A FUJI-SERVER
Error 8/22/2005 8:11:54 AM Service Control Manager None 7000 N/A FUJI-SERVER
Warning 8/22/2005 6:47:16 AM Srv None 2013 N/A FUJI-SERVER
Error 8/22/2005 6:45:28 AM aic78xx None 15 N/A FUJI-SERVER
Information 8/22/2005 6:42:00 AM Tcpip None 4201 N/A FUJI-SERVER
Information 8/22/2005 6:41:48 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/22/2005 6:41:48 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/22/2005 6:41:48 AM nvatabus None 2 N/A FUJI-SERVER
Error 8/22/2005 6:42:16 AM Service Control Manager None 7026 N/A FUJI-SERVER
Error 8/22/2005 6:42:08 AM Service Control Manager None 7001 N/A FUJI-SERVER
Error 8/22/2005 6:42:07 AM Service Control Manager None 7001 N/A FUJI-SERVER
Error 8/22/2005 6:42:07 AM Service Control Manager None 7024 N/A FUJI-SERVER
Error 8/22/2005 6:42:07 AM Workstation None 5727 N/A FUJI-SERVER
Error 8/22/2005 6:42:07 AM Workstation None 5727 N/A FUJI-SERVER
Error 8/22/2005 6:42:07 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/22/2005 6:42:07 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/22/2005 6:42:07 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/22/2005 6:42:07 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/22/2005 6:42:01 AM eventlog None 6005 N/A FUJI-SERVER
Information 8/22/2005 6:42:01 AM eventlog None 6009 N/A FUJI-SERVER
Error 8/22/2005 6:42:07 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/20/2005 10:38:04 AM eventlog None 6006 N/A FUJI-SERVER
Warning 8/20/2005 8:38:37 AM Srv None 2013 N/A FUJI-SERVER
Information 8/20/2005 8:33:21 AM Tcpip None 4201 N/A FUJI-SERVER
Information 8/20/2005 8:33:09 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/20/2005 8:33:09 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/20/2005 8:33:09 AM nvatabus None 2 N/A FUJI-SERVER
Error 8/20/2005 8:33:33 AM Netlogon None 5788 N/A FUJI-SERVER
Error 8/20/2005 8:33:33 AM Netlogon None 5789 N/A FUJI-SERVER
Error 8/20/2005 8:33:28 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/20/2005 8:33:28 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/20/2005 8:33:28 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/20/2005 8:33:28 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/20/2005 8:33:22 AM eventlog None 6005 N/A FUJI-SERVER
Information 8/20/2005 8:33:22 AM eventlog None 6009 N/A FUJI-SERVER
Error 8/20/2005 8:33:28 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/19/2005 7:02:19 PM eventlog None 6006 N/A FUJI-SERVER
Error 8/19/2005 5:40:45 PM Netlogon None 5788 N/A FUJI-SERVER
Error 8/19/2005 5:40:45 PM Netlogon None 5789 N/A FUJI-SERVER
Error 8/19/2005 2:32:44 PM Netlogon None 5788 N/A FUJI-SERVER
Error 8/19/2005 2:32:44 PM Netlogon None 5789 N/A FUJI-SERVER
Warning 8/19/2005 12:26:36 PM Srv None 2013 N/A FUJI-SERVER
Error 8/19/2005 11:10:43 AM Netlogon None 5788 N/A FUJI-SERVER
Error 8/19/2005 11:10:43 AM Netlogon None 5789 N/A FUJI-SERVER
Error 8/19/2005 10:27:56 AM aic78xx None 15 N/A FUJI-SERVER
Error 8/19/2005 9:42:48 AM aic78xx None 15 N/A FUJI-SERVER
Information 8/19/2005 7:56:17 AM Tcpip None 4201 N/A FUJI-SERVER
Information 8/19/2005 7:56:05 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/19/2005 7:56:05 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/19/2005 7:56:05 AM nvatabus None 2 N/A FUJI-SERVER
Error 8/19/2005 7:56:29 AM Netlogon None 5788 N/A FUJI-SERVER
Error 8/19/2005 7:56:29 AM Netlogon None 5789 N/A FUJI-SERVER
Error 8/19/2005 7:56:24 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/19/2005 7:56:24 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/19/2005 7:56:24 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/19/2005 7:56:24 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/19/2005 7:56:18 AM eventlog None 6005 N/A FUJI-SERVER
Information 8/19/2005 7:56:18 AM eventlog None 6009 N/A FUJI-SERVER
Error 8/19/2005 7:56:24 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/19/2005 6:33:32 AM Tcpip None 4201 N/A FUJI-SERVER
Information 8/19/2005 6:33:20 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/19/2005 6:33:20 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/19/2005 6:33:20 AM nvatabus None 2 N/A FUJI-SERVER
Error 8/19/2005 6:33:43 AM Netlogon None 5788 N/A FUJI-SERVER
Error 8/19/2005 6:33:43 AM Netlogon None 5789 N/A FUJI-SERVER
Error 8/19/2005 6:33:38 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/19/2005 6:33:38 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/19/2005 6:33:38 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/19/2005 6:33:38 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/19/2005 6:33:32 AM eventlog None 6005 N/A FUJI-SERVER
Information 8/19/2005 6:33:32 AM eventlog None 6009 N/A FUJI-SERVER
Error 8/19/2005 6:33:38 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/18/2005 3:45:53 PM eventlog None 6006 N/A FUJI-SERVER
Error 8/18/2005 1:14:36 PM Netlogon None 5788 N/A FUJI-SERVER
Error 8/18/2005 1:14:36 PM Netlogon None 5789 N/A FUJI-SERVER
Error 8/18/2005 9:50:35 AM Netlogon None 5788 N/A FUJI-SERVER
Error 8/18/2005 9:50:35 AM Netlogon None 5789 N/A FUJI-SERVER
Information 8/18/2005 6:40:10 AM Tcpip None 4201 N/A FUJI-SERVER
Information 8/18/2005 6:39:58 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/18/2005 6:39:58 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/18/2005 6:39:58 AM nvatabus None 2 N/A FUJI-SERVER
Error 8/18/2005 6:40:21 AM Netlogon None 5788 N/A FUJI-SERVER
Error 8/18/2005 6:40:21 AM Netlogon None 5789 N/A FUJI-SERVER
Error 8/18/2005 6:40:16 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/18/2005 6:40:16 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/18/2005 6:40:16 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/18/2005 6:40:16 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/18/2005 6:40:10 AM eventlog None 6005 N/A FUJI-SERVER
Information 8/18/2005 6:40:10 AM eventlog None 6009 N/A FUJI-SERVER
Error 8/18/2005 6:40:16 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/17/2005 6:15:00 PM eventlog None 6006 N/A FUJI-SERVER
Error 8/17/2005 5:06:38 PM Netlogon None 5788 N/A FUJI-SERVER
Error 8/17/2005 5:06:38 PM Netlogon None 5789 N/A FUJI-SERVER
Error 8/17/2005 1:28:50 PM Netlogon None 5788 N/A FUJI-SERVER
Error 8/17/2005 1:28:50 PM Netlogon None 5789 N/A FUJI-SERVER
Information 8/17/2005 9:59:05 AM Tcpip None 4201 N/A FUJI-SERVER
Information 8/17/2005 9:58:53 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/17/2005 9:58:53 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/17/2005 9:58:53 AM nvatabus None 2 N/A FUJI-SERVER
Error 8/17/2005 9:59:20 AM Netlogon None 5788 N/A FUJI-SERVER
Error 8/17/2005 9:59:20 AM Netlogon None 5789 N/A FUJI-SERVER
Error 8/17/2005 9:59:12 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/17/2005 9:59:12 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/17/2005 9:59:12 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/17/2005 9:59:12 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/17/2005 9:59:06 AM eventlog None 6005 N/A FUJI-SERVER
Information 8/17/2005 9:59:06 AM eventlog None 6009 N/A FUJI-SERVER
Error 8/17/2005 9:59:12 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/17/2005 9:57:51 AM eventlog None 6006 N/A FUJI-SERVER
Information 8/17/2005 9:57:09 AM Tcpip None 4201 N/A FUJI-SERVER
Information 8/17/2005 9:56:57 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/17/2005 9:56:57 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/17/2005 9:56:57 AM nvatabus None 2 N/A FUJI-SERVER
Error 8/17/2005 9:57:21 AM Netlogon None 5788 N/A FUJI-SERVER
Error 8/17/2005 9:57:21 AM Netlogon None 5789 N/A FUJI-SERVER
Error 8/17/2005 9:57:16 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/17/2005 9:57:16 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/17/2005 9:57:16 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/17/2005 9:57:16 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/17/2005 9:57:10 AM eventlog None 6005 N/A FUJI-SERVER
Information 8/17/2005 9:57:10 AM eventlog None 6009 N/A FUJI-SERVER
Error 8/17/2005 9:57:16 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/17/2005 9:55:47 AM eventlog None 6006 N/A FUJI-SERVER
Error 8/17/2005 9:55:28 AM Netlogon None 5788 N/A FUJI-SERVER
Error 8/17/2005 9:55:28 AM Netlogon None 5789 N/A FUJI-SERVER
Information 8/17/2005 9:27:56 AM Tcpip None 4201 N/A FUJI-SERVER
Information 8/17/2005 9:27:44 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/17/2005 9:27:44 AM nvatabus None 2 N/A FUJI-SERVER
Information 8/17/2005 9:27:44 AM nvatabus None 2 N/A FUJI-SERVER
Error 8/17/2005 9:28:03 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/17/2005 9:28:03 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/17/2005 9:28:03 AM Service Control Manager None 7000 N/A FUJI-SERVER
Error 8/17/2005 9:28:03 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/17/2005 9:27:57 AM eventlog None 6005 N/A FUJI-SERVER
Information 8/17/2005 9:27:57 AM eventlog None 6009 N/A FUJI-SERVER
Error 8/17/2005 9:28:03 AM Service Control Manager None 7000 N/A FUJI-SERVER
Information 8/17/2005 9:26:55 AM eventlog None 6006 N/A FUJI_SERVER
Warning 8/17/2005 9:26:12 AM W32Time None 11 N/A FUJI_SERVER
Error 8/17/2005 9:26:07 AM Netlogon None 5788 N/A FUJI_SERVER
Error 8/17/2005 9:26:07 AM Netlogon None 5789 N/A FUJI_SERVER
Warning 8/17/2005 8:18:54 AM Srv None 2013 N/A FUJI_SERVER
Information 8/17/2005 8:13:59 AM W32Time None 593 N/A FUJI_SERVER
Error 8/17/2005 8:13:50 AM Netlogon None 5788 N/A FUJI_SERVER
Error 8/17/2005 8:13:50 AM Netlogon None 5789 N/A FUJI_SERVER
Error 8/17/2005 8:13:45 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/17/2005 8:13:45 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/17/2005 8:13:45 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/17/2005 8:13:45 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/17/2005 8:13:45 AM Service Control Manager None 7000 N/A FUJI_SERVER
Information 8/17/2005 8:12:53 AM Tcpip None 4201 N/A FUJI_SERVER
Information 8/17/2005 8:12:41 AM nvatabus None 2 N/A FUJI_SERVER
Information 8/17/2005 8:12:41 AM nvatabus None 2 N/A FUJI_SERVER
Information 8/17/2005 8:13:39 AM eventlog None 6005 N/A FUJI_SERVER
Information 8/17/2005 8:13:39 AM eventlog None 6009 N/A FUJI_SERVER
Information 8/17/2005 8:12:41 AM nvatabus None 2 N/A FUJI_SERVER
Warning 8/17/2005 7:04:03 AM Srv None 2013 N/A FUJI_SERVER
Information 8/17/2005 6:59:08 AM W32Time None 593 N/A FUJI_SERVER
Information 8/17/2005 6:58:47 AM Tcpip None 4201 N/A FUJI_SERVER
Information 8/17/2005 6:58:35 AM nvatabus None 2 N/A FUJI_SERVER
Information 8/17/2005 6:58:35 AM nvatabus None 2 N/A FUJI_SERVER
Information 8/17/2005 6:58:35 AM nvatabus None 2 N/A FUJI_SERVER
Error 8/17/2005 6:58:59 AM Netlogon None 5788 N/A FUJI_SERVER
Error 8/17/2005 6:58:59 AM Netlogon None 5789 N/A FUJI_SERVER
Error 8/17/2005 6:58:54 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/17/2005 6:58:54 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/17/2005 6:58:54 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/17/2005 6:58:54 AM Service Control Manager None 7000 N/A FUJI_SERVER
Information 8/17/2005 6:58:48 AM eventlog None 6005 N/A FUJI_SERVER
Information 8/17/2005 6:58:48 AM eventlog None 6009 N/A FUJI_SERVER
Error 8/17/2005 6:58:54 AM Service Control Manager None 7000 N/A FUJI_SERVER
Information 8/17/2005 6:54:50 AM eventlog None 6006 N/A FUJI_SERVER
Information 8/17/2005 6:54:35 AM Windows Update Agent Installation
19 N/A FUJI_SERVER
Warning 8/17/2005 6:52:00 AM Srv None 2013 N/A FUJI_SERVER
Information 8/17/2005 6:51:48 AM Windows Update Agent Installation
19 N/A FUJI_SERVER
Information 8/17/2005 6:47:05 AM W32Time None 593 N/A FUJI_SERVER
Information 8/17/2005 6:46:44 AM Tcpip None 4201 N/A FUJI_SERVER
Information 8/17/2005 6:46:32 AM nvatabus None 2 N/A FUJI_SERVER
Information 8/17/2005 6:46:32 AM nvatabus None 2 N/A FUJI_SERVER
Information 8/17/2005 6:46:32 AM nvatabus None 2 N/A FUJI_SERVER
Error 8/17/2005 6:46:56 AM Netlogon None 5788 N/A FUJI_SERVER
Error 8/17/2005 6:46:56 AM Netlogon None 5789 N/A FUJI_SERVER
Error 8/17/2005 6:46:51 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/17/2005 6:46:51 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/17/2005 6:46:51 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/17/2005 6:46:51 AM Service Control Manager None 7000 N/A FUJI_SERVER
Information 8/17/2005 6:46:45 AM eventlog None 6005 N/A FUJI_SERVER
Information 8/17/2005 6:46:45 AM eventlog None 6009 N/A FUJI_SERVER
Error 8/17/2005 6:46:51 AM Service Control Manager None 7000 N/A FUJI_SERVER
Information 8/17/2005 6:42:47 AM eventlog None 6006 N/A FUJI_SERVER
Information 8/17/2005 6:42:18 AM Windows Update Agent Installation
19 N/A FUJI_SERVER
Information 8/17/2005 6:40:28 AM W32Time None 593 N/A FUJI_SERVER
Information 8/17/2005 6:40:07 AM Tcpip None 4201 N/A FUJI_SERVER
Information 8/17/2005 6:39:55 AM nvatabus None 2 N/A FUJI_SERVER
Information 8/17/2005 6:39:55 AM nvatabus None 2 N/A FUJI_SERVER
Information 8/17/2005 6:39:55 AM nvatabus None 2 N/A FUJI_SERVER
Error 8/17/2005 6:40:19 AM Netlogon None 5788 N/A FUJI_SERVER
Error 8/17/2005 6:40:19 AM Netlogon None 5789 N/A FUJI_SERVER
Error 8/17/2005 6:40:14 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/17/2005 6:40:14 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/17/2005 6:40:14 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/17/2005 6:40:14 AM Service Control Manager None 7000 N/A FUJI_SERVER
Information 8/17/2005 6:40:08 AM eventlog None 6005 N/A FUJI_SERVER
Information 8/17/2005 6:40:08 AM eventlog None 6009 N/A FUJI_SERVER
Error 8/17/2005 6:40:14 AM Service Control Manager None 7000 N/A FUJI_SERVER
Information 8/16/2005 6:29:02 PM eventlog None 6006 N/A FUJI_SERVER
Error 8/16/2005 4:40:35 PM Netlogon None 5788 N/A FUJI_SERVER
Error 8/16/2005 4:40:35 PM Netlogon None 5789 N/A FUJI_SERVER
Error 8/16/2005 12:59:35 PM Netlogon None 5788 N/A FUJI_SERVER
Error 8/16/2005 12:59:35 PM Netlogon None 5789 N/A FUJI_SERVER
Error 8/16/2005 9:48:35 AM Netlogon None 5788 N/A FUJI_SERVER
Error 8/16/2005 9:48:35 AM Netlogon None 5789 N/A FUJI_SERVER
Warning 8/16/2005 6:42:54 AM Srv None 2013 N/A FUJI_SERVER
Information 8/16/2005 6:37:57 AM W32Time None 593 N/A FUJI_SERVER
Information 8/16/2005 6:37:36 AM Tcpip None 4201 N/A FUJI_SERVER
Information 8/16/2005 6:37:24 AM nvatabus None 2 N/A FUJI_SERVER
Information 8/16/2005 6:37:24 AM nvatabus None 2 N/A FUJI_SERVER
Information 8/16/2005 6:37:24 AM nvatabus None 2 N/A FUJI_SERVER
Error 8/16/2005 6:37:48 AM Netlogon None 5788 N/A FUJI_SERVER
Error 8/16/2005 6:37:48 AM Netlogon None 5789 N/A FUJI_SERVER
Error 8/16/2005 6:37:43 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/16/2005 6:37:43 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/16/2005 6:37:43 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/16/2005 6:37:43 AM Service Control Manager None 7000 N/A FUJI_SERVER
Information 8/16/2005 6:37:37 AM eventlog None 6005 N/A FUJI_SERVER
Information 8/16/2005 6:37:37 AM eventlog None 6009 N/A FUJI_SERVER
Error 8/16/2005 6:37:43 AM Service Control Manager None 7000 N/A FUJI_SERVER
Information 8/15/2005 6:15:18 PM eventlog None 6006 N/A FUJI_SERVER
Error 8/15/2005 2:54:19 PM Netlogon None 5788 N/A FUJI_SERVER
Error 8/15/2005 2:54:19 PM Netlogon None 5789 N/A FUJI_SERVER
Warning 8/15/2005 11:48:06 AM Srv None 2013 N/A FUJI_SERVER
Information 8/15/2005 11:43:05 AM W32Time None 593 N/A FUJI_SERVER
Information 8/15/2005 11:42:45 AM Tcpip None 4201 N/A FUJI_SERVER
Information 8/15/2005 11:42:33 AM nvatabus None 2 N/A FUJI_SERVER
Information 8/15/2005 11:42:33 AM nvatabus None 2 N/A FUJI_SERVER
Information 8/15/2005 11:42:33 AM nvatabus None 2 N/A FUJI_SERVER
Error 8/15/2005 11:42:57 AM Netlogon None 5788 N/A FUJI_SERVER
Error 8/15/2005 11:42:57 AM Netlogon None 5789 N/A FUJI_SERVER
Error 8/15/2005 11:42:52 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/15/2005 11:42:52 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/15/2005 11:42:52 AM Service Control Manager None 7000 N/A FUJI_SERVER
Error 8/15/2005 11:42:52 AM Service Control Manager None 7000 N/A FUJI_SERVER
Information 8/15/2005 11:42:46 AM eventlog None 6005 N/A FUJI_SERVER
Information 8/15/2005 11:42:46 AM eventlog None 6009 N/A FUJI_SERVER
Error 8/15/2005 11:42:52 AM Service Control Manager None 7000 N/A FUJI_SERVER
Information 8/15/2005 11:36:48 AM eventlog None 6006 N/A FUJI_SERVER
Warning 8/15/2005 11:07:18 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:07:10 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:07:03 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:06:54 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:06:46 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:06:39 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:06:30 AM cdrom None 51 N/A FUJI_SERVER
Error 8/15/2005 11:06:23 AM cdrom None 7 N/A FUJI_SERVER
Warning 8/15/2005 11:06:20 AM cdrom None 51 N/A FUJI_SERVER
Error 8/15/2005 11:06:12 AM cdrom None 7 N/A FUJI_SERVER
Warning 8/15/2005 11:06:08 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:06:00 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:05:53 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:05:44 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:05:37 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:05:28 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:05:20 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:05:13 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:05:05 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:04:57 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:04:50 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:04:42 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:04:34 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:04:27 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:04:19 AM cdrom None 51 N/A FUJI_SERVER
Warning 8/15/2005 11:04:12 AM cdrom None 51 N/A FUJI_SERVER
Error 8/15/2005 10:59:49 AM Netlogon None 5788 N/A FUJI_SERVER
Error 8/15/2005 10:59:49 AM Netlogon None 5789 N/A FUJI_SERVER
Error 8/15/2005 8:45:16 AM Netlogon None 5788 N/A FUJI_SERVER
Error 8/15/2005 8:45:16 AM Netlogon None 5789 N/A FUJI_SERVER
Warning 8/15/2005 6:48:31 AM Srv None 2013 N/A FUJI_SERVER
Warning 8/15/2005 6:48:31 AM Srv None 2013 N/A FUJI_SERVER

As you can see there are a lot of errors associated with these machines!!!!

"Lanwench [MVP - Exchange]" wrote:

>
>
> In news:64395CBE-2F29-48A1-85EF-,
> Bitbob <> typed:
> > Lanwrench: To install the outlook client from sbs we use the wizard
> > to send out the install startup on the 2000 client and the first user
> > to log on follows the prompts to set up outlook for his profile. The
> > install gets to the point where it goes out to check for the user
> > profile on the sb-server and returns with an error message that it
> > cannot find the users folder on the server{which is where it is
> > supposed to be} and thus cannot continue with the outlook install.
> > The 2000 client was install using the install computer wizard and
> > appears in the domain list of computers and the user is listed in the
> > users list in the users folder. Do you need the blow by blow of the
> > 2003 install or the sbs client software wizard? Thanks

>
> No, that should be enough. Did you apply all Windows updates & Office 2003
> patches (SP1, etc)?
> Also - can you can ping the Exchange server by its NetBIOS name and get a
> reply in the format of the FQDN, indicating that your query was resolved via
> DNS?
>
> I usually run all apps once as an admin, myself.
> Might try to temporarily put Domain Users in the local administrators group,
> log in as a user, and delete / recreate the profile. Do this in Control
> Panel | Mail...make sure all you have is the Exchange server in the profile.
>
> Also - event log errors on the client might help, if all this fails.
>
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >>
> >>
> >> In news:76281FED-4D71-4A1E-BD01-,
> >> Bitbob <> typed:
> >>> Already tried that several times !!
> >>>
> >> Please post the exact steps you took, and the exact error message
> >> you get.
> >>
> >>> "Lanwench [MVP - Exchange]" wrote:
> >>>
> >>>>
> >>>>
> >>>> In news:32558E2F-DD25-4731-839B-,
> >>>> Bitbob <> typed:
> >>>>> I used the add computer wizard in sbs to add the computer. The DNS
> >>>>> is set to the sbs server. Both are up to date with service packs.
> >>>>> No roaming profiles. Other ideas?
> >>>>
> >>>> Delete and recreate the Outlook profile on each, and see if it
> >>>> works.
> >>>>
> >>>>>
> >>>>> "Lanwench [MVP - Exchange]" wrote:
> >>>>>
> >>>>>>
> >>>>>>
> >>>>>> In news:3ABC022A-09CE-4F0D-95A5-,
> >>>>>> Bitbob <> typed:
> >>>>>>> I am running an SBS2003 server and about 25 computers most of
> >>>>>>> which are XP installs. The xp installs work fine when I set up
> >>>>>>> users and outlook 2003. The 2000 machines see the SBS server and
> >>>>>>> can access it but when I try to set up Outlook 2003 for a user
> >>>>>>> that is logged onto the 2000 machine it gets just so far and
> >>>>>>> then displays an error message that it cannot find the user
> >>>>>>> folders on the SBS server? The installation fails at this
> >>>>>>> point. The two 2000 machines I need to set up respond in an
> >>>>>>> identical fashion during an outlook 2003 install. Any
> >>>>>>> Ideas??????????????
> >>>>>>
> >>>>>> How did you add this computer to the domain, and is it identical
> >>>>>> in terms of DNS config to the XP box that works? Have you
> >>>>>> checked the event logs on the clients? Are they both fully
> >>>>>> patched (Windows and Office) ?
> >>>>>>
> >>>>>> Also, don't use roaming profiles if you have mixed client OS
> >>>>>> versions. Not sure if that's relevant.

>
>
>

 
Reply With Quote
 
Lanwench [MVP - Exchange]
Guest
Posts: n/a

 
      08-24-2005

"Bitbob" <> wrote in message
news:667279BB-A4B0-4A21-8BFA-...
> Well we have finally tried everything you suggested to no avail. But we
> did
> find a lot of prblems in the Windows2000 logs---
>
> ype Date Time Source Category Event User Computer
> Information 8/22/2005 9:29:28 AM Windows Update Agent Installation
> 19 N/A FUJI-SERVER
> Error 8/22/2005 8:40:20 AM Netlogon None 5788 N/A FUJI-SERVER
> Error 8/22/2005 8:40:20 AM Netlogon None 5789 N/A FUJI-SERVER
> Warning 8/22/2005 8:17:07 AM Srv None 2013 N/A FUJI-SERVER
> Error 8/22/2005 8:12:14 AM Netlogon None 5719 N/A FUJI-SERVER

<snip>
> As you can see there are a lot of errors associated with these
> machines!!!!


Yep.
Check out www.eventid.net. The free access should suffice, although I do
recommend subscribing as you get more goodies.

>
> "Lanwench [MVP - Exchange]" wrote:
>
>>
>>
>> In news:64395CBE-2F29-48A1-85EF-,
>> Bitbob <> typed:
>> > Lanwrench: To install the outlook client from sbs we use the wizard
>> > to send out the install startup on the 2000 client and the first user
>> > to log on follows the prompts to set up outlook for his profile. The
>> > install gets to the point where it goes out to check for the user
>> > profile on the sb-server and returns with an error message that it
>> > cannot find the users folder on the server{which is where it is
>> > supposed to be} and thus cannot continue with the outlook install.
>> > The 2000 client was install using the install computer wizard and
>> > appears in the domain list of computers and the user is listed in the
>> > users list in the users folder. Do you need the blow by blow of the
>> > 2003 install or the sbs client software wizard? Thanks

>>
>> No, that should be enough. Did you apply all Windows updates & Office
>> 2003
>> patches (SP1, etc)?
>> Also - can you can ping the Exchange server by its NetBIOS name and get a
>> reply in the format of the FQDN, indicating that your query was resolved
>> via
>> DNS?
>>
>> I usually run all apps once as an admin, myself.
>> Might try to temporarily put Domain Users in the local administrators
>> group,
>> log in as a user, and delete / recreate the profile. Do this in Control
>> Panel | Mail...make sure all you have is the Exchange server in the
>> profile.
>>
>> Also - event log errors on the client might help, if all this fails.
>>
>> >
>> > "Lanwench [MVP - Exchange]" wrote:
>> >
>> >>
>> >>
>> >> In news:76281FED-4D71-4A1E-BD01-,
>> >> Bitbob <> typed:
>> >>> Already tried that several times !!
>> >>>
>> >> Please post the exact steps you took, and the exact error message
>> >> you get.
>> >>
>> >>> "Lanwench [MVP - Exchange]" wrote:
>> >>>
>> >>>>
>> >>>>
>> >>>> In news:32558E2F-DD25-4731-839B-,
>> >>>> Bitbob <> typed:
>> >>>>> I used the add computer wizard in sbs to add the computer. The DNS
>> >>>>> is set to the sbs server. Both are up to date with service packs.
>> >>>>> No roaming profiles. Other ideas?
>> >>>>
>> >>>> Delete and recreate the Outlook profile on each, and see if it
>> >>>> works.
>> >>>>
>> >>>>>
>> >>>>> "Lanwench [MVP - Exchange]" wrote:
>> >>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> In news:3ABC022A-09CE-4F0D-95A5-,
>> >>>>>> Bitbob <> typed:
>> >>>>>>> I am running an SBS2003 server and about 25 computers most of
>> >>>>>>> which are XP installs. The xp installs work fine when I set up
>> >>>>>>> users and outlook 2003. The 2000 machines see the SBS server and
>> >>>>>>> can access it but when I try to set up Outlook 2003 for a user
>> >>>>>>> that is logged onto the 2000 machine it gets just so far and
>> >>>>>>> then displays an error message that it cannot find the user
>> >>>>>>> folders on the SBS server? The installation fails at this
>> >>>>>>> point. The two 2000 machines I need to set up respond in an
>> >>>>>>> identical fashion during an outlook 2003 install. Any
>> >>>>>>> Ideas??????????????
>> >>>>>>
>> >>>>>> How did you add this computer to the domain, and is it identical
>> >>>>>> in terms of DNS config to the XP box that works? Have you
>> >>>>>> checked the event logs on the clients? Are they both fully
>> >>>>>> patched (Windows and Office) ?
>> >>>>>>
>> >>>>>> Also, don't use roaming profiles if you have mixed client OS
>> >>>>>> versions. Not sure if that's relevant.

>>
>>
>>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Web Hosting on a SBS2003 member server Charles Irwin Windows Small Business Server 15 12-27-2010 07:58 AM
windows 2003 Ent SP1 Server Crash Issues Will Owens Windows Server 2 03-03-2010 01:13 AM
fail to install the SP1 but n error in the log file!!! Jéjé Windows Small Business Server 5 05-23-2005 03:51 PM
upgrade windows 2000 server to sbs2k3 Pedro Ferreira aka Dundee Windows Small Business Server 4 01-18-2005 11:48 AM
Changing IP addresses SBS 2000 Network JeffM Windows Small Business Server 20 11-01-2004 02:31 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59