Re: Design for internet conectivity

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 05/15/04 

Date: Sat, 15 May 2004 08:22:06 -0400

sam wrote:
> Existing Hardware / software Components:
> 1. ISP Connection DSL MOdem.(Hareware)
> 2. Dlink DI 704 P DSL Router.(Hardware)
> 3. Dlink Switch 16 Port (Two).
> 4. IBM X series 220 eServer.( Hardware)
> 5. SQL server 2000.(Software)
> 6. Windows 2000 Server.(Software)
> 6. 25 Windows 2000 Workstations.(Hardware)
> 7. All Static IP addressing
>
> I inherited a network setup at a company which has a DSL
> internet connection which in turn is connected to a Dlink
> DSL DI704 router. We one IBM xseries 220 eserver pluged in
> to Dlink 16 port switch. All workstations are also in to
> switch. The DSL Dlink Router is plugged into one of the
> port on Switch. We have Active Directory and a DNS setup
> (Local).
>
> All workstations are configured static (192.168.0.XX) IP
> Information with Primary DNS and Secondary DNS numbers
> provided by ISP.
>
> If we put up new workstation it would NOT join Domain
> atall with above configuration. I got certain that it is a
> name resolution issue. After putting my IBM eserver IP
> (192.168.22.1) to the DNS settings on the workstation, the
> computer joined the domain right away.

All servers and workstations should specify *only* the internal
AD-integrated DNS server's IP address in their network settings. The
AD-integrated DNS server should be set up with forwarders to your ISP's DNS
servers for external resolution. See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202 for more
info. Using DHCP instead of static addresses makes changes like this a *lot*
easier - I'd use DHCP if it were up to me.

Another thing I'd look at is whether the DLink router is any sort of real
firewall (not just a NAT box). Firewalls aren't a cure-all but it's
important to protect your network at the perimeter.
>
> The network logon time is very slow, and event viewer has
> many errors.
>
> Now First question if at all the existing configuration is
> a valid configuration (Design) in windows2000
> environment?.
>
> If not suggest solution please.
> Thanks
> sam

Relevant Pages

  • Re: logon problem
    ... I would like to understand your pointing me to DNS. ... another user can not log on, and all workstations are getting IP's ... from DHCP scope on SBS Server, what should I be looking for in the IP Config ... >> Server is providing DNS services for the entire network, ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: UNC, VPN site to site
    ... Posting on MS newsgroup will benefit all readers and you may get more help. ... How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com ... On Site A are all Microsoft ressources (DNS, Wins, PDC) We use Win NT4 ... At the same moment, for other workstations on site B, applications are ...
    (microsoft.public.windows.server.networking)
  • 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)
  • Slow Network and Other Issues -- W2K & XP
    ... about 10 XP Pro workstations and no remote locations. ... point I don't know if it server or workstation related. ... All seems network ... I have begin to questioned my orginal instattion of AD and DNS. ...
    (microsoft.public.windows.server.networking)
  • Re: DNS rookie
    ... You would do better to allow SBS to do both DHCP and DNS. ... I have a simple network, DSL from the Internet to my SonicWall ...
    (microsoft.public.windows.server.sbs)