WTR54GS Intermittent failure mode

I have a WTR54GS and have used it successfully for many years (about 5 years) as a travel router. For the most part it has worked like a charm.
Recently it has exhibited a strange problem. It will suddenly *stop* working as a wireless router, and the lights flash in a rhythmic pattern with about a 2 second cycle time. I can't figure out what causes this, or what to do about it. The big security button, which is normally an amber color in normal use will flash white every two seconds, and the other lights flash at different, regular times. It is clearly displaying some sort of distress code, but I don't know what it means.
It will, however, sometimes fix itself. I left it running all night without problem, but then about 8 in the morning, it suddenly goes into this mode. At that time it becomes undetectable as a wireless network -- it no longer appears in the windows wireless lan list. I sat and wateched, and about 10 minutes later it stops doing that, and becomes a wireless lan again. At other times I have unplugged it, and plugged it back in. Sometimes when you plug it back in, it works, and sometimes it continues in the failure mode. It is not overheated ... I have unplugged it for long periods (e.g. 1 hour) and found it still failing when plugging it back in.
Right now, however, it is working fine, and I am submitting this message using it in wireless mode.
I have firmware version 1.0.15 which is the latest version listed on the Cisco site.
Does anyone have any idea what the flashing lights means? OR what to do about it when it happens?

Sounds like it's dying. You can try upgrading/reflashing the firmware and resetting the router.
The box said windows xp or better... So I installed Linux!

Similar Messages

Apple Mail and Google Apps (personal domain) - 554 554 Denied Mail Delivery Subsystem (Intermittent Failure)

Hello,
I am having problems with my Apple Mail and Google Apps and I don't know what to do. I have been using apple mail with google apps for a few months now with no complications. In the last week I have recieved a handful of messages from the Mail Delivery Subsystem citing error "554 554 Denied". I know that the emails I have tried to send to are real emails and are entered correctly. I tried to send directly from google apps to one of these people today and it worked so I assume the problem is with Apple Mail, or is intermittent. Adding to my frustration is that it works with some people and not with others so it's hard for me to see exactly what is causing the problem.
Any ideas?
I'll include a copy of one of the Mail Delivery Subsystem emails I recieved - excluding the email address and message body.
Thanks for your help!
From: Mail Delivery Subsystem <[email protected]>
Subject: Delivery Status Notification (Failure)
Date: October 10, 2011 10:40:53 AM CDT
To: [email protected]
Delivery to the following recipient failed permanently:
    [email protected]
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 554 554 Denied (Mode: normal) (state 18).
----- Original message -----
Received: by 10.236.155.74 with SMTP id i50mr20817257yhk.23.1318261251237;
       Mon, 10 Oct 2011 08:40:51 -0700 (PDT)
Return-Path: <[email protected]>
Received: from [192.168.0.190] (c-66-41-33-96.hsd1.mn.comcast.net. [66.41.33.96])
       by mx.google.com with ESMTPS id n18sm26532559yhi.14.2011.10.10.08.40.49
       (version=SSLv3 cipher=OTHER);
       Mon, 10 Oct 2011 08:40:50 -0700 (PDT)
From: Mary Jo Bailey <[email protected]>
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: multipart/alternative; boundary="Apple-Mail=_08B0FA71-0443-40B4-AEAB-4056C662063D"
Subject: Re: Cleaning Quote
Date: Mon, 10 Oct 2011 10:40:47 -0500
In-Reply-To: <[email protected]>
To: "XXXXXX" <[email protected]>
References: <[email protected]>
Message-Id: <[email protected]>
X-Mailer: Apple Mail (2.1244.3)

For mail issue, I had the same problem. My mail password was different than my itunes password and when I changed mail to itunes password, it started working again. Not sure about the google apps issue.
hope this helps a bit.
Matthew

Failure modes in TCP WRITE?

