Accedi
Microsoft.com
 
Microsoft
 
 
 
Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
Microsoft >
> 
> 
Install Failure

Con risposta Install Failure

  • sabato 17 febbraio 2007 20:41
     
     
    Registrati per votare
    0

    My install from the Served failed to end up in a working system.  The actual setup on the server seemed to go just fine, but when I installed Computer Connect on my main machine, I got an error that the Server was not found.  I repeated this twice and got the same message.  I then went to the server, reattached monitor, mouse & kb and went to Device Manager.  It showed that drivers were not installed for my NForce 4 MSI K8N Diamond motherboard, ie there were no drivers for network adaptor, ide controller etc.  I assumed the information in the Server DM was correct, so I loaded the motherboard drivers onto a thumb drive and then loaded them via checking the Load Drivers check box.  Again the install seemed to go just fine but when I went to install the client software, I saw exactly the same thing as before.  I am suprised that drivers for the nforce 4 motherboard were in included on the install DVD.  I would have thought that quite of few of these boards would have been found among the 1,000 testers within MS who tested prior builds.  I was obviously also suprised that even when I used the thumb drive to provide the necessary drivers, that the setup failed.  I will file a bug report and in the meantime hope that someone can help me figure out how to install this build.  Otherwise, I guess I will wait for another build :(

    Aaron Monroe

     

Tutte le risposte

  • martedì 20 febbraio 2007 17:05
    Moderatore
     
     Con risposta
    Registrati per votare
    0

    What specific drivers were you not able to install?  Did you try the Windows Server 2003 version of drivers?

     

    After checking Nvidia's website, it looks like the AMD version of that motherboard supports Windows Server 2003 and also notes, (AMD ONLY).

     
  • martedì 20 febbraio 2007 17:20
     
     
    Registrati per votare
    0

    Joel,

    I had a similiar experience. I also have an nforce 4 based motherboard. The network drivers aren't part of the WHS install image. This is a real pain because you have to go to another computer and create a CD from the download at Nvidia's website so they can be installed on the server. Getting a full breadth of network drivers (basic support) would be very beneficial before you ship this thing. To compound this the documentation that is available on Connect tells you to install WHS then remove the monitor/keyboard/mouse. You don't know until you try to install the Client SW that the server isn't on the network.

     
  • martedì 20 febbraio 2007 17:23
     
     
    Registrati per votare
    0

    During the first install I mistakenly installed the Vista driver....not fully recognizing that WHS was based on Server 2003.  When I realized that 2003 drivers were the right ones I installed them from DM on the existing install and they worked just fine.

    Thanks.

    Aaron

     
  • martedì 27 febbraio 2007 13:18
     
     
    Registrati per votare
    0
    I'm having this same issue with nvidia nic card.  Server does get its ip address assigned but, none of the PCs can see the server.  Do you have the link to nvidia's driver?
     
  • martedì 27 febbraio 2007 15:47
    Moderatore
     
     
    Registrati per votare
    0
     inlvnv wrote:
    I'm having this same issue with nvidia nic card. Server does get its ip address assigned but, none of the PCs can see the server. Do you have the link to nvidia's driver?

    If the server is getting an IP address, then it's probably not an issue with NIC drivers. (Are you sure it's getting one? If the IP address you're seeing is in the 169.254.xx.xx address space, then you're probably not getting an address unless that's the address space your DHCP server is set to allocate from). A couple of things you can try:
    • Check the status of your firewall software on both WHS and your home PCs
    • Try accessing the server's shares by IP address: \\12.34.56.78
    • Shut down all of the computers on your home network except your WHS, then start them back up. (I have seen issues where Windows Networking gets confused as to which machine on the network is in charge of browsing, and this should correct that by forcing the WHS to be the master browser.)
    Keep us posted on your progress, and we'll try to provide additional help.

     
  • mercoledì 28 febbraio 2007 16:08
     
     
    Registrati per votare
    0
    thanks for your help.  I've tried the above, upgraded router firmware and anything else I could think of.  Server is being assigned the correct ip address, in my case, 192.168.1.100.  It however, cannot access the router or the web, one reason I'm unable to activate the WHS.  My laptops, wired or wireless, also cannot find the server during the connector software install.  I am still thinking it is the built in nforce network card and/or the driver and am about ready to pickup a new card.
     
  • mercoledì 28 febbraio 2007 19:52
     
     
    Registrati per votare
    0

    I am having a similar problem.  My WHS install seemed to go fine.  I am used to installing Win2K3 Server so when the install completed I checked if drivers had been installed for all the components and noted that the Intel 10/100 Ethernet adapter did not have a driver loaded.  This was a little surprising as the Intel 10/100 Ethernet chip is an extremely common part.  So, I installed it manually, using a Win2K3 driver.

    The WHS system now has IP 192.168.0.12, my client has IP 192.168.0.3.  I can ping between them and even browse from the client to \\192.168.0.12\software and copy the Connector software over to the client.  However, when I install the Connector software on the client, it reports that it cannot find the WHS system!  Even if I supply the IP and try to manually connect it fails.  Any ideas why this could be?

     
  • mercoledì 28 febbraio 2007 20:14
    Moderatore
     
     
    Registrati per votare
    0
     Joe Gruher wrote:

    I am having a similar problem. My WHS install seemed to go fine. I am used to installing Win2K3 Server so when the install completed I checked if drivers had been installed for all the components and noted that the Intel 10/100 Ethernet adapter did not have a driver loaded. This was a little surprising as the Intel 10/100 Ethernet chip is an extremely common part. So, I installed it manually, using a Win2K3 driver.

    The WHS system now has IP 192.168.0.12, my client has IP 192.168.0.3. I can ping between them and even browse from the client to \\192.168.0.12\software and copy the Connector software over to the client. However, when I install the Connector software on the client, it reports that it cannot find the WHS system! Even if I supply the IP and try to manually connect it fails. Any ideas why this could be?


    If you can ping and browse by IP I'd say it's definitely not the server itself, but rather a network configuration issue of some sort. This has been bugged on Connect, and I think there's some additional information there that may help you to resolve this issue.

    Please keep us updated; there's probably additional assistance that we can provide.
     
  • giovedì 1 marzo 2007 11:40
     
     
    Registrati per votare
    0
    I don't believe the server itself was ever a problem, other than Microsoft not providing all possible nic drivers, I think the nvidia nic driver itself was the problem.  Anyway, after trying the latest nvidia nic driver, I gave up.  I bought & installed a linksys nic, and install went fine and working.  I'm one happy camper.  Now onto next problem.
     
  • giovedì 1 marzo 2007 18:46
     
     
    Registrati per votare
    0
    I had a problem with drivers and becuase i couln't install my network driver, my install failed. It was not the server 2003 part of the installation that failed though, it was the Home Server specific addons that had failed. To fix this, install the drivers, put the CD in the drive and reboot. Don't boot from the cd though. When Home Server starts, it should then log itself on and finish the installation