Slow logon and other problems

[Dimitrios Papoudas]

Hi
I have a network with W2K advanced server another machine
with W2k Advanced server that runs a commercial program and
some W2k pro macines. Access to the internet is done
through a DSL modem. The IP are all static. The servers
have 192.168.0.x and the workstations 192.168.1.x the
subnet is set to 255.255.0.0. Up until now eveything worked
fine. Suddenly i noticed that the main server (also a
AD/DC) dosn't get any updates for the antivirus server or
windows updates. When i checked it, it couldn't ping the
modem. And the same happened also for the other server.
After i changed the IP for both servers to 192.168.1.x
everything worked fine but some of the workstations had a
very long logon time (around 30 min). If i change back the
IP the workstations logon fine but the servers can't
connect to the internet.
any ideas?
Any help would be nice
Dimitrios

 

[jason]

sound slike the dsl modem is on a diff subnet whats is its
ip address is it 192.168.0 or 192.168.1? maybe make it
same as rest of network i.e 19.168.1 and long logon maybe
due to dns prob? ensure the dns server is in the LAN not
use the isp dns

 

[SteveC]

Hi
I have a network with W2K advanced server another machine
with W2k Advanced server that runs a commercial program and
some W2k pro macines. Access to the internet is done
through a DSL modem. The IP are all static. The servers
have 192.168.0.x and the workstations 192.168.1.x the
subnet is set to 255.255.0.0. Up until now eveything worked
fine. Suddenly i noticed that the main server (also a
AD/DC) dosn't get any updates for the antivirus server or
windows updates. When i checked it, it couldn't ping the
modem. And the same happened also for the other server.
After i changed the IP for both servers to 192.168.1.x
everything worked fine but some of the workstations had a
very long logon time (around 30 min). If i change back the
IP the workstations logon fine but the servers can't
connect to the internet.
any ideas?
Any help would be nice
Dimitrios

Hello,

If you change the IP address of the servers to 192.168.1.x, you will
also need to change the server DNS records to reflect the change.
As well, you need to change the DNS servers used by your servers and
workstations to reflect the IP address change.

This will most probably care of the slow login times.

The default mask for 192.168.0.x is 255.255.255.0. Using 255.255.0.0
may not agree with some of your network devices. I've seen similar
problems with some buggy routers. This may or may not apply in your
case.

Personally, I try to avoid using supernets when I can. Since you're
using a private network addressing scheme, you can use 172.16.x.x/16
for example if you need the address space, or if address space is not
an issue, use 192.168.x.x/24

regards,

SteveC
======
If at first you don't succeed, forget skydiving