I need help diagnosing an issue where TCP communications breaks down between my host (Windows) and a PXI (LabVIEW RT 2010).
The bottom-line questions are these:
1...Are there circumstances in which TCP WRITE, given a string of say, 10 characters, will write more than zero and fewer than 10 characters to the connection? If so, what are those circumstances?
2...Is it risky to use a timeout value of 1 mSec? Further thought seems to say that I won't get a 1000 uSec timeout if we're using a 1-mSec timebase, but I don't know if that's true in the PXI.
Background:
On the PXI, I'm running a 100-Hz PID loop, controlling an engine. I measure the speed and torque, and control the speed and throttle. Along the way, I'm measuring 200 channels of misc stuff (analog, CAN, TCP instruments) at 10 Hz and sending gobs of info to the host (200 chans * 8 = 1600 bytes every 0.1 sec)
The host sends commands, the PXI responds.
The message protocol is a fixed-header, variable payload type: a message is a fixed 3-byte header, consisting of a U8 OpCode, and a U16 PAYLOAD SIZE field. I flatten some structure to a string, measure its size, and prepend the header and send it as one TCP WRITE. I receive in two TCP READs: one for the header, then I unflatten the header, read the PAYLOAD SIZE and then another read for that many more bytes.
The payload can thus be zero bytes: a TCP READ with a byte count of zero is legal and will succeed without error.
A test starts with establishing a connection, some configuration stuff, and then sampling starts. The 10-Hz data stream is shown on the host screen at 2-Hz as numeric indicators, or maybe selected channels in a chart.
At some point the user starts RECORDING, and the 10-Hz data goes into a queue for later writing to a file. This is while the engine is being driven thru a prescribed cycle of speed/torque target points.
The recording lasts for 20 or in some cases 40 minutes (24000 samples) and then recording stops, but sampling doesn't. Data is still coming in and charted. The user can then do some special operations, related to calibration checks and leak checks, and those results are remembered. Finally, they hit the DONE button, and the whole mess gets written to a file.
All of this has worked fine for several years, but as the system is growing (more devices, more channels, more code), a problem has cropped up: the two ends are occasionally getting out of synch.
The test itself, and all the configuration stuff before, is working perfectly. The measurement immediately after the test is good. At some point after that, it goes south. The log shows the PXI sending results for operations that were not requested. The data in those results is garbage; 1.92648920e-299 and such numbers, resulting from interpreting random stuff as a DBL.
After I write the file, the connection is broken, the next test re-establishes it, and all is well again.
In chasing all this, I've triple-checked that all my SENDs are MEASURING the size of the payload before sending it. Two possibilities have come up:
1... There is a message with a payload over 64k. If my sender were presented with a string of length 65537, it would convert that to a U16 of value 1, and the receiver would expect 1 byte. The receiver would then expect another header, but this data comes instead, and we're off the rails.
I don't believe that's happening. Most of the messages are fewer than 20 bytes payload, the data block is 1600 or so, I see no evidence for such a thing to happen.
2... The PXI is failing, under certain circumstances, to send the whole message given to TCP WRITE. If it sent out a header promising 20 more bytes, but only delivered 10, then the receiver would see the header and expect 20 more. 10 would come immediately, but whatever the NEXT message was, it's header would be construed as part of the payload of the first message, and we're off the rails.
Unfortunately, I am not checking the error return from TCP write, since it never failed in my testing here (I know, twenty lashes for me).
It also occurs to me that I am giving it a 1-mSec timeout value, since I'm in a 100-Hz loop. Perhaps I should have separated the TCP stuff into a separate thread. In any case, maybe I don't get a full 1000 uSec, due to clock resolution issues.
That means that TCP WRITE cannot get the data written before the TIMEOUT expires, but it has written part of it.
I suspect, but the logs don't prove, that the point of failure is when they hit the DONE button. The general CPU usage on the PXI is 2-5% but at that point there are 12-15 DAQ domain managers to be shutting down, so the instantaneous CPU load is high. If that happens to coincide with a message going out, well, maybe the problem crops up. It doesn't happen every time.
So I repeat the two questions:
1...Are there circumstances in which TCP WRITE, given a string of say, 10 characters, will write more than zero and fewer than 10 characters to the connection? If so, what are those circumstances?
2...Is it risky to use a timeout value of 1 mSec? Further thought seems to say that I won't get a 1000 uSec timeout if we're using a 1-mSec timebase, but I don't know if that's true in the PXI.
Thanks,
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks
Solved!
Go to Solution.

