Re: New At Network Configuration

administrative computer and then the Group of
workstaions connect via the admin computer to the network


You lost me here.

I really can't follow what you are trying to do.

DDS
"Silom" <nospam@xxxxxxxxxxxxxxx> wrote in message
news:53466EA0-D716-49D8-9E68-0E72073D8D7D@xxxxxxxxxxxxxxxx
Hi All,

I am very new to all of this.

I am using MS Server 2003 R2 etc and so far have tried some very simple
networks all using the same internal network.

Now I would like to start a network where a group of workstations connect
to the network but using a different address.
So there would be a DHCP/DNS/AD/RRAS server, a Web server,a Firewall, an
administrative computer and then the Group of
workstaions connect via the admin computer to the network.

Computer 1. two NIC's (one for the internet, one for the local network)
(srv 2003 r2)
Computer 2. a single NIC (web server)
Computer 3. two NIC's (one for the local network and one for the admin
computer) (firewall)
Computer 4. two NIC's (one to connect to admin and the other to the Group
of workstations) (Admin)
Computers 5 - 10 one NIC each


I let the server program configure as a typical first server. OK. Those
computers that reside up to the firewall
(as yet not installed), computers 1 to 3, connect to the network and also
the internet using DHCP/DNS/AD/RRAS as setup.

However, The card in computer 3 that looks to connect to the admin
computer and those which look from the workstations
to the admin computer do not connect to the network.

I have not setup any other configurations except as instructed "To Do
Next" after the initial setup. I am seeing leases
used under DHCP and the same addresses appearing in the FWD Lookup zone
under the domain name.

Can some assist me in configuring the necessary aspects to help me rectify
the problem.


.

Relevant Pages

  • RE: Event ID 529
    ... The source is clear - workstations that are not part of my ... SBS2003 domain share the same local network (it's a shared local network in ... This kind of issue may be caused by Application logon such as while Outlook ... is connecting to Exchange Server, or this is an automated dictionary attack ...
    (microsoft.public.windows.server.sbs)
  • Re: Adding PC to SBS 2000 domain
    ... There are three workstations that have been working fine for years. ... I have inherited this network and my knowledge is based/limited to SBS ... On the SBS 2000 server I created and new user account and new computer ...
    (microsoft.public.windows.server.sbs)
  • Re: Applying Personal Settings
    ... I wouldn't rule out that or another network ... ruling out the server NIC). ... Running ipconfig /all on the workstations confirms that they're getting DHCP ... with ipconfig results pointing gateway & dns ...
    (microsoft.public.windows.server.sbs)
  • RE: howto let asigned user login destinated workstation
    ... among them we have 5 workstations ... our give them the rights to login every workstation i.e. any ... may be really setting up your network for failure. ... resources on their own server with very limited access to anything else. ...
    (microsoft.public.windowsxp.general)
  • Re: Deleting duplicate service pack files
    ... until we went Server 2003 and XP workstations. ... I liked my network a lot ... The good thing is we use terminal services and remote desktop for our ...
    (microsoft.public.windowsxp.general)