Přihlásit
 
HlavníKnihovnaCertifikaceDownloadPodporaKomunitaFóra
Zdroje informací pro profesionály v oboru IT >
> 
> 
Replacing NIC

Traitée Replacing NIC

  • 5. května 2012 12:38
     
     
    Přihlásit se a hlasovat
    0

    I have replaced the NIC in my server running VMM 2012.  When I open the console, I get a connection error.  It is a name resolution error.  The IP information on the interface has been set static to match the old NIC.  Is there a way to get my connection back short of re-installing the VMM server?

    Any help would be great and thank you in advance.

    D.W.

     

Všechny reakce

  • 5. května 2012 12:47
     
     
    Přihlásit se a hlasovat
    0
    I should also add that the console connection is failing on the local machine.  It is not from a remote computer which just adds to my confusion.  I am attempting to connect to localhost:8100 when I get the connection failure.  

    D.W.

     
  • 7. května 2012 14:59
    Moderátor
     
     
    Přihlásit se a hlasovat
    1

    VMM relys on DNS lookups as well as a SQL connection. Where have you placed your SQL server in this environment for VMM? Are you able to get a successful connection to your SQL server and your VMM database by using SQL management studio or SQLCMD?

    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

     
  • 7. května 2012 16:19
     
     
    Přihlásit se a hlasovat
    0
    SQL is on the local host as well.  I thought this might be part of the issue, but I am not sure how to correct it in SQL either.  Can you offer any advice?

    D.W.

     
  • 7. května 2012 18:12
     
     Odpovědět
    Přihlásit se a hlasovat
    0
    I was able to work it out.  I was trying to duplicate the ip address on the new NIC and that was confusing SQL.  I gave it a new static ip, and all is well.

    D.W.

    • Označen jako odpověď dlwilliams12 7. května 2012 18:13
    •  
     
  • 7. května 2012 18:18
     
     
    Přihlásit se a hlasovat
    0

    Hi D.W.

    Did you try writing IP Adrress:8100 instead of localhost:8100.

    Also you can check if any logon error seen in SQL - Management ,SQL Server Logs.

    Sincerely,

    Murat Demirkiran

    If the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. www.scvmm2012.com (TR Language) Please note that I'm not a Microsoft Representative or SpokesPerson.