There are a couple of issues at play here, and both are working together to cause your issue(s).
1) LV RT will suspend the TCP thread when your CPU utilization goes up to 100%. When this happens, your connection to the outside world simply goes away and your communications can get pretty screwed up. (More here)
Unless you create some form of very robust resend and timeout strategy your only other solution would be to find a way to keep your CPU from maxing out. This may be through the use of some scheduler to limit how many processes are running at a particular time or other code optimization. Any way you look at it, 100% CPU = Loss of TCP comms.
2) The standard method of TCP communication shown in all examples I have seen to date uses a similar method to transfer data where a header is sent with the data payload size to follow.
<packet 1 payload size (2 bytes)><packet 1 payload..........><packet 2 payload size (2 bytes)><packet 2 payload.......................>
On the Rx side, the header is read, the payload size extracted then a TCP read is set with the desired size. Under normal circumstances this works very well and is a particularly efficent method of transferring data. When you suspend the TCP thread during a Rx operation, this header can get corrupted and pass the TCP Read a bad payload size due to a timeout on the previous read. As an example the header read expects 20 bytes but due to the TCP thread suspension only gets 10 before the timeout. The TCP Read returns only those 10 bytes, leaving the other 10 bytes in the Rx buffer for the next read operation. The subsequent TCP Read now gets the first 2 bytes from the remaining data payload (10 bytes) still in the buffer. This gives you a further bad payload read size and the process continues OR if you happen to get a huge number back, when you try to allocate a gigantic TCP receive buffer, you get an out of memory error.
The issue now is that your communications are out of sync. The Rx end is not interpeting the correct bytes as the header thus this timeout or bad data payload behavior can continue for quite a long time. I have found that occasionally (although very rare) the system will fall back into sync however it really is a crap shoot at this point.
I more robust way of dealing with the communication issue is to change your TCP read to terminate on a CRLF as opposed to the number of bytes or timeout (The TCP Read has an enum selctor for switching the mode. In this instance, whenever a CRLF is seen, the TCP Read will immediately terminate and return data. If the payload is corrupted, then it will fail to be parsed correctly or would encounter a checksum failure and be discarded or a resend request issued. In either case, the communications link will automatically fall back into sync between the Tx and Rx side. The one other thing that you must do is to encode your data to ensure that no CRLF characters exist in the payload. Base64 encode/decode works well. You do give up some bandwith due to the B64 strings being longer, however the fact that the comm link is now self syncing is normally a worthwhile sacrifice.
When running on any other platform other than RT, the <header><payload> method of transmitting data works fine as TCP guarantees transmission of the data, however on RT platforms due to the suspension of the TCP thread on high CPU excursions this method fails miserably.

Intermittent Failure of incoming calls to Response Group

Hello,
We're running Lync Server 2010 and intermittently calls coming into the response group don't ring the attendant or take a long time to start ringing. We ARE seeing events in the event log pertaining to the LS Response Group Service as show below. I
haven't been able to find anything on this on TechNet or anywhere else. We are running all of the latest updates. Any help would be greatly appreciated!
Event Log
Log Name:      Lync Server
Source:        LS Response Group Service
Date:          11/22/2013 3:43:11 PM
Event ID:      31172
Task Category: (2001)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      vm-12-04.sipdomain.net
Description:
The workflow runtime encountered an error while connecting the call.
The workflow runtime encountered a critical error.
Failure occurrences: 9, since 11/21/2013 7:42:57 AM.
The last encountered error was from a workflow having the display name: Main RSP, the URI: sip:[email protected], and the GUID: 647cc313-9ea7-46a5-a153-3e5a164b9785.
Exception: System.InvalidOperationException - Accept Call activity '_actvAcceptCall' cannot run. The Call (AudioVideoCall or InstantMessagingCall) is not in the incoming state. The current state is 'Terminated'.
Inner Exception: -
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="LS Response Group Service" />
    <EventID Qualifiers="34769">31172</EventID>
    <Level>3</Level>
    <Task>2001</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-11-22T21:43:11.000000000Z" />
    <EventRecordID>276664</EventRecordID>
    <Channel>Lync Server</Channel>
    <Computer>vm-12-04.sipdomain.net</Computer>
    <Security />
</System>
<EventData>
    <Data>9</Data>
    <Data>11/21/2013 7:42:57 AM</Data>
    <Data>Main RSP</Data>
    <Data>sip:[email protected]</Data>
    <Data>647cc313-9ea7-46a5-a153-3e5a164b9785</Data>
    <Data>System.InvalidOperationException - Accept Call activity '_actvAcceptCall' cannot run. The Call (AudioVideoCall or InstantMessagingCall) is not in the incoming state. The current state is 'Terminated'.</Data>
    <Data>-</Data>
</EventData>
</Event>
Calls will begin to come in again after this but it appears the service is recovering from some type of failure state.
Thanks for any help!
RWK

Did this issue happen to multiple response group?
Did this happen to calls from PSTN calls?
This problem is mostly related with network issue.
The following is a similar thread for you:
http://social.technet.microsoft.com/Forums/lync/en-US/d0e53ab2-42e7-4d79-be01-b8770d508133/calls-to-workflows-fail
For further troubleshooting. You can use Lync Logging Tool to collect trace file on Lync Front End Server.
Lisa Zheng
TechNet Community Support

Intermittent failure to boot, flashing question mark or white screen

So, I've had two MacBooks with similar problems (I am a Mac consultant). The first one would intermittently boot to a white screen, often enough to be annoying. This current one is occasionally booting to a flashing question mark. My first thought is, of course, the hard drive, but in both cases the hard drive tests fine using SMART Utility, which is usually great at giving advance warning when a drive starts experiencing hardware errors.
On the first MacBook, the one with the white-screen boots, I tried reinstalling the system with no effect; replacing the drive eventually made the problem go away. The current MacBook, with the question-mark boots, has already had its drive replaced once, when the stock drive failed.
I will reseat the drive, which is all Apple could suggest. I just wonder if anybody else had experienced something like this and can offer any information about what might be going on.

Thanks for the reply. Aside from finding that holding the mouse button down at boot might cause a flashing question mark, I already knew all that. I will ask the owner if she is leaning on the trackpad button when she starts up her computer in the morning.
I've already reset the power manager and the PRAM; we'll see if that makes any difference. The puzzling thing here is that the problem is intermittent.
I also need to ask her if, when the computer does boot to the question mark, there has been a chime first. Somehow I think there has to be, for the system to have gotten as far as looking for a boot drive. I couldn't find anything useful in the logs; not surprising, since if it can't find a drive to boot to, it won't have anything to write a log to.
Again, the mystery is why the failure to boot is intermittent. If it happened every time, I'd know what to do!
Thanks
cavenewt

SGD 4 6 AD intermittent failures

Hello all
I have an issue with SGD 4.6....
The infrastructure:
2 SGD 4.6 in array config
1 AD for authentication
First time I had authentication to the AD and I saw the tree of the AD on the SGD and every thing worked fine, one day I just couldn´t get the tree.
The next day I found that I could autenticate with the AD in both servers, at the afternoon once again I lost auth in one of the array and a few minutes after on both servers, next day at mid morning I got authentication in one serverver, I restarted the second one and gained authentication again.
When i try to set up the authentication in the global conf during those outages I got this message.
*errorLDAP Connection Error
Failed to connect, no servers available[ dcexternal-srv.company.com.gt='javax.naming.AuthenticationException: GSSAPI [Root exception is javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Server not found in Kerberos database (7))]]'; ]*
If I change the user for autentication (I now is not the one to get acces i got this message)
LDAP Connection Error Fail to connect, invalid authentication credentials
I´ll apreciate any help with this issue, is killing me and I have a whole project waiting to solve this.
Regards,

Hi there,
The error:
GSSException: No valid credentials provided (Mechanism level: Server not found in Kerberos database (7))
means that SGD cannot find an authentication realm for the AD server being connected to and therefore cannot connect.
If your AD environment has more than one AD server check you have a domain_realm mapping in your krb5.conf file for the network domain company.com.gt. If the mapping is missing, assign an authentication realm to the company.com.gt domain.
If your AD environment has only a single AD server, were there any DNS outages around the time of the AD failures? DNS outages can mean that SGD cannot resolve the hostname of the server and therefore cannot work out a domain and/or an authentication realm to use when connecting to the server.
For the LDAP issue, you may need to reconfigure the search filter used to find users in LDAP as the default values are sometimes not adequate for AD. The following blog entry should provided more information on reconfiguring this value:
http://blogs.sun.com/danielc/entry/using_ad_as_an_ldap
Hope this helps,
-- DD

Intermittent failure to send mail and/or save sent...

Several times now I have sent mail & got no record of the sent mail - no settings change, just mail server behaviour.... I have set Mac Mail up for IMAP and asked to store sent messages on the server. Most times it is fine, but occasionally fails to save the sent message, although the message is delivered to the recipient.
More worryingly, and on random occasions, my sent mail is not even delivered - with no failure notice. BTYahoo server seems to deliver (goes ok) but then simply ignores or loses the mail, even though it appears in my sent mail folder. Other times I get no record of sent mail. Mac Mail doesn't seem to have read receipts as an option, so of course the only way to find it hasn't been delivered is when I speak or email again and am told it didn't arrive. Turns out that it fails to be received by all recipients, not just one, so seems to be a BTYahoo issue, not another mail server in the WWW.
Has anyone else discovered that mails sent aren't being received or stored? Or have ideas why this might be happening?
Certainly isn't acceptable mail server behaviour....
Cheers
Andy

I've been having problems with my BT Yahoo mail since day 1 (July 9th). It nearly always fails to send the first time but then sends fine the second time I try. For about an hour this evening I wasn't able to send or receive at all because of a bunch of acronyms that the server had stopped supporting.
I have no idea what's wrong or how to fix it. I just figured you'd like to know you're not alone.

Intermittent failure to boot after installing SSD

I have recently installed new RAM and an SSD in my late 2009 MacBook Pro, running OS X 10.6.8, and it now frequently hangs when I try to start it up. Here are details:
In recent weeks I noticed signs that seemed to point to a failing hard drive. I took the machine to a Genius Bar. The genius tried Disk Utility and a quick diagnostic and could not reproduce an error, but he noted many, many I/O errors recorded in a log file.
He said I probably had a failing disk, but it might be a cable issue. He gave me two options: leave the machine with Apple overnight to run diagnostics and perhaps repair if the problem was confirmed, or just take a chance and replace the drive myself, for less money and less downtime.
I went to a local computer store, and the salesman there noted that I was using relatively little disk space. He suggested that I swap my failing 160 G disk for a smaller, 120G solid-state drive, which happened to be on sale. I agreed and also bought some new RAM.
I installed the drive and RAM, partitioned the disk (with HFS journaling), and restored my files with Time Machine. For that day and the next, everything worked perfectly.
The second day after the installation, the system hung while starting up. The Apple logo appeared, the gray spinner appeared, and it just spun. I tried resetting PRAM. I tried safe restart. I started up from the install disk and ran Disk Utility: no problems found. I repaired permissions. I took out the new RAM and put back the old. In some cases after trying these steps, the system booted fine — once. In others, it would not boot the first time, but would boot on the second or third attempt. I reinstalled OS X and updated software. The problem persisted. I installed some freeware to enable trimming the new disk. No better.
I have booted many times in verbose mode. During the unsuccessful boots, there is usually a message "Bug: launchctl.c: 3557 (23930):6 ioctl(S6, SIO CAIFADOR_IN6, &ifra6) ! = -1". The next line is the command "fsck_hfs", and the machine hangs. Eventually it sometimes spits out "launchctl: please convert the following to launchd: /etc/mach_init.d/dashboardadvisory.plist". If I let it go for a long time, I sometimes come back to find a long string of I/O error messages, to the effect that media was expect to be there but wasn’t. I think every time I have gotten the launchctl message, it has booted successfully on the next try.
During the successful boots in verbose mode, everything happens so quickly that it is hard to say what is going on, but I don’t think it is running fsck_hfs. If it boots successfully and I give it a heavy I/O task, like doing a virus scan, everything works fine. If I run Disk Utility off the installation disk, it says the disk appears to be OK.
I started the machine in single user mode and ran fsck manually. It gave me reports similar to running Disk Utility, and told me the disk appeared to be OK. It then gave me the prompt for a new command. I typed "exit". It responded "logout". And hung.
One last thing: I just tried a couple of times to restart with the Apple Hardware test. Despite holding down the D key, the test failed to load, and after a long pause, the machine attempted a normal start-up.
Any insights?

Thanks, sanjampet, I have an old copy of Spring Cleaning, and I'm letting it sift through my files right now.
I have done some investigation on other forums, and there are some suggestions that the problem is associated with the make and model of drive that I installed. That is, this might not be an OS X issue so much as a hardware or firmware compatibility issue.
I bought the device on the recommendaiton of a salesman at a physical store, without consulting the manufacturer's webpages or online reviews. It turns out that many of those reviews are negative. It also turns out that although the manufacturer says that the device is suitable for Macs, the manufacturer does not yet offer a way to update to the most recent firmware unless the device is connected to a machine running Windows or Vista. And there are reports that some units out in the stores were shipped with outdated firmware, which might be the root cause of my problem. Or maybe not.
So here's the painful lesson: don't buy new hardware without first double-checking the specs, the support, and the reviews.
If anyone has a more hopeful insight into the problem, please let me know!

ICloud password not accepted, intermittent failure and must be reset each time

So, my wife is becoming manic depressant when she tries to use her phone, computer, whatever... on icloud. It will work fine for a week or two, then suddenly the password for the same account she has had no problem with for the last 4 years doesn't work any more. I then get called in to reset her password, re-sign in all of her devices, and she and I are happy once again. This has happened a ******** amount of times, (more than 10). I have went through the entire process of resetting all of the security questions... blah, blah... tech support... turn off, sign out all devices, blah blah... turn on, sign back in, on and on... update the computer, soft reset, hard reset, "upgrade" to the new stupid operating system that she really hates, blah blah, update the phone to an even worse OS,... on and on. Honest. I've tried everything. Everything is the latest model, and software version.
Does anyone out there actually know how to fix this intermittent problem? There is no solid pattern to the time intervals. It can happen within hours, or weeks of me resetting the password and signing in.
Lately, I have spent more intimate time with my wifes Apple devices than her, and this is very disturbing for me. (and her)

Hi,
Whilst Apple IDs that end in either @mac.com or @me.com they registration pages do not tell you that if you are going to be using it as an AIM Screen Name the password has to be 16 characters otr less. (This is an AIM server limit)
At some point you will need to update the password.
10:08 PM Friday; March 23, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Lion 10.7.3)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

