Brycerocket

Asus P8P67 - Lan Driver And Max Ram

12 posts in this topic

Hey everyone, two questions:

- Does WHS 2011 support the P67 chipset default intel lan adapter? I tried everything to get it to load: driver's from the intel site, asus site, device manager.

- Is there a max limit on ram in WHS 2011? I put 16 gb in my machine, which is registered but properties reports only 8gb as usable.

Thanks!

-Brycerocket

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

Hey everyone, two questions:

- Does WHS 2011 support the P67 chipset default intel lan adapter? I tried everything to get it to load: driver's from the intel site, asus site, device manager.

- Is there a max limit on ram in WHS 2011? I put 16 gb in my machine, which is registered but properties reports only 8gb as usable.

Thanks!

-Brycerocket

The on board nic for the P8P67 does not work with WHS/2008R2 I tried everything myself and ended up adding in a nic card. Not sure abbout the ram but I'm pretty sure it should see all 16GB

Share this post


Link to post
Share on other sites

Any suggestions on compatible NICs? would like to have gigabit. Yeah I'm pretty sure the memory is a limitation since it does show 16 right next to the 8 usable.

Share this post


Link to post
Share on other sites

>>I put 16 gb in my machine,

overkill, WHS will barley ever use 4GB, pull some memory down to 8 or 4 and use it elsewhere.

Share this post


Link to post
Share on other sites

WHS 2011 is based on Windows Server 2008 R2 Foundation, which is capped at 8GB RAM and a single CPU (although multiple cores are supported).

Share this post


Link to post
Share on other sites

>>I put 16 gb in my machine,

overkill, WHS will barley ever use 4GB, pull some memory down to 8 or 4 and use it elsewhere.

I plan on running virtual machines in vmware so the extra ram is for that

Share this post


Link to post
Share on other sites

I just finished building a WHS2011 server using the Asus P8H67-M EVO board. It uses the same LAN chip that the P8P67 uses. It is not an Intel Lan chip. It is a Realtek® 8111E.

The Intel LAN chip is only used on the P8P67-Pro, P8P67-Evo, and P8P67-Deluxe. The standard P8P67 and P8P67-LE use Realtek LAN chips.

In my case, the driver wiould not install if I used the Asus setup utility since it did not recognize WHS. I manually found the setup utility within the folder structure and ran that instead. Has worked great.

Share this post


Link to post
Share on other sites

I just finished building a WHS2011 server using the Asus P8H67-M EVO board. It uses the same LAN chip that the P8P67 uses. It is not an Intel Lan chip. It is a Realtek® 8111E.

The Intel LAN chip is only used on the P8P67-Pro, P8P67-Evo, and P8P67-Deluxe. The standard P8P67 and P8P67-LE use Realtek LAN chips.

In my case, the driver wiould not install if I used the Asus setup utility since it did not recognize WHS. I manually found the setup utility within the folder structure and ran that instead. Has worked great.

sorry I didn't realize there was just a P8P67 - I have a P8P67 pro

Share this post


Link to post
Share on other sites

Your board has the Intel 82579 LAN chip. Did you try the Intel driver directly from their website. I believe any driver for x64 systems are the same. Here is a link for the Windows Swerver 2008 R2, which is the same as the Win 7 x64 Driver. Download the PROWinx64.exe driver and try that.

INTEL DRIVER

Share this post


Link to post
Share on other sites

Your board has the Intel 82579 LAN chip. Did you try the Intel driver directly from their website. I believe any driver for x64 systems are the same. Here is a link for the Windows Swerver 2008 R2, which is the same as the Win 7 x64 Driver. Download the PROWinx64.exe driver and try that.

INTEL DRIVER

Yup - tried that. I Windows Server 2008 R2 also so I may try that too.

Share this post


Link to post
Share on other sites

