Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Subject: Windows NT4 and Teaming

Original Message
Name: plantolf
Date: December 4, 2007 at 21:58:00 Pacific
Subject: Windows NT4 and Teaming
OS: NT4
CPU/Ram: 1.8GHz 4GB Ram
Model/Manufacturer: Proliant ML570/G2
Comment:
Experienced an issue with an NT server that we have had for years that has been working without issue. The Server was origninally created by vendor and it had static IP addresses outside our local LAN on both NICs. The NICs appear to have originally been teamed (fault tolerant) at our local site with a local LAN address that was statically assigned to the Team. Only one NIC was used in the team and the second NIC was never plugged in yet it still maintained its original static IP. We could ping the team ip, the app was fine and all has been good for a very long time. Connectivity to the app was lost after the server rebooted recently. After the reboot, we noticed the Team was disolved and the original static IP address for NIC 1 changed back to the original address when we first got the server from the outside source. We changed the NIC 1 IP back to our LAN ip, reteamed the NIC and the device was pingable but the app still did not work. We discovered that putting back the original static IP that came from the vendor, rebooting, and then recreating the team and assigning the local LAN static IP corrected the issue. I am not sure why the orignal static IP from the vendor was still assigned to the physical nic and was since corrected only after we brought it back to original state and then re-teamed. Secondly, the only thing that was done immediately prior to all this was that I was reviewing the adapter and protocol settings tabs (not changing anything)and then clicked okay out of the networking window. I know NT is a bit flaky in that I have seen by just reviewing these settings often causes the rebinding of protocols progress bar to appear after you click okay and present you with a "restart for changes to take affect" message. I don't know if this is related but I don't think it is a coincidence. They are related but I don't know how.

Thank you,

/paul


Report Offensive Message For Removal

Response Number 1
Name: Jennifer SUMN
Date: January 10, 2008 at 14:10:47 Pacific
Subject: Windows NT4 and Teaming
Reply: (edit)
Is there a question in there? Might have better luck requesting Justin delete this post, and you can repost in the Networking Forum (if you're asking for help with that part of this.)

Life's more painless for the brainless.


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Windows NT4 and Teaming

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software



Version Tracker Pro
Keep your software current and secure, effortlessly

Click Here for a Free Scan

Driver Agent
Automatically find the latest drivers for your computer.
Click Here for a Free Scan



The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC