Ghost Solution Suite

 View Only

  • 1.  Client can not connect to the server with a teamed NIC

    Posted Jun 01, 2007 06:46 AM
    Ive installed GSS 1.1 on a HP server (dedicated for management) with 2 onboard NIC's.
    The 2 nics are teamed as one virtual NIC.
     
    The problem is that the clients cannot seem to receive the broadcast data from the server when i start a session.
     
    Anyone ever teamed 2 nics before?


  • 2.  RE: Client can not connect to the server with a teamed NIC

    Posted Jun 02, 2007 06:35 AM
    Network adapter teaming
     
    ProLiant server customers look for improved network uptime and better network throughput. HP networking adapter teaming meets both of those needs. It improves network uptime by protecting the network in the event of a network failure. This protection prevents ProLiant server clients from losing connectivity. HP network adapter teaming also offers better network throughput by distributing traffic efficiently across ProLiant server ports.

    A team consists of two to eight ports that function as though they were a single NIC. This virtual NIC appears to the system as a single physical address and a single IP address. Should one NIC in this team fail, the remaining NICs assume the failed NIC's traffic, providing resiliency. This fault tolerance is provided by all the configurations of teams available. When teamed, each NIC can also share the network traffic load, increasing the network throughput. Each type of team provides varying levels of traffic management, (called load balancing), and all teams provide fault tolerance.
     


  • 3.  RE: Client can not connect to the server with a teamed NIC

    Posted Jun 06, 2007 08:19 AM
    I have a Proliant with teamed NIC's running Ghost Console and have been unable to get an image task to work.
     
    The error file reports error code "10030 unable to establish contact with session".
     
    Symantec support told me this was a McAfee issue (blocking IRC ports on the server), but i confirmed that this wasn't the case.
     
    I ran a packet trace on the client and confirmed it was receiving the broadcast. the problem was with client to server initiated communication.
     
    I disolved the team, set the IP details on each (seperated) NIC, and now the image process completes just fine.
     
    I am looking for a fix, as I cannot have a production server running on a single NIC.


  • 4.  RE: Client can not connect to the server with a teamed NIC

    Posted Jun 06, 2007 08:33 AM
    Gord,
     
    I have the exact same problem here. NO fix yet.
    Support doesnt help me much tho.
     
    How did you get the ghostcasting to work after dissolving the teamed NIC's?
    I've tried that aswell...still no luck
     
    Meanwhile im still waiting for an answer...from support
     
     
     


  • 5.  RE: Client can not connect to the server with a teamed NIC

    Posted Jun 06, 2007 08:43 AM
    Hey hummr
     
    That's all I did - just disolved the team. Maybe you have more than one issue?
     
    Can your ghost console talk to your client at all? I was able to do a Remote Client install and take an inventory - it's was only the image process that failed.


  • 6.  RE: Client can not connect to the server with a teamed NIC

    Posted Jun 06, 2007 08:58 AM
    Hi Gord...
     
    The only problem i hv is getting a imagetask to work. The console can see the clients (online), configuration refresh, remote installation of a client...all works perfectly.
     
    I even connected the clients to the same switch as the server just to make sure its not the networkcomponents...
     


  • 7.  RE: Client can not connect to the server with a teamed NIC

    Posted Jun 06, 2007 09:02 AM
    Are you running any AV software? Support did initially say that the error number I reported was due to ports 6666-6669 being blocked on the server, and if so to add the ghostsrv.exe process as an exception.
     
    If not, I am out of ideas I am afraid.


  • 8.  RE: Client can not connect to the server with a teamed NIC

    Posted Jun 06, 2007 09:09 AM
    Yup...confirmed that its not the AV client...:smileysad:
     


  • 9.  RE: Client can not connect to the server with a teamed NIC

    Posted Jun 12, 2007 11:13 AM
    updated the NIC driver, firmware and the Teaming Utility...
     
    seems to hv done the trick...
     
    iT WORKS!!! grrr....finally!:smileymad:

    Message Edited by hummr on 06-12-200708:13 AM