Computing.Net > Forums > Windows NT > Windows NT4 and Teaming

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Windows NT4 and Teaming

Reply to Message Icon

Name: plantolf
Date: December 4, 2007 at 21:58:00 Pacific
OS: NT4
CPU/Ram: 1.8GHz 4GB Ram
Product: 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



Sponsored Link
Ads by Google

Response Number 1
Name: Jennifer SUMN
Date: January 10, 2008 at 14:10:47 Pacific
Reply:

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.


0
Reply to Message Icon

Related Posts

See More


How to find disk size wit... Disable Shut Down Option ...


Use following form to reply to current message:

Login or Register to Reply
LoginRegister


Sponsored links

Ads by Google


Results for: Windows NT4 and Teaming

SBS Windows NT4 and remote desktop www.computing.net/answers/windows-nt/sbs-windows-nt4-and-remote-desktop/21894.html

Dual Booting NT4 and windows 98 SE www.computing.net/answers/windows-nt/dual-booting-nt4-and-windows-98-se/18175.html

Secrets on Windows NT4 CD :-) www.computing.net/answers/windows-nt/secrets-on-windows-nt4-cd-/22161.html