S
sam
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
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