Re: Setting up client computers after SBS 2003 install

From: Les Connor [SBS Community Member - SBS MVP] (les.connor_at_DEL.cfive.ca)
Date: 01/21/05


Date: Fri, 21 Jan 2005 14:06:36 -0600

Roger,

Unfortunately you have dug yourself a hole here, and I'm not sure what the
best way out would be at this point. The root cause is that your network is
not configured correctly; this results in connectcomputer (and other things)
not working, which has caused you to bypass the wizards, which meahs that
you are not going to get the good stuff that SBS should be providing.

You have broken some dns rules, and are following some practices (such as
single nic, and using your router for DHCP) that just aren't in your best
interests. Is there any chance you can start over ? You can fix up what you
have, but it's a bit of a trek - and if you start things out on the right
foot and let SBS do it's thing it's sooooo easy :-).

Have a look at http://www.smallbizserver.net in the networking section, for
examples of how to set up your network.

I'd recommend two_nics_and_a_router; you already have everything except the
second nic, and that's a very minor investment to make towards a very
resilient system.

Note that you can go single nic, some recommend it in fact - (but not me).
If you elect to go the single nic method, one of the proponents of that
configuration will certainly assist you.

-- 
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
"roger" <rogersrd@tds.net> wrote in message 
news:uIndzz%23$EHA.960@TK2MSFTNGP10.phx.gbl...
> Well, I finally got these computers to be connected to the SBS 2003 domain
> name, I did it the old fashion way, went the the system properties instead
> of using the "wizard".  Now the only problem is:
> Now I log into the workstation using the network user name and domain 
> name.
> When I first did that, it created a new profile.  So then I logged in as
> administrator of both the workstation and the network user name so that I
> could copy the profile of the original user name to the profile of the new
> user name with the SBS 2003 domain.  Before we had no network.  I go into
> System --> user profiles -->  select a profile --> click on "copy to" -->
> click on "permitted to use" --> but it will not find the SBS2003 domain
> name, only the local user domain name.
> Got any ideas?
> Here is the IPCONFIG /ALL from the server:
> Windows IP Configuration
>   Host Name . . . . . . . . . . . . : srd-server
>   Primary Dns Suffix  . . . . . . . : SRD.local
>   Node Type . . . . . . . . . . . . : Unknown
>   IP Routing Enabled. . . . . . . . : Yes
>   WINS Proxy Enabled. . . . . . . . : Yes
>   DNS Suffix Search List. . . . . . : SRD.local
>
> Ethernet adapter Server Local Area Connection:
>   Connection-specific DNS Suffix  . :
>   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Adapter
>   Physical Address. . . . . . . . . : 00-30-48-73-C9-D8
>   DHCP Enabled. . . . . . . . . . . : No
>   IP Address. . . . . . . . . . . . : 192.168.1.2
>   Subnet Mask . . . . . . . . . . . : 255.255.255.0
>   Default Gateway . . . . . . . . . : 192.168.1.1
>   DNS Servers . . . . . . . . . . . : 204.246.1.20
>                                       204.70.128.1
>   Primary WINS Server . . . . . . . : 192.168.1.2
>
>
> And from the workstation
> Windows IP Configuration
>        Host Name . . . . . . . . . . . . : Jason
>        Primary Dns Suffix  . . . . . . . : SRD.local
>        Node Type . . . . . . . . . . . . : Mixed
>        IP Routing Enabled. . . . . . . . : No
>        WINS Proxy Enabled. . . . . . . . : No
>        DNS Suffix Search List. . . . . . : SRD.local
> Ethernet adapter Network Bridge (Network Bridge):
>        Connection-specific DNS Suffix  . :
>        Description . . . . . . . . . . . : MAC Bridge Miniport
>        Physical Address. . . . . . . . . : F2-34-FF-2F-F3-E6
>        Dhcp Enabled. . . . . . . . . . . : No
>        IP Address. . . . . . . . . . . . : 192.168.1.20
>        Subnet Mask . . . . . . . . . . . : 255.255.255.0
>        Default Gateway . . . . . . . . . : 192.168.1.1
>                                            192.168.1.2
>        DNS Servers . . . . . . . . . . . : 204.246.1.20
>                                            207.70.128.1
>
>
> "Roger" <cadmanroger@sbcglobal.net> wrote in message
> news:w6XHd.237$Wh2.235@fe06.lga...
>> I am in central time.  I will have these answers when I make it to that
>> office tomorrow at 7 am.  I will post then.
>> Thanks
>> Roger
>>
>> "Cris Hanna [SBS-MVP]" <crisnospamhanna@computingnospampossibilities.net>
>> wrote in message news:%23%23RTLjz$EHA.1340@TK2MSFTNGP10.phx.gbl...
>> > Roger
>> > We also need to see the IPconfig /all from the server and from
>> > workstations.
>> >
>> > --
>> > Cris Hanna [SBS - MVP]
>> > ---------------------------------------
>> > Please reply only to the newsgroup and not to me directly so that
> everyone
>> > can benefit from the information
>> > "Roger" <cadmanroger@sbcglobal.net> wrote in message
>> > news:etUHd.208$zZ7.87@fe06.lga...
>> >> Yes I have.
>> >> I have completed the "To Do List" on the server.  All users, 
>> >> mailboxes,
>> >> computer setups are done.
>> >> I am at a different location today, so I do not have access to the
> error
>> >> message that I was getting, but I am going to be there tomorrow to try
> to
>> >> figure out why the typical "http://(name of server)/connectcomputer is
>> >> not working.  I will post again if I cannot figure it out and give the
>> >> error message.
>> >>
>> >> Thanks
>> >> Roger
>> >>
>> >> "Cris Hanna [SBS-MVP]"
> <crisnospamhanna@computingnospampossibilities.net>
>> >> wrote in message news:ul3yOry$EHA.1404@TK2MSFTNGP11.phx.gbl...
>> >>> Have you created the users and computers using the wizards from the
>> >>> Server Management console??
>> >>>
>> >>> --
>> >>> Cris Hanna [SBS - MVP]
>> >>> ---------------------------------------
>> >>> Please reply only to the newsgroup and not to me directly so that
>> >>> everyone can benefit from the information
>> >>> "Roger" <cadmanroger@sbcglobal.net> wrote in message
>> >>> news:nqTHd.1054$Zw6.698@fe03.lga...
>> >>>>I have just finished setting up a 10-user SBS 2003 computer.  I have
>> >>>>above average knowledge on workstations but little on servers.
>> >>>>According to the help support from the software, I need to go to each
>> >>>>workstation, go into IE, and go to "http://(name of
>> >>>>server)/connectcomputer"
>> >>>> Then I click on the link and it will "try" to set up that
> workstation.
>> >>>> It tries to go thru the process but gives me an error.
>> >>>>
>> >>>> Does anybody have a procedure document that would be willing to 
>> >>>> share
>> >>>> on how to setup workstations using Windows XP Pro and connecting to 
>> >>>> a
>> >>>> SBS2003 server?
>> >>>>
>> >>>> Thanks in advance
>> >>>> Roger
>> >>>>
>> >>>
>> >>>
>> >>
>> >>
>> >
>> >
>>
>>
>
> 