HP Pavilion p6510f Desktop intermittent failures - Antec 25 430 WATT Power & NVIDIA GEFORCE GTX 650

After installing a new power supply and video card (Antec 25 430 WATT Power & NVIDIA GEFORCE GTX 650), my system became unstable. It worked fine for the first 3-4 hours then had a BSOD (blue screen of death) with kernel_data_inpage_error 0000007A and later a critical process failure 000000F4. I've done all of the tests listed on this page as well as removed and replaced the cmos battery:
http://www.faultwire.com/solutions-fatal_error/KERNEL-DATA-INPAGE-ERROR-0x0000007A-*1137.html
All of the tests passed and no problems were found and yet the system still fails after 3-4 hours of use.
So, I removed everything from my system and restored it to it's original settings. It seems to be back to normal now (but, we'll see for how long).
This experience has demoralized me. This is due to the fact that I've heard of others having difficulties trying to upgrade their systems. Seems like there is about a 50% success rate unless you know what works from past experience. I feel that the only way to get a system that has good graphics now is a well tested gaming box (PS3, XBOX, or Wii). Is there any recommended or possibly well tested setups for this type of system that could give me the quality of a GEFORCE GTX 650 without causing blue screens or cause instability for my computer?
Since this computer comes with ATI and AMD parts, I presume maybe getting an ATI or AMD graphics card would work? Regardless of the graphics card, the 250W power that comes with this system would most likely need to be replaced. Are there are any power supplys that you recommend or possibly tested?
I realize there are a few questions in this post, but I have one more. Are there any motherboard analysis tools to enusre nothing has gone wrong with the mother board? When the blue screens were occurring it seemed to make strange noises from the hard drive as it it were thrashing and after rebooting it would sometimes fail to recognize the existance of the hard drive as well. Since all of the hard drive tests were successful (I also ran SeaTools), this leads me to believe that the power is inssuficient, but I'm now fearful that if I upgrade the power it will only cause more problems.
A paying customer,
Zintage
This question was solved.
View Solution.

So, using the standard setup still makes strange noises at various intervals, but not as frequently. I have a bad feeling that it has caused disk drive problems based on the fact that:
1) Strange noises are now occuring during particular load times (although rarely)
2) Computer crashes (although, it no longer crashes now that I'm back in it's regular setup)
3) Occassionall it has really slow access times
These symptoms fall into the category of a failing drive based on the following site:
http://www.lifehack.org/articles/technology/how-to-tell-when-your-hard-drive-is-going-to-fail.html
I'm going to return the power supply and game card and look to investing in a new hard drive in case this one finally decides to go to valhalla.

E1000: Intermittent failure when uploading

This week, I activated AT&T's U-verse Internet service (which works well and faster than my previous DSL service). My problem deals primarily with uploading, as follows.
I'm a web developer. I routinely upload files to my server using FTP with Dreamweaver (CS3) on a Mac (OS 10.5). Since my switch from DSL to U-verse (which provided the Linksys E1000 router), half the time I attempt to upload a file or files to the server, the transfer goes quickly. Unfortunately, half the attempts I make get hung up; the progress bar moves verrrrry slowly, then stops and tells me that transfer failed becuse it timed out.
I've reloaded the Linksys E1000 software, hoping to fix this new problem. Sadly, that didn't correct it..
What might cause the E1000's intermittent uploading? What's a recommended fix?
Thanks, in advance.

