Hp Nc326i Pcie Dual Port Gigabit Server Adapter

Hello, May I ask again for your expertise and experience regarding our problem. We have a dc/file server (win2k8 r2) with more or less 2000 users. Earlier, some users could no longer access it via WAN or LAN. The difficult part is that not all users are experiencing the problem, also WAN & LAN. As per our network group, there was no problem on the routers, switches, connections and ports.

1. Hp Nc326i Pcie Dual Port Gigabit Server Adapter Windows 10

Download the latest driver for HP NC326i PCIe Dual Port Gigabit Server Adapter #2, fix the missing driver with HP NC326i PCIe Dual Port Gigabit Server. This download provides HP NC326i PCIe Dual Port Gigabit Server Adapter driver and is supported on HP ProLiant ML350 G6 that is designed to run on Windows Operating System Only. Product detail -- C3N37AA:HP 361T PCIe Dual Port Gigabit NIC Includes features, specifications and warranty information, as well links to technical support, product data sheets, and a list of compatible products.

I did not find any error logs on the evnt viewer regarding connection problems or services malfunctioning. I just noticed in resource monitor - TCP Connection that its graph is consistently high with 60 max. Our last resort was to restart the server.

After restart, all users could now connect to the server. Still no event for error logs, but in resource monitor - TCP Connection, the graph was in the middle but its now 500 max. I'm afraid it might happen again until we can't find the cause. Have you also encountered this and have known the cause? Thanks a lot. Hello, the problem description is not really helpful. How exactly do you realize the WAN/LAN access problem?

Hopefully the DC is NOT connected with 2 NICs and used for RRAS services as VPN server or is this SBS version from Windows? But as you state Windows server 2008 R2 it seems not. For starting please post an unedited ipconfig /all from the DC/DNS server and a problem client so we can verify some basic settings. Is that the only DC in the domain, then with 2000 users please think about building a second DC/DNS/GC for failover and redundancy? This is also recommended by Microsoft. Best regards Meinolf Weber MVP, MCP, MCTS Microsoft MVP - Directory Services My Blog: Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights. Hi Meinolf, Thanks for the response.

To clarify, our server is Win2k8 Server Standard R2 (SP1). Although we have backup DCs, its file server service have no failover/redundancy (sorry, business have limited budget for OS and HW).

The server is not connected with 2 NICs and is not used for RRAS. Its' roles are DC, File Server, DNS only. Here is the scenario, Server (IP 172.21.100.XXX; SB: 255.255.252.0, GW: 172.21.100.XXX) could be ping by users in LAN. Users have the same ip range & subnet as the server. However, some users when connecting to the shared folder of the server (red error 'Unable to find path' or 'could not be accessed'. Some users, same range and subnet, could access the server. For WAN A & B, sample IPs (172.21.30.XXX & 172.21.10.XXX) can't access with same error but can ping the server.

But for WAN C (172.21.32.XXX), have no problem. After the restart of the server, all are working fine.

As of now, the problem did not yet reoccured. Hello, please post the unedited ipconfig /all as requested. The ip address infos are not really helpful this way. As you are using 172.21.x.x this is private ip range and NOT accessible from the internet so no problem with postin gthem here. Domain names or server name you can change if you have concerns about BUT keep the format of names, so DOMAIN.COM or DOMAIN for example. What kind of WAN access are you talking about, between subnets or to the internet?

Best regards Meinolf Weber MVP, MCP, MCTS Microsoft MVP - Directory Services My Blog: Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights. Hello, on servers it is recommended to disable not used NICs. So the problem server is not DNS server, if yes please configure the real ip address instead using only the lopback ip 127.0.0.1.

On the client you use 'mshome.net' as Connection specific DNS suffix Search list entry, why? So the problem server is in a different subnet as the client machine according to the ip configuration? Is that a routed network or different? Any firewalls in between and which bandwitdh/speed is between the locations? Best regards Meinolf Weber MVP, MCP, MCTS Microsoft MVP - Directory Services My Blog: Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights. Hi Prashant, Thanks for the response. We have DHCP appliance on our network group giving us these IP addresses for the computers.

Could it be the main cause of the problem? Actually, this is the first time I noticed that there was an IPV6 on the computers. However, please take note that we could ping the server by its IP addresses and servername. Need to check if those without IPV6 encountered this problem. Hi Meinolf, Ok, will disable not used NICs.

Hp Nc326i Pcie Dual Port Gigabit Server Adapter Windows 10

The problem server is a DNS server but its IP-DNS is configured to 172.21.32.24 (another DC) and a loopback as its secondary. Connection from client to server is a routed network (but as mentioned, this also happened to clients with the same subnet). For firewalls, I think there are routers which act as a firewall that disables specific ports. For the DNS suffix search, not sure why, I also did not know how 'mshome.net' got there. Could it be removed? Please also note that when I restarted the problem server, the access of shared folders from the users to the server have been solved without changing config from the servers and clients. Hi Jeff, Actually, the problem reoccured with the link below and after restart, it was ok with no critical error being logged on the event viewer. What we saw in the data collector sets are the following: While having error: After Restart: Fortunately, a server replacement is scheduled this week. This server will be reformatted and we could now update the machine's BIOS and firmware as suggested by the manufacturer.

Still not yet sure what is the cause but those screenshots are the only clues I got. I assume this is a machine error but what concerns me also is the difference in the resource monitor.