Relevant Pages

  • RE: Slow login, network browsing on SBS 2003
    ... I understand that several workstations in your SBS ... domain are having trouble logging in the domain and access the network ... shares on the SBS Server. ... Let's perform a Clean Boot on the problematic workstation. ...
    (microsoft.public.windows.server.sbs)
  • Re: Small office Recomondations
    ... of SBS 2003 will work with Win9x machines, it's best to have either Win2K ... This may mean added $$$ for software/hardware for a total network ... NTBackup to do a nightly backup of the USB drive to the workstation hard ... saving data to the local hard drives). ...
    (microsoft.public.windows.server.sbs)
  • Re: Web Traffic by Hour
    ... "Jim Behning SBS MVP" wrote: ... Wireshark and watch what is happening. ... Best bet it to format the workstation. ... Wireshark is a network monitoring utility. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cliients Cannot ping or connect to new SBS 2003 Server
    ... Win2k3 SP2 but that seems very messy and may force a complete server rebuild. ... pinging one workstation from another? ... you may need to install Network Monitor on the ... See what SBS support is working on ...
    (microsoft.public.windows.server.sbs)
  • Re: For the AdaOS folks
    ... Mach's concept of thread migration seems inappropriate. ... Since priorities must be enforced by the AdaOS kernel at all times (to ... could be on any workstation in the network. ...
    (comp.lang.ada)