K
Karl Burrows
I have spent the last 3 days trying to figure out why our WAN connection all
of a sudden crashed. Here's the scenario:
Neighborhood has a wireless connection that originates from our building.
Our LAN was supposed to be separate. We setup DSL about 3 weeks ago to get
away from the poor connections from the wireless. I got a call from the ISP
yesterday telling me we were broadcasting our server IP on the WAN! Turns
out when they guy came to setup the DSL connection for us, he decided it
would be nice for the neighborhood to also have DSL, so he plugged the
wireless WAN into our LAN!!!! Instant trouble!
Needless to say, I got them back on their own network and we are no longer
exposed to the Internet, however, now we cannot see past the firewall.
Every once in a while, the Internet will pop up, but then disappear after
about 15 minutes.
Here's our network setup:
*Windows 2000 Server running DHCP, no DNS in a domain of about 20 clients.
No other servers.
*Network connects to 2 switches (one Linksys, no auto-negotiate, one Zonet,
auto negotiate)
*Switches connect to Linksys DSL router (assigned an address in the subnet)
to DSL modem
Very flat, simple setup. The problems is now anytime I connect any type of
Layer 2 device (switch or hub) to the WAN, the Linksys drops the connection.
I started by pulling the Linksys from the network and hooking a laptop to it
to reset and reconfigure. I set it up with no DHCP, PPPoE and port
forwarding for VPN and Terminal Services. Again, pretty basic. If I plug
the modem into the WAN port and plug the laptop into any other port, I get
instant Internet and I can open the router interface with no problems. If I
connect any switch, everything goes down (or goes down very shortly). Even
the laptop, which is connected directly to the router is unable to even get
into the Linksys interface. Internal network is fine and I can ping the
router from any computer, but no connection. I cannot ping the WAN
interface or any of the DNS servers (only occasionally will I get a short
window where something will return a ping).
I even tried plugging the laptop by itself into a new switch, then plugging
the switch into the Linksys (those were the only connections). Again, the
connection was lost.
I have rebooted the router several times and occasionally I will get
connected for a few minutes and then I'm gone again. It's almost like RIP
is running and the tables couldn't update and drops the connection. I have
replaced the router and the same thing happens. I have replaced the cable,
tried plugging it into different switches and ports. DHCP on the sever is
working fine, no errors in the system events log and nothing shows up in the
outgoing or incoming logs for the Linksys.
I even shut down the entire network, and brought it up starting with the DSL
modem, the Linksys, the switches (to reset the tables in case there was a
DNS, IP or other error), then the server and then the clients. Still
nothing.
Again, I can ping the LAN interface from anywhere in the LAN, but nothing
much past that.
I have contacted Linksys and they have been little help. I can't get beyond
the first level of help and they tell me to run it as a router or move my
DHCP to the Linksys (which I refuse to do, because if it goes down, my
entire network goes down). Better to have the server keep DHCP.
ANY THOUGHTS????????????????????
of a sudden crashed. Here's the scenario:
Neighborhood has a wireless connection that originates from our building.
Our LAN was supposed to be separate. We setup DSL about 3 weeks ago to get
away from the poor connections from the wireless. I got a call from the ISP
yesterday telling me we were broadcasting our server IP on the WAN! Turns
out when they guy came to setup the DSL connection for us, he decided it
would be nice for the neighborhood to also have DSL, so he plugged the
wireless WAN into our LAN!!!! Instant trouble!
Needless to say, I got them back on their own network and we are no longer
exposed to the Internet, however, now we cannot see past the firewall.
Every once in a while, the Internet will pop up, but then disappear after
about 15 minutes.
Here's our network setup:
*Windows 2000 Server running DHCP, no DNS in a domain of about 20 clients.
No other servers.
*Network connects to 2 switches (one Linksys, no auto-negotiate, one Zonet,
auto negotiate)
*Switches connect to Linksys DSL router (assigned an address in the subnet)
to DSL modem
Very flat, simple setup. The problems is now anytime I connect any type of
Layer 2 device (switch or hub) to the WAN, the Linksys drops the connection.
I started by pulling the Linksys from the network and hooking a laptop to it
to reset and reconfigure. I set it up with no DHCP, PPPoE and port
forwarding for VPN and Terminal Services. Again, pretty basic. If I plug
the modem into the WAN port and plug the laptop into any other port, I get
instant Internet and I can open the router interface with no problems. If I
connect any switch, everything goes down (or goes down very shortly). Even
the laptop, which is connected directly to the router is unable to even get
into the Linksys interface. Internal network is fine and I can ping the
router from any computer, but no connection. I cannot ping the WAN
interface or any of the DNS servers (only occasionally will I get a short
window where something will return a ping).
I even tried plugging the laptop by itself into a new switch, then plugging
the switch into the Linksys (those were the only connections). Again, the
connection was lost.
I have rebooted the router several times and occasionally I will get
connected for a few minutes and then I'm gone again. It's almost like RIP
is running and the tables couldn't update and drops the connection. I have
replaced the router and the same thing happens. I have replaced the cable,
tried plugging it into different switches and ports. DHCP on the sever is
working fine, no errors in the system events log and nothing shows up in the
outgoing or incoming logs for the Linksys.
I even shut down the entire network, and brought it up starting with the DSL
modem, the Linksys, the switches (to reset the tables in case there was a
DNS, IP or other error), then the server and then the clients. Still
nothing.
Again, I can ping the LAN interface from anywhere in the LAN, but nothing
much past that.
I have contacted Linksys and they have been little help. I can't get beyond
the first level of help and they tell me to run it as a router or move my
DHCP to the Linksys (which I refuse to do, because if it goes down, my
entire network goes down). Better to have the server keep DHCP.
ANY THOUGHTS????????????????????