G
Guest
Hi,
I probably shouldn't have posted this question here, but it seems to me that
the people who take the time here to help others would be by far the best
place to start with my question.
I am currently looking after a school's network which contains two seperate
VLAN'ed networks, one for admin staff and one for curriculum users. For
reasons unbeknown to himself, the previous administrator set the network up
to utilise one 2003 server which both networks share as a DC, query for DNS
and WINS. The school also only has one domain name between both networks
which may not be a really bad thing, but its a single label domain name.
A few months ago the network went down completely, the problem being traced
to a loop in one of the switches, ever since that problem I occasionally log
onto the curriculum network, do a net view and find that I can only see the
other VLAN. I cannot actually access any of the computers on that network
(apart from the DC and file server) but I can still ping hosts on the same
network and my IP settings are correct. I have also gone around and checked
the VLAN memberships on all ports and everything is as it should be (working
from the previous administrators documentation).
The finger seems to be pointing at a looped network cable going from one
switch to another (VLAN to VLAN), but Im not totally sure...does anyone have
any suggestions as to how I should proceed wiht this before I go around and
check every cable runa nd patch lead? I have tried using GFI LAnguard to see
if that would shed any light and I have also tried using a Fluke network
analyser but that didnt show anything up either.
I would be very grateful if someone could help a Brit in need, even if he is
posting in the wrong group!!
TIA,
Kermitdafwog
I probably shouldn't have posted this question here, but it seems to me that
the people who take the time here to help others would be by far the best
place to start with my question.
I am currently looking after a school's network which contains two seperate
VLAN'ed networks, one for admin staff and one for curriculum users. For
reasons unbeknown to himself, the previous administrator set the network up
to utilise one 2003 server which both networks share as a DC, query for DNS
and WINS. The school also only has one domain name between both networks
which may not be a really bad thing, but its a single label domain name.
A few months ago the network went down completely, the problem being traced
to a loop in one of the switches, ever since that problem I occasionally log
onto the curriculum network, do a net view and find that I can only see the
other VLAN. I cannot actually access any of the computers on that network
(apart from the DC and file server) but I can still ping hosts on the same
network and my IP settings are correct. I have also gone around and checked
the VLAN memberships on all ports and everything is as it should be (working
from the previous administrators documentation).
The finger seems to be pointing at a looped network cable going from one
switch to another (VLAN to VLAN), but Im not totally sure...does anyone have
any suggestions as to how I should proceed wiht this before I go around and
check every cable runa nd patch lead? I have tried using GFI LAnguard to see
if that would shed any light and I have also tried using a Fluke network
analyser but that didnt show anything up either.
I would be very grateful if someone could help a Brit in need, even if he is
posting in the wrong group!!
TIA,
Kermitdafwog