"Scott" wrote:

> I work for a small boat repair shop, my boss (cheap x 1000) has put me in
> charge of this detail, I have some experience but could use some help.
>
> I need to connect all workstations to our server and use as file server,
> print server etc.
>
> Will have 2 sales and 2 tech needing access into server using remote desktop
> from the road.
>
> Email is will not be on server, it is hosted outside source.
>
> server has NOT been setup as a domain and currently the router is handling
> dhcp.
>
> Will also need to provide free wireless to cust in waiting area.
>
> What I currently have:
>     1 server box running 2003 standard
>     8 win xp workstations (5 winxp-pro, 3 winxp-home)
>     1 Static cable broadband connection (opt-online)
>     1 wrt54G Router
>     2 hp 2420dnt laser printers (would like to have all workstations just
> use these 2 networkable printers)
>    
> Any help (advice / how to / best practices) will be greatly appreciated.
>
> Scott
>

> Scott,
>
> That is a lot of work just to setup a domain controller and RDP.  If you
> don't have a lot of experiences, you may want to contact a local network
> administrator even though you stated your boss is really cheap.
>
> 1. Are you going to be running SBS 2003?
> 2. Do you plan to setup Exchange?
> 3. Do you know which port to open for RDP?  Should be 3389.
> 4. Setting up a wireless router should not be difficult since you will not
> be using WEP.
>

"Scott" wrote:

> Trimelater,
>
> The OS will be win server2003 standard R@ edition
>
> I do not plain on setting up Exchange
>
> Yes, you are correct, I have already configured the router to allow TS on
> port 3389
>
> >My  question about DHCP and DNS is, which is better - to have the router serve dhcp or the server? We will have a max of 10 users
>
> Do I need to set the server up as a domain server, currently it set not as a
> domain server
>
> Scott
>
>
>
> > Scott,
> >
> > That is a lot of work just to setup a domain controller and RDP.  If you
> > don't have a lot of experiences, you may want to contact a local network
> > administrator even though you stated your boss is really cheap.
> >
> > 1. Are you going to be running SBS 2003?
> > 2. Do you plan to setup Exchange?
> > 3. Do you know which port to open for RDP?  Should be 3389.
> > 4. Setting up a wireless router should not be difficult since you will not
> > be using WEP.
> >
>

"Trimelater" wrote:

> Scott,
>
> You have two options:
> 1. If you decide to go without a domain controller
>  a. then you will need to do all your configuration for RDP in computer
> management.
>  b. Leave the router to do the DHCP
>  c. You will probably be setup as a Peer to Peer network.
> 2. With a domain controller
>   a. Setup your DNS, DHCP, WINS, VPN, TS
>
> In the past, I have always preferred to go with a domain controller.  Things
> you should think about is, research:
> 1. Forest Prep and domain prep.
> 2. dcpromo.
>
> Let me know what route you would like to go and maybe I will be able to
> assist you with it.
>
>
> "Scott" wrote:
>
> > Trimelater,
> >
> > The OS will be win server2003 standard R@ edition
> >
> > I do not plain on setting up Exchange
> >
> > Yes, you are correct, I have already configured the router to allow TS on
> > port 3389
> >
> > >My  question about DHCP and DNS is, which is better - to have the router serve dhcp or the server? We will have a max of 10 users
> >
> > Do I need to set the server up as a domain server, currently it set not as a
> > domain server
> >
> > Scott
> >
> >
> >
> > > Scott,
> > >
> > > That is a lot of work just to setup a domain controller and RDP.  If you
> > > don't have a lot of experiences, you may want to contact a local network
> > > administrator even though you stated your boss is really cheap.
> > >
> > > 1. Are you going to be running SBS 2003?
> > > 2. Do you plan to setup Exchange?
> > > 3. Do you know which port to open for RDP?  Should be 3389.
> > > 4. Setting up a wireless router should not be difficult since you will not
> > > be using WEP.
> > >
> >

"Scott" wrote:

> how will I be able to reach you?
>
> "Trimelater" wrote:
>
> > Scott,
> >
> > You have two options:
> > 1. If you decide to go without a domain controller
> >  a. then you will need to do all your configuration for RDP in computer
> > management.
> >  b. Leave the router to do the DHCP
> >  c. You will probably be setup as a Peer to Peer network.
> > 2. With a domain controller
> >   a. Setup your DNS, DHCP, WINS, VPN, TS
> >
> > In the past, I have always preferred to go with a domain controller.  Things
> > you should think about is, research:
> > 1. Forest Prep and domain prep.
> > 2. dcpromo.
> >
> > Let me know what route you would like to go and maybe I will be able to
> > assist you with it.
> >
> >
> > "Scott" wrote:
> >
> > > Trimelater,
> > >
> > > The OS will be win server2003 standard R@ edition
> > >
> > > I do not plain on setting up Exchange
> > >
> > > Yes, you are correct, I have already configured the router to allow TS on
> > > port 3389
> > >
> > > >My  question about DHCP and DNS is, which is better - to have the router serve dhcp or the server? We will have a max of 10 users
> > >
> > > Do I need to set the server up as a domain server, currently it set not as a
> > > domain server
> > >
> > > Scott
> > >
> > >
> > >
> > > > Scott,
> > > >
> > > > That is a lot of work just to setup a domain controller and RDP.  If you
> > > > don't have a lot of experiences, you may want to contact a local network
> > > > administrator even though you stated your boss is really cheap.
> > > >
> > > > 1. Are you going to be running SBS 2003?
> > > > 2. Do you plan to setup Exchange?
> > > > 3. Do you know which port to open for RDP?  Should be 3389.
> > > > 4. Setting up a wireless router should not be difficult since you will not
> > > > be using WEP.
> > > >
> > >