My recommendation is to call Dell if the server is still under support.
They should walk you through the process.
It saved me lots on time when getting my first few PEs back form disaster.
Good Luck!
By the way, the HP ProCurve switches have 802.3ad LACP is enabled by default.
No configuration needed when the NICs are teamed using this protocol.
Thanks again for all your help!
By the way:
After a longer review of the servers, we have noticed a marked increase in response times...
How busy are your servers?
Our main file servers gets hit big time all day with very large 30-40MB. I noticed quicker response time on the large files after making the change.
Well well well.
It seems I have configured the teams incorrectly.
Doing a LOT of research has lead me to the conclusion that the teams should be configured as
802.3ad Link Aggregation
Thank you for all your help!
ADB100
We are hoping to increase the bandwidth each server can use. From what I understand, the fault tolerance approach will not accomplish this. True or am I misinformed?
Still researching and gathering information.
Both the Intel PROset and BACS have the ability to test the network switch's configuration. This configuration test passes on all 3 switches from all 4 servers.
I am reading the some switch configuration may be necessary.
However, I can't seem to...
Thanks for the tips Andy. I am the network team as well at our location!
We do have a consultant with whom I will discuss these issues as well.
Should the network see 2 NICs or only 1 when load balancing?
What configuration should be used on the switches (HP ProCurve 26xx, 28xx, and 41xx?
NIC Teaming - How should the network see them?
We are in the process of teaming the NICs on all of our PowerEdge 17xx, 26xx, 28xx and 29xx series servers and have noticed an interesting situation when scanning the network.
All servers are running Server 2003.
All NIC are imbedded.
All virtual...
You shouldn't have to put the entire UNC path.
\\domaincontroller\netlogon\foldername\logon.bat
But everything after netlogon should be there.
foldername\logon.bat
Make sure the path in the profile and permissions on the folder are correct.
\\domaincontroller\netlogon\foldername\logon.bat
The profile should have: foldername\logon.bat
Thanks for the reply but nothing about what you've described seems to apply.
It happens even after the 50th log on.
Log on scripts do not run when this happens.
Logging off then back on has (from what we can tell) always worked.
Argh...
Environment:
Windows XP clients and Windows Server 2003 Active directory infrastructure.
Problem:
After logging on, users' desktops will not load. The PC just sits there with the blue background. The logon scripts do not run.
Ctrl-Alt-Del works.
Logging off and then back on will cause the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.