2008 R2 networking issue
Hi Trana010,
Thanks for posting here.
> however I am unable to launch a number of things suchs as for example:
>Network and sharing center
>Local Services
>Broadcom Advanced Controller Suite
After reading your symptoms, Id say that networking may not the root cause of this issue. Actually Id consider it as a performance issue here.
If all these services would startup properly after a time interval then it clearly indicates that services might got delay somehow since OS boot up.
Id suggest to first check if we will get same issue if reboot this system into safe mode with networking. Meanwhile, Id also suggest troubleshooting by removing the OEM Broadcom Advanced Controller Suite form this server but reaming only NIC driver
and see how is going.
Regards,
Tiger Li
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact
tnmff@microsoft.com.Tiger Li
TechNet Community Support
August 27th, 2012 11:09pm
Okay, well, that looks to be okay on the surface of things. You could provide the output from a "route print" statement, but to be honest, I think that's only going to reinforce the fact that things look fine, though the persistent
entries (or lack thereof) might be insightful.
That said, those IPv6 DNS servers don't sit comfortably with me insofar as during startup, where a kajillion things are all trying to start up, any delays from non-existent DNS servers can be critical to services starting
in a timely manner, and there's three in this list that I'm guessing aren't used. They should only exist on the loopback interface.
If you're not using IPv6, you might want to run the following (where each bullet point is a new line):
netshint ipv6set int "Backup" routerdiscovery=disabled otherstateful=disabled managedaddress=enableddel dns "Backup" allexit
You can run either of the following to check they've been removed:
ipconfig /allnetsh int ipv6 show "Backup" dns
Despite having the "Office Network" NIC first in the binding order, I've personally run into too many issues where this dynamically changes on the fly (particularly on ISA), hence making sure each NIC is clean and the routing table
is configured statically (which is where the route print comes in handy).
I'd also disable NetBIOS over TCP/IP (using the GUI) unless it's actually a requirement for the application itself.
But really, all this is is housekeeping. It may have no bearing on your startup issue whatsoever.
Cheers,
Lain
Free Windows Admin Tool Kit Click here and download it now
August 27th, 2012 11:57pm
Hi,
I've got a Dell R510 with some odd network issues, OS is 2008 R2 SP1, no NIC teaming, the builting Broadcom BCM5716C double port nic has 2 fixed IPs on different subnets.
The server restarts just fine with no boot errors and using the console screen I am able to login, however I am unable to launch a number of things suchs as for example:
Network and sharing centerLocal ServicesBroadcom Advanced Controller Suite
Other things like Event Viewer and Windows Explorer, browsing the local disks work perfectly fine, server responds to ping on hostname and network shares are available just fine.
After about 15 minutes, all applications and features launch just fine and RDP now works as well. At this stage the server really behaves percetly normally. I am concerned that this network issue is just a symptom of a greater problem which might also be
affecting my backups done on this server of remote servers.
What I have tried off the top of my head is:
Different NIC settingsChecked NIC bindingsDifferent NIC drivers (removed, updated)With and without fixed IP address settings (both on DHCP)Different switch portsSwapped ethernet cablesDell support (who advised no HW fault after checking some logs)This command: "net localgroup "Administrators" "local Service" /add"TCP Chimney settings:
http://us.generation-nt.com/answer/w2008-server-network-sharing-center-help-77404082.html
Any ideas?
August 28th, 2012 4:46am
Hi,
Please see if your Server needs any firmware updates.I do not represent the organisation I work for, all the opinions expressed here are my own.
This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
- .... .- -. -.- ... --..-- ... .- -. - --- ... ....
Free Windows Admin Tool Kit Click here and download it now
August 28th, 2012 5:03am
Tiger, thanks for your response, you led me onto the right track, one of my backup software services was holding up the other services which the network features are relying on, I disabled this service and restarted the server and everything now
starts up as quickly as expected. Now I can proceed troubleshooting the backup software knowing that the backup issues arent caused by the network issue.
Lain, thanks as well, regardless of you having a direct impact on the resolution you given me some good advice for some housekeeping.
August 28th, 2012 6:00pm
As mentioned I've tried different NIC drivers, old ones, new ones and Windows default ones. I've also updated some other drivers like the chipset and flashed the BIOS.
Free Windows Admin Tool Kit Click here and download it now
August 28th, 2012 8:03pm
I would install a new NIC. I have had a couple of failures of the built-in Broadcom NIC in Dell machines.
The symptoms were similar to yours at first (slow start up), and gradually got worse.
Bill
August 28th, 2012 9:36pm
Hi,
You mentioned you have two separate NICs. How did you set up the IPv4 configuration? You didn't set up gateways on both NICs, did you? If it's only one, then what static routing rules have you added?
For a dual NIC setup, the "normal" configuration requires that you only specify the gateway address on one adapter - typically the one which directs traffic to undefined networks (hence being the default), while for the other NIC without the gateway, you
use the "route" command to statically define which networks should route through it.
I can go into depth on this with examples but I'd rather find out which your current configuration is first.
Cheers,
Lain
Free Windows Admin Tool Kit Click here and download it now
August 28th, 2012 10:19pm
Hi Lain,
Thanks for your response. NIC #1 is configured for the main office subnet with the appropriate gateway (this is the first NIC in the bindings of
course). NIC #2 is configured for our backup subnet, same as all other servers that gets backed up. As mentioned though, I've tried with DHCP on both NICs and the behaviour is exactly the same. Technically its 2 ports on the integrated motherboard NIC.
Ethernet adapter Office Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5716C NetXtreme II GigE (NDIS
VBD Client) #10
Physical Address. . . . . . . . . : <editted out>
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::3057:6fdc:49a3:a451%14(Preferred)
IPv4 Address. . . . . . . . . . . : 10.10.2.7(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.2.2
DHCPv6 IAID . . . . . . . . . . . : 293088203
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-65-FC-E1-78-2B-CB-20-81-3A
DNS Servers . . . . . . . . . . . : 10.10.2.12
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Backup network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5716C NetXtreme II GigE (NDIS
VBD Client) #36
Physical Address. . . . . . . . . : <editted out>
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::452a:9aa:3b23:8a3b%15(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.7(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 343419851
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-65-FC-E1-78-2B-CB-20-81-3A
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Bill: I've got no hardware errors, not in the Dell OpenManage logs, not in the Windows logs and when reported to Dell, the technician was unable to find any network hardware related fault or error.
August 29th, 2012 12:38am