Hmm... that's odd. I was able to load the Ethernet drive on a P8P67-M Pro board, but it really took some wranging to get it to work. Once you're in setup where it notifies you that your drivers aren't working, you need to CTRL-ALT-DEL and start Task Manager so you'll be able to see the desktop. Then manually install the driver by opening up Device Manager, looking for the NIC card, and manually pointing Windows to find the driver on the ASUS DVD. You have to do this roundabout way of installing drivers because ASUS' mobo utility refuses to install on any server OS. It's one of the reasons I swapped that board for a MSI board (the other reason is that a board with an H67 chipset is much better suited for a server since you don't need to have a separate video card installed).

Share this post


Link to post
Share on other sites

I got it working by telling it I wanted to pick the driver, selected Ethernet devices, selected Intel and then selected the 82579LM driver and it was happy.

Edit: I have the P8P67 Pro with the Intel LAN chip

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now



Upgrade to a WGS Supporter Account to remove this ad.



  • Posts

    • I had no problem with Windows 10.  However, I just completed the anniversary update and now the "Connector" won't run to conclusion.  It backs itself out and reports an unspecified error.
    • Apologies if I'm being stupid, but I'm having great trouble understanding how Lightsout backup and the Server Essentials 2012 backup work together (or fight with each other). I find the Lightsout documentation on this very unclear, and various threads have left me no wiser. I'd appreciate some help! Here's the setup: Lightsout is running nicely on the server. Before backups were set up, I established that the server hibernated when the clients were switched off. The server woke up when a client was powered up. (This behaviour broke when backups were set up.) The server is Essentials 2012, with a number of client laptops: a mix of Windows 7, 8 & 10. The Essentials backup window is 22:00 - 07:00. No backup settings are currently made in Lightsout. Here's what I'd like to achieve: At the end of the working day all the clients are put to sleep or hibernate (or switched off completely, I don't care which). Ten minutes after that, Lightsout hibernates the server. Sometime during the night (22:00 - 07:00) the server wakes up, then wakes up the various clients in turn, backs them up, and puts them back to sleep / hibernate / shutdown (I don't care which). Here's what actually happens (when I look at the uptime chart the next morning): At the end of the day (about 17:15) the clients are put to sleep / hibernate. (I tell the team not to shut down their client laptops because I assume the server can't wake a completely shut down client - is that correct?) The server does not hibernate. Approximately 90 minutes after the clients were put to sleep / hibernate, they all wake up simultaneously (around 18:45, but I don't know why this happens). The clients then stay awake all night. Later, from 22:00, some of the backups take place (but not all of them). The backups are spread wide apart in the 22:00 - 07:00 window with lots of time when nothing is going on at all. The clients do not go back to sleep / hibernate after their backups. ...can anyone suggest what combination of settings I should be using to get the desired behaviour? Here are the sort of things that are confusing me, but I can't find definitive answers (and each experiment I do takes 24 hours to give any results!): I know I can specify clients' individual backup times in Lightsout, but I don't know how long a client's backup will take, so I could have backups overlapping each other and causing a traffic jam. Should I worry about this? If I set Lightsout backups, what do I set for the Essentails backup window? What if it's not long enough to get all the backups done? If I make settings in the Lightsout backup dialog do I have to complete everything in that dialog box? Does this make the Essentials 2012 backup settings redundant? What about the Essentials 22:00 - 07:00 backup window, does that matter any more? I tried setting client backup times in Lightsout with an end action of 'sleep'. The backups didn't happen at all and clients all spontaneously went to sleep in the middle of the working day (the server / clients clocks all match, I checked). Can Lightsout wake up a client laptop that is completely shut down? Thanks for reading this long post and sorry if these seem like stupid questions. I already have WHS2011 / Lightsout running perfectly on another setup (where my backups take place during the day), but nocturnal backups are a new level of complexity for me!
    • Christopher wrote:  << And to clarify, if you want multiple backup drives to be cycled offsite, you MUST connect all of them at the same time when you set up the backups. >> I'm not clear about this. To the best of my recollection, I never connected both of my backup drives to the server at the same time,  For test purposes, I just initiated a recovery (using the WHS Installation Disk) with each of them hooked up.  The one that has been offsite and the one that backed up last night were both found by the "Repair an existing installation" procedure.  Perhaps I'm misreading your clarification.
    • Please check if task scheduler is still working. If not use this tool here https://repairtasks.codeplex.com/ If that does not help you may try to reinstall WHS Connector.
    • My WHS v1 (home build) starting misbehaving and finally needed a new system disk.
      After lots of threads, trial and errors, AF and non-AF drives, and lack of the Server Reinstallation choice it has finally progressed.
      Weeks of frustration. My recent attempts proceeded well but all ended up without the rebuilding of the Storage Pool (6 drives).
      The drives are detected and show up as "not added" in Server Storage and as "non managed" in Disk Management.
      There is no C:\fs on the SYS volume.
      It appears that the RebuildPrimary stage of the reinstallation, mentioned by some posters, was not successful. Has anyone found a way to force the rebuilding of the Storage Pool on reinstallation?
      I have tried X: Files v1.5.5 and the original Microsoft Disk with the same outcome. [My next step will be to migrate the "shares" and "folders" manually - it would have be quicker to have done this initially.]
       
  • Popular Contributors