Conference mvblab::sable

2608.0. "Second CPU in 2100 causes TCP/IP to fail" by COMICS::SYMONDSK () Fri May 23 1997 13:24

    Dear All,
    
    Could anyone possibly throw any ideas or thoughts on the following
    problem:
    
    Customer has an Alpha 2100 4/275 running Windows NT 3.51 + SP4 and when 
    he add's a second CPU (another 4/275) it fails to allow TCP/IP to 
    function, however netbeui works perfectly and they have changed from
    thin wire to utp but the problem still occurs. As soon as the second
    CPU is removed all works fine and TCP/IP behaves itself.
    
    I have asked what the rev levels are, and the following was relayed:
    
            CPU id      = 21064
            Rev         = 3
            System Rev  = 0x0
            Speed       = 274Mhz
            Memory      = 192mb
    
            Firmware    = V4.44 - 951204.1210
            Console Rev = V4.43
    
    Since last speaking to him he has applied service pak 5 and has put the
    second CPU in slot 0 and left the original main CPU out of the machine
    and has been running for about 5 hours so far without any problems and
    I have also asked that V4.50 be applied as soon as I can get it to him.
    
    So at this moment in time I am lost as to why this second CPU is
    causing IP to fail.
    
    Any ideas ?
    
    Thanks in advance,
    Kevin Symonds
    (CSC - Basingstoke)
    
    

   Contact Microsoft -- it's their package, and this needs to be worked
   from their end back, if necessary, to the hardware folks.