This post is more than 5 years old
12 Posts
0
31121
April 4th, 2013 10:00
PE2950 Intermittent network problems
Hey guys, I have a PE2950 running Windows 2008 R2. It is a domain controller (not primary) and I'm having all kinds of trouble with replication errors. I'm also having trouble with DNS errors.
When I log onto the 2950 and run nslookup ifc.local, sometimes it will complete successfully immediately. Then if I run it again just seconds later, it will time out. I have checked the reverse lookup zones on both servers and they each have the correct PTR records (it appears) and each server's NIC points to the other server and then to its self for DNS. There are forwarders established in the DNS records but not on the NIC. I don't seem to be having any network trouble with the pdc (a 1950).
It would appear that my network problem is intermittent and may be hardware/driver related but I'm not sure. One thing I found interesting is that if I try to enable IPV6 on the 2950's NIC, I get an error message that says in order to configure TCP/IP I must install a network card but there is clearly one there and IP4 is configured just fine.
IPconfig also shows two tunnel adapters I'm not familiar with. Clearly they aren't being used. Should I disable them some how?
Here are the results of an ipconfig /all and nslookup example. Of course, when I went to post this I couldn't get nslookup to time out but when it does I get server: UNKNOWN and the correct IP address and then three lines of time out.
Thank you, in advance for any help you can offer!
Windows IP Configuration
Host Name . . . . . . . . . . . . : IFCServer2
Primary Dns Suffix . . . . . . . : IFC.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : IFC.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client)
Physical Address. . . . . . . . . : 00-1C-23-CF-7E-6E
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.2.11(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.10
192.168.2.11
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{865DC311-438F-4420-9B23-0062AF1CFBE5}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
/////////////////////////////////////////////////////////////////////////////////////////////
Server: ifcserver1.ifc.local Address: 192.168.2.10 Name: ifc.local Addresses: 192.168.2.11 192.168.2.10



theflash1932
9 Legend
•
16.3K Posts
1
April 4th, 2013 11:00
Is your firmware up to date? There were several issues with these NIC's early on which were addressed via firmware and driver updates (drivers issues were with 2003 ... have not heard anything specific about 2008). You should update your BIOS and ESM before updating the NIC firmware.
Brandon_IFC
12 Posts
1
April 17th, 2013 08:00
Brandon_IFC
12 Posts
0
April 4th, 2013 10:00
Also, I was just connected to this server via RDP when I wrote this post and I just got disconnected. I am beginning to think this has to be hardware or driver related...
theflash1932
9 Legend
•
16.3K Posts
0
April 4th, 2013 11:00
Well, there would be no harm in running it ... it would abort the update if it were not for the right device.
We may need one of the Dell guys to decipher the garbage listed for these updates, if the one you have doesn't work. One way you could do it would be to run SUU to update the system - it would automatically pick the latest version for the NIC's in this system, but that is a pretty large download to update a single device (assuming everything else is up to date).
Brandon_IFC
12 Posts
0
April 4th, 2013 11:00
Here's a question about the firmware. I only see one firmware update available for Broadcom Nextreme. Mine is a Broadcom NExtreme II. I assume that since there is only one firmware update that it's good for mine too? It talks about being an update for the 7.4.x firmware family but my firmware is currently 5.2.22.0. Do you see any problem with running this firmware update?
Brandon_IFC
12 Posts
0
April 4th, 2013 11:00
I've got the BIOS and ESM up to date. I just grabbed the driver from Dell and the install package said it was going from version 1.0 to version 14.x so that's pretty huge. I'll take a look at firmware next assuming I can log back in over RDP today when that driver install finishes.
Brandon_IFC
12 Posts
0
April 4th, 2013 14:00
Well, bad news. I ran a driver update via RDP and now I can't access the server anymore. I had a person on site perform a reboot but that didn't bring it back so I won't be able to touch the thing for a few days now.
theflash1932
9 Legend
•
16.3K Posts
0
April 4th, 2013 15:00
It is normal for the connections to drop during the update, but it shouldn't last more than several seconds. Which driver (file) did you use to update with?
RAJKUMAR J
21 Posts
0
April 17th, 2013 04:00
Please share the below information for our understanding.
1)Share the network card Family type like Broadcom,intel,QLogic etc
2)Provide the Firmware and driver version of the NIC.
3)Is the NIC supporting N-PAR(network Partitioning) and Enabled?
4)Is Windows OS type as x86 or x64 Bit version ?