Yea, I can't think of anything either. It's clearly not your router since you said that it didn't work when connected directly to your modem. Usually people don't have problems when they connect directly to their modem, but you said that it didn't work at all when you tried that. The other twist was that you said it worked a few times with the router connected.
If I were in this situation, I would reconfigure my ftp settings from scratch. If that didn't work, then I would contact the ftp server's host and tell them about my problems to see if they had any suggestions. And if that didn't work then I would contact ATT. I'm pretty sure the host would have a lot more information and solutions to fix this issue.
I don't work for Cisco. I'm just here to help.

WRT300N Intermittent Failures

I am having intermittent problems with a recently purchased WRT300N wireless router.
Wired connections ALWAYS appear to work OK. I am using a wired connection to compose this message right now.
Wireless connections work for a few days and then the wireless stops working for a few hours and then seems to "fix" itself. For example, according to the DHCP log on my router:
Wed, 28 Feb 2007 18:11:50 received DISCOVER from 00:17:AB:E9:6B:BC
Wed, 28 Feb 2007 18:11:51 sending OFFER to 255.255.255.255 with 192.168.1.101
... repeats every 20 minutes or so until ...
Sat, 03 Mar 2007 07:12:36 received REQUEST from 00:17:AB:E9:6B:BC
Sat, 03 Mar 2007 07:12:36 sending ACK to 192.168.1.101
... no further entries in the DHCP log ...
Its now 1840, so its been almost 12 hours with the router failing to communicate with other wireless devices. There may be a correlation to the router renewing its IP address with the ISP (according to the router status page, the current lease is 4 days), but I cannot be sure.
A scan using my other wireless devices find other wireless routers (on other channels), but not mine.
Yes, I have the latest firmware (0.93.9).
Yes, I have gone back to factory defaults after loading that latest firmware & set my network back up again.
Yes, I have reported it to the support team (Incident: 070224-010921) but they suggested the first two steps and fail to respond to any further inquiries.
Any suggestions on "fixing" this problem or more diagnostics I could do to help isolate it and get a firmware update (or new device)?
Thanks.
--Mark

magic25 wrote:
My question is, Are you using an N-adapter to your wireless computer?
Actually, I am having problems now with B/G.
and for you firmware...there is a new firmware...1.03.3
Sure enough there is a new version (dated Jan 11). Curious the web site only now shows that (and the response to my incident submittal referred to the older version as well).
Will be trying your (and saber_tooth's) suggestions but since it took four days to fail this last time, it will likely be a while before I have new news to report.

Intermittent failure to detect LCD screen on bootup on Satellite X200

For a while now my X200 has been suffering an intermittent problem with the screen. When powering on it will issue one long and two short beeps and then proceed to boot but without the display.
I normally power cycle a few times and find that it sorts itself out but this evening it didn't want to cooperate so I dug out a cable for my TV and used that as a monitor and sure enough the machine booted fine and after POST immediately switched to the onboard display again. Does anyone have any idea what is happening and why?
A bit more background.
This has been happening on and off for a good month or so now.
I have used a variety of drivers both WHQL latest, and LV2G releases, but they all have the same issue.
At the moment I am on the default version of most the drivers and am going through the process of appyling the upgrades having just clean rebuilt the machine due to other issues (in a separate thread) but immediately before the rebuild, the probelm was just as evident and all drivers were the latest so I don't think it is a driver related issue or at least not one that appears to be solved by any of the existing releases.

Sounds pretty strange. Have you checked your BIOS options? Perhaps you should set it back do default settings.
Or try and install the recent BIOS version.
If this does not help, and as I read you already have done a clean reinstallation with latest drivers, I would suggest you contact local ASP, as beeping sounds are not that normal.
They can tell you what those sounds mean.

Intermittant failure validating PEAP security

I have 2 devices using the WPC600N wireless adapter which are set up and working normally in a account that has the Cisco Radius server using WPA with TKIP data encryption & it's using PEAP authentication. I’m using windows Zero wireless to configure the adapter. XP Pro SP3 all updates current. One of the devices usually sits in one location while one roams around the facility, both successfully negotiates various access points and validates through a Radius server without issue. When one of the devices roams around the facility it is intermittently rejected by the Radius Server. It can take anywhere from a day to 3 weeks for it to occur but when it does the operator sees that status as indicating “validating” for the network adapter. I’ve determined that when this occurs the radius server is not recognizing my user name and password. If I re-boot the PC I'll get a pop up request to manually input the user name and password again and it will accept it and go on working from there once again to repeat the whole situation in a matter of days or within a week or two. It doesn't happen on the one that sits in one location even though it has to validate as it powers off and on regularly through the day, so I suspect the roaming has some effect. This is a large facility with multiple networks that are "bridged?" together for a continuous wireless environment. Multiple other devices are working normally in this facility. On the Radius server they will usually get an error stating "Radius Extension DLL rejected user" The IT staff at this location speculate that my PC or the adapter is "forgetting" it's user credentials because it asked for them to be input again upon a re-boot. I suspect that since the Radius server had not recognized me that the pc is naturally asking me to again input the user name and password like it did the first time I validated with it. (chicken before the egg problem) How can I determine if my device is sending the correct credentials and is getting blocked by the server or if my device is not sending the correct credentials over to the radius server? Any ideas what this error message really means or is it stating the obvious, hat I was rejected but not as to why I was rejected? One more thing, I configured my laptop with the smae set up and walked around the facility and it eventually gave me the same problem and caused the same error ont eh Radius Server further pointing to the problem being on the Radius server side or the network in general.
Any assistance at all would be greatly appreciated with this head scratcher, thank you in advance.

Hi Serge,
Thanks for your response it makes sense. The only problem I'll have doing this is that the Radius server and network belongs to the facility not my company. I'm the company that has the device that occasionally can't validate through their network security. Naturally they feel that their network is "perfect" without fail, unfortunately I think otherwise. Thus far I've configured 3 separate devices on this network one of which is my service laptop and they all fail in the exact same mannaer as they roam around the facility. To me this points in the direction of the network but proving it is the challenge. Particularly on my side. My next move is going to be to get a different network card, the Cisco AirNet card was suggested to me as possible a better fit since the network is a Cisco network and I was told that the Linksys card I'm using isn't Cisco ACS certified and the Cisco card is. Once I’ve done that I would have to wait and see if it fails again and if so I’ll hopefully have more leverage to push back on the facilities IT that there is an issue on their network.
Thanks,

SQR Intermittent failure

Hello all:I have written a complex dynamic query in SQR, which fails about 1-2% of the time in our production environment. After such failures, we merely execute the program again and it generally runs properly. In addition, we have not been able to recreate the error in either our development or test environments. The worst-case scenario generates a query of roughly 11,000 characters; however, it is failing when it is less than 2/3 that size.Has anyone encountered such an issue, and if so, how was it resolved. I checked our sqr.ini files SQLSIZE processing-limit, which is currently set at 4000. However, we are also using another run-time definition file that overrides that value to 28,000, which should be more than sufficient to handle the above-mentioned query. One would think that SQR would fail each time the query exceeds the configured limit.Could our issue be that SQR is not properly overriding the sqr.ini settings at run-time leading to some sort of memory leak? We are currently running SQR 8.0.1 on top of Oracle 9 and looking to upgrade to 8.3 in about three months. It is our hope that this potential is SQR or Oracle bug will have been taken care of, however, I would like to get to the root of the problem prior to then and avoid the hopes that it will mysteriously disappear.Any thoughts???Thanks,Steve

FYI, we have solved the problem by running the program via the SQT. I think there may be some memory leaks in the C SQR API...

WTR54GS Intermittent failure mode

Similar Messages

Maybe you are looking for