Windows Server 2008 - Bridged network problems suddenly - unidentified access!!
Hi Guys, I thought I sign up since I wish for some assistance to some of
the network engineers/support there who would might know what is up with this
specific weird issue we are having since I am scratching my head a little on
this and itís probably something simple but I am just not getting it.
Some of our our servers today connection has become unidentified access and would not wish
to communicate with our Domain Controller/DHCP. Nothing has been altered what so
ever from any of us and this why it is weird. All Static IP information is
correct and fits in with our IP range we was given, we have static
IPs (the first 49) outside the DHCP Scope we have on this system (172.16.0 to
172.16.49 we have for static IPS and then we have made a scope from 172.16.12.50
to .16.254 in our address range) and we know the first 50 static IPs are fine
since some of the servers we have been fine and the only ones that had been
affected are some of them which is unfortunately our curriculum File server and
our backup and printer server.
How we got these to work as a temporary measure
was to unbridge all our network adapters and have them go for automatic
addresses but I am sure you can see why this is not the best thing to do and
want to get them statically back and all network adapters bridged again to what
they were. All of our environment is windows server 2008/Windows 7 so it is very
strange that suddenly three of these servers have done this when nothing else
has been altered. Even if we disabled some of the multiple network adapters to have one and put in the original IP details they are working fine, but when it is bridged it comes up with unidentified. We only have the standard windows firewall on and I have looked on group policy and nothign seems to have changed there.
Static Ip addresses (0-49) have not been changed on bit and even some of the
servers in this range are working still.
Really do appreciate this guys and happy to folk out and pay for a beer if you can point what the issue could be :)