Question about IBM Netfinity 3500 M20 8657 Server

1 Answer

Network & Speed Problem

My IBM servicer is very slow and it shows error at startup 5962 configuration change has occured
and can't detect network

Posted by on

1 Answer

  • Level 3:

    An expert who has achieved level 3 by getting 1000 points

    Superstar:

    An expert that got 20 achievements.

    All-Star:

    An expert that got 10 achievements.

    MVP:

    An expert that got 5 achievements.

  • Master
  • 2,567 Answers

I suspect that the network interface card failed, & that's why you get the error message. Try disabling it from the BIOS & see if the error message disappears. If it did, then you have a failing network interface card & need to install anew one.

Posted on Apr 14, 2009

1 Suggested Answer

6ya6ya
  • 2 Answers

SOURCE: I have freestanding Series 8 dishwasher. Lately during the filling cycle water hammer is occurring. How can this be resolved

Hi,
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need.
goodluck!

Posted on Jan 02, 2017

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

1 Answer

BMC Heartbeat blinking


Then you need to look into your System Event Log (SEL) entries to review the issue that is causing it. If the BMC is showing this heartbeat light, that means that there are critical errors piling up in the BMC's SEL log.

You can either do this through the BIOS (assuming IBM implemented that functionality here) OR you can log into your BMC over your OoB network. (Assuming SSH/telnet is not disabled and has a user configured.)

We can not help with this issue any further without SEL logs.

Jul 09, 2014 | IBM System x3200 M3 7328 Server tower ...

Tip

Understanding windows account lockups


Common Causes for Account Lockouts

This section describes some of the common causes for account lockouts The common troubleshooting steps and resolutions for account lockouts are also described in this section.

To avoid false lockouts, check each computer on which a lockout occurred for the following behaviors:

* Programs: Many programs cache credentials or keep active threads that retain the credentials after a user changes their password.

* Service accounts: Service account passwords are cached by the service control manager on member computers that use the account as well as domain controllers. If you reset the password for a service account and you do not reset the password in the service control manager, account lockouts for the service account occur. This is because the computers that use this account typically retry logon authentication by using the previous password. To determine whether this is occurring, look for a pattern in the Netlogon log files and in the event log files on member computers. You can then configure the service control manager to use the new password and avoid future account lockouts.

* Bad Password Threshold is set too low: This is one of the most common misconfiguration issues. Many companies set the Bad Password Threshold registry value to a value lower than the default value of 10. If you set this value too low, false lockouts occur when programs automatically retry passwords that are not valid. Microsoft recommends that you leave this value at its default value of 10. For more information, see "Choosing Account Lockout Settings for Your Deployment" in this document.

* User logging on to multiple computers: A user may log onto multiple computers at one time. Programs that are running on those computers may access network resources with the user credentials of that user who is currently logged on. If the user changes their password on one of the computers, programs that are running on the other computers may continue to use the original password. Because those programs authenticate when they request access to network resources, the old password continues to be used and the users account becomes locked out. To ensure that this behavior does not occur, users should log off of all computers, change the password from a single location, and then log off and back on.

noteNote
Computers running Windows XP or a member of the Windows Server 2003 family automatically detect when the users password has changed and prompt the user to lock and unlock the computer to obtain the current password. No logon and logoff is required for users using these computers.

* Stored user names and passwords retain redundant credentials: If any of the saved credentials are the same as the logon credential, you should delete those credentials. The credentials are redundant because Windows tries the logon credentials when explicit credentials are not found. To delete logon credentials, use the Stored User Names and Passwords tool. For more information about Stored User Names and Passwords, see online help in Windows XP and the Windows Server 2003 family.

noteNote
Computers that are running Windows 95, Windows 98, or Windows Millennium Edition do not have a Stored User Names and Passwords file. Instead, you should delete the user's .pwl file. This file is named Username.pwl, where Username is the user's logon name. The file is stored in the Systemroot folder.

* Scheduled tasks: Scheduled processes may be configured to using credentials that have expired.

* Persistent drive mappings: Persistent drives may have been established with credentials that subsequently expired. If the user types explicit credentials when they try to connect to a share, the credential is not persistent unless it is explicitly saved by Stored User Names and Passwords. Every time that the user logs off the network, logs on to the network, or restarts the computer, the authentication attempt fails when Windows attempts to restore the connection because there are no stored credentials. To avoid this behavior, configure net use so that is does not make persistent connections. To do this, at a command prompt, type net use /persistent:no. Alternately, to ensure current credentials are used for persistent drives, disconnect and reconnect the persistent drive.

* Active Directory replication: User properties must replicate between domain controllers to ensure that account lockout information is processed properly. You should verify that proper Active Directory replication is occurring.

* Disconnected Terminal Server sessions: Disconnected Terminal Server sessions may be running a process that accesses network resources with outdated authentication information. A disconnected session can have the same effect as a user with multiple interactive logons and cause account lockout by using the outdated credentials. The only difference between a disconnected session and a user who is logged onto multiple computers is that the source of the lockout comes from a single computer that is running Terminal Services.

* Service accounts: By default, most computer services are configured to start in the security context of the Local System account. However, you can manually configure a service to use a specific user account and password. If you configure a service to start with a specific user account and that accounts password is changed, the service logon property must be updated with the new password or that service may lock out the account.

noteNote
You can use the System Information tool to create a list of services and the accounts that were used to start them. To start the System Information tool, click Start, click Run, type winmsd, and then click OK.

Other Potential Issues

Some additional considerations regarding account lockout are described in the following sections.
Account Lockout for Remote Connections

The account lockout feature that is discussed in this paper is independent of the account lockout feature for remote connections, such as in the Routing and Remote Access service and Microsoft Internet Information Services (IIS). These services and programs may provide their own unrelated account lockout features.
Internet Information Services

By default, IIS uses a token-caching mechanism that locally caches user account authentication information. If lockouts are limited to users who try to gain access to Exchange mailboxes through Outlook Web Access and IIS, you can resolve the lockout by resetting the IIS token cache. For more information, see "Mailbox Access via OWA Depends on IIS Token Cache" in the Microsoft Knowledge Base.
MSN Messenger and Microsoft Outlook

If a user changes their domain password through Microsoft Outlook and the computer is running MSN Messenger, the client may become locked out.

In this case, since the user has multiple devices connected to the exchange at given time , if he changes the password without disconnecting the other deivices. The account would get locked. You can inform him disconnect all the devices from the exchange except for one machine to change the paswword and then reconnect other devices with new creditentials.


Thanks
Proton

on May 29, 2010 | Computers & Internet

1 Answer

In IBM system X3550 M3 server pxe e61 media test failure check cable error is coming and when i mam trying to install OS Partition will not show. pls give me solution.


This sounds like you are asking two different questions. PXE booting would be the way you would begin installing or loading an operating system. "Media test failure" errors would indicate a lack of network connectivity on the network interface that you're trying to PXE boot from.

You go on to mention an OS partition not showing... So did you resolve the PXE media test failure issue?

Your question is unclear and unanswerable in it's current state. BE CLEAR, CONCISE AND SPECIFIC.

May 26, 2014 | IBM Computers & Internet

1 Answer

Getting an error on console which repeats fairly regularly. Ideas? See content below event: Carrier check failure from node local:.lurker CSMA-CD station CSMACD-0


"The "carrier check" means that you have a network problem or a network transceiver or a transiever cabling problem. The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) protocol senses the network carrier as part of the IEEE 802.3 communications signalling, and your configuration is reporting an error.
You have a network problem, in other words.
Please contact your hardware support organization, as it would appear that you have a network problem, a network transceiver configuration or hardware problem, or a transceiver cabling problem."
Copied from here http://h71000.www7.hp.com/wizard/wiz_7105.html
Is relevant though.

Sep 15, 2013 | Compaq AlphaServer 1200

1 Answer

Slow cursor


Either CPU usage reaches 100% to perform a disk operation or to read the Interrupt. Check the Event Viewer for Specific Errors. You can verify it using the Task or Process Manager. A Sudden increase of the CPU usage. Typically servers are configured to allocate the CPU for the Background Services. So it can happen. You should not change it.
The other things is your Mouse interrupts (IRQs) are not compatible with another Device such as a Network card you have. (Most probably a network card) That is a common issue. You have to check the compatibility of your Devices.
Other Scenarios:
Scan the System for Spyware.
Clean the mouse connectors.
Try booting into safe mode, getting into device manager, deleting the mouse drivers and rebooting will solve the issue as well.
Hope this will help. You can check the IRQs on the web. Please feel free to ask for further help.
Please rate the answer as well
Thanks for using Fixya!

Jul 08, 2010 | Dell Computers & Internet

1 Answer

IBM fan error


I have updated all the firmware of the server using latest updates
and after restar it work properlly . waw my problem solved.

Dec 30, 2009 | IBM x3400 Server

1 Answer

IBM Server Information


It depends on what you do with the server, a server may be just another computer or a great help.
You can use your server as a Web Cache server, this means that the server will storage all the webapges your users access, so, when somebody wants to open a webpage the server will download only the updated parts of the webpage, that will save time and the users will think everything is faster.
Yet a server won't give you a faster internet conenction per se, it just optimized your resources, a server can also be a firewall or an antispam, so your network won't have undesired traffic coming from internet, so less trafic, faster network ^_^ .

Yet again, if you only buy a server, then plug it into your network and turn it on does not make anything. You will need to install/configure diferent solutions (sometimes you will need to buy them).
I recommend you to go with Linux, it is free, open source and there is plenty of documentation out there.

Mar 12, 2009 | IBM Netfinity 4000R 8652 Server

6 Answers

Restarting


Check below things:
1) Check Primary DNS server ip in TCP IP Configuration
2) Stop Unwanted services from start up
3) Run Chkdsk /R command from command prompt and restart the server. It will check your harddrive and recover data.

Regards,
karik

Nov 21, 2008 | IBM x3400 Server

Not finding what you are looking for?
IBM Netfinity 3500 M20 8657 Server Logo

Related Topics:

257 people viewed this question

Ask a Question

Usually answered in minutes!

Top IBM Computers & Internet Experts

Brian Sullivan
Brian Sullivan

Level 3 Expert

27725 Answers

Les Dickinson
Les Dickinson

Level 3 Expert

18333 Answers

Donald DCruz
Donald DCruz

Level 3 Expert

17129 Answers

Are you an IBM Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...