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.

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

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...b;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

Is it possible to regiser the IBM server (local) with ISP
and if this would possibly solve the name resolution for
all Win2000 Prof on the network and leave the DNS to same
as provided by the ISP?



>-----Original Message-----
>
>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
>
>
>.
>

(E-Mail Removed) wrote:
> Is it possible to regiser the IBM server (local) with ISP
> and if this would possibly solve the name resolution for
> all Win2000 Prof on the network and leave the DNS to same
> as provided by the ISP?

The external DNS for your Internet domain can (and probably should) still be
hosted by the ISP. I'm talking about your AD DNS...you *must* set it up as I
outlined or you will continue to have problems. Heck, you can name your
internal DNS microsoft.com and nobody else in the universe need ever know
about it...it's a separate entity. Not that I'm recommending that name.
>
>
>
>> -----Original Message-----
>>
>> 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
>>
>>
>> .

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.
>
> 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 *

hey mate,

just reading your speel on how you have your network set up. I mysel
(at home) run a dlink di-704p router with great sucess. but i feel tha
is where the dlink di-704p and di-704up routers belong, at home.

One of the people that responded to this message made a very vali
point about the firewall regarding its effectiveness at keeping th
malicious users and traffic out of your network. If you want to sta
with dlink hardware you really need to go for something which wa
intended to be run in a commercial environment. These include, Dlin
DI-804HV (http://www.dlink.com/products/?pid=59) or the Dlink DFL-30
or DFL-600 (http://www.dlink.com/products/?pid=66)

I have been heavily involved with windows 2000 server and workstatio
deployment and the only 2 ways that a windows 2000 professiona
workstation will be able to log into a windows 2000/2003 server is t
have your dns configuration as follows on the client pc's (or your DHC
Server configuration).
Primary DNS: 192.168.0.1 (your win2000 server IP)
Secondary DNS: xxx.xxx.xxx.xxx (Primary DNS @ ISP)
Tertiary DNS: xxx.xxx.xxx.xxx (Secondary DNS @ ISP)

If you can possibly get your windows 2000 server's DNS server t
forward to your isp's dns servers that is by far the preferred metho
of doing things. One other thing, i couldn't agree more with using DHC
on that network. it would make the administration so much mor
manageable for you. One important thing is if you are planning o
deploying DHCP on your network you need to make sure the DHCP server i
disabled on the dlink router first.

The short and sweet: look at buying another router designed fo
commercial use, set your dns configuration as above and for mor
manageability and control i would be implementing DHCP on your window
2000 server.

Hope this helps you out,

Andrew Parson


-
aparson
-----------------------------------------------------------------------
Posted via http://www.mcse.m
-----------------------------------------------------------------------
View this thread: http://www.mcse.ms/message677344.htm