Windows Server Connects to web for a few seconds at a time

[meltdowndave]

Hello. You may remember from such threads as "help, I'm in over my head" and "Non-techie stuck as network admin"...

Anyway, I'm setting up a small computer lab for my students and have been having fits getting the DNS/Active Directory and DHCP/WINS servers installed and configured.

I've had some success in getting them installed...now it's about the configuration.

I have all of the comptuers, server too, physically connected in parallel behind a router in another building. Also on the router is another classroom in an adjacent building.

Anyway, I'm only able to connect to the internet for a few seconds at a time. I have to repair the connection to get it working again.

I have the DCHCP turned off in the router and IP addresses 192.168.0.100 - 130 block set aside.

The router's IP has been changed to 192.168.0.101

The main network card on my server is configured as follows:

IP: 192.168.0.123 (last good IP address prior to installing everything)
Subnet: 255.255.255.0
Gateway: 192.168.0.101 (router's IP address)

DNS: 192.168.0.123
Alternate DNS: 71.252.0.12 (set up as a forwarder, too)

I have domain forwarders set for two of Verizon's local DNS servers.

I also have another network card installed that is also connected. The DHCP server is attached to that card and I have the IP 192.168.0.1 attached to it, although the second tier in the DCHP control panel lists it as 192.168.0.0...if this means anything. The DCHP server is set to dole out IPs from 192.16.0.150-220. Even though the IPs on a test computer is 106 and is conecting to my DHCP server....but that's another matter.

I can access my router...so I'm sure that the assigned IP is good. What I can't do is connect to the internet for any period of time without renewing.

What can I check or try to get a solid internet connection?


Sorry if I'm long winded. Just trying to provide as much info as I can and I don't know what is, or isn't necessary.

Thanks!

 

[meltdowndave]

Update. Posted for others down the road.

Two hours later everything seems to have smoothed out, even the DHCP client issues.

I think it was a matter of IP conflicts on the network. Could it be that the IPs on existing computers expired/were retired and new ones doled out?

Stay tuned for the next installment of this train wreck when I tackle Active Directory.

Thanks.