Lost internet connection..."A connection time out occurred"

I've read a number of recent threads blaming Lion for lost wireless internet connections. I wish my problem was that simple.
I have an AT&T furnished Siemens SpeedStream 4100 modem connected via ethernet cable to a Netgear 3500 router providing a wireless network. This configuration worked without problem for over six months serving an iBook G4 (OS X 10.4) replaced by an iMac (OS X 10.7) in mid August, Lenovo Thinkpad (Windows 7), iPhone 3GS, and occasionally a MacBook (OS X 10.5) and a MacBook Pro (OS X 10.6). Then last week my iMac lost internet connectivity and displayed a dialog box saying:
"Could not join NETWORK NAME. A connection timeout occurred."
At the same time, my iPhone lost its WiFi connection to my network, and could not reconnect; and the Thinkpad could no longer find my wireless network.
Thinking the problem was with the Netgear router, I substituted my 6 year old Apple Airport Express in the same configuration, but with a different wireless network name. (I had used this network setup successfully for over five years before replacing the Airport Express with the Netgear router in February.) The Airport Express network worked on both computers and my iPhone for a couple of days before I again lost internet connectivity exactly as I had with the Netgear router.
I called AT&T, thinking the Siemens modem must be at fault, since a problem with that one device seemed more likely than successive failures of two different routers within a few days of each other, or a simultaneous problem with a Mac, PC and iPhone. AT&T said their modem checked out problem free. I have now connected my iMac directly to the Siemens modem with an ethernet cable and have a problem free wired internet connection.
I need my wireless network. Any thoughts on what happened to my WiFi?

AppleSince86 ... we have this same problem with a wired version of 802.1x
It appears if a user updates their password (perhaps their login screen prompts this to do this)... the underlying eapolclient will still use the old outdated password to reauthenticate upon the next x min refresh interval.
This will basically kick the user off line.
Two things could really improve this process:
1) When the operating system reauthenticates for network access... use the absolute most current version of a users password
2) Timeout handling seems much more wonky in 10.7 / 10.8 ... could probably shorten all of the timeouts up a great deal... no need to wait 30 seconds error out... in reality... if you haven't heard back in 5 seconds, you're not going to.
Unfortunately, I haven't found any configuration files to control this from our end... it appears to be the compiled behavior of the apple code

Similar Messages

"connection time-out occurred" when my mac goes to sleep.

When My macbook goes to sleep I get a "connection time-out occurred" when I try to connect to the internet. and I have to restart my mac and restart the router. The is always a BT hotspot page displayed on the screen.
I have a 2011 macbook pro. This happens on my son's as well. he has the same model. he recently got a new retina display macbook and there hasn't been any problems. this doesn't happen on our phones either.
-Thanks for any help

I don't think the post can be edited after 10 or 15 minutes, what madking can do is ask host to remove it from this forum.
In addition to my own post, here are the correct link.
try to reset PRAM and SMC to refresh your macbook hardware behaviour:
http://docs.info.apple.com/article.html?artnum=2238\
http://docs.info.apple.com/article.html?artnum=303319
Good Luck

TNS:Connect time out occur

Hi:
I have an error message no matter how I login for SQLplus? TNS:COnnect time out occur. from what I read it has to do witht he URL? in what way?
thanks,
Mary

Hi,
Use the CONNECT_TIMEOUT_<SID_NAME>=100 in your listener.ora.
thanks
srinivas.

I am having Macbook Pro, I have recently tried updating my operating system to OS Yosemite, but after that its giving problem in connecting to Wifi. The error is "Connection Time out Occurred". Its getting connected by Ethernet cable.

I am having Macbook Pro, I have recently tried updating my operating system to OS Yosemite, but after that its giving problem in connecting to Wifi. The error is "Connection Time out Occurred". Its getting connected by Ethernet cable.

Take each of the following steps that you haven't already tried, until the problem is resolved. Some of these steps are only possible if you have control over the wireless router.
Step 1
Turn Wi-Fi off and back on.
Step 2
Restart the router and the computer. Many problems are solved that way.
Step 3
Change the name of the wireless network, if applicable, to eliminate any characters other than letters and digits. You do that on your router via its web page, if it's not an Apple device, or via AirPort Utility, if it is an Apple device.
Step 4
Run the Network Diagnostics assistant.
Step 5
In OS X 10.8.4 or later, run Wireless Diagnostics and fix the issues listed in the Summary, if any.
Step 6
Back up all data before proceeding.
Launch the Keychain Access application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Keychain Access in the icon grid.
Enter the name of your wireless network in the search box. You should have one or more "AirPort network password" items with that name. Make a note of the name and password, then delete all the items. Quit Keychain Access. Turn Wi-Fi off and then back on. Reconnect to the network.
Step 7
You may need to change other settings on the router. See the guidelines linked below:
Recommended settings for Wi-Fi routers and access points
Potential sources of interference
Step 8
Make a note of all your settings for Wi-Fi in the Network preference pane, then delete the connection from the connection list and recreate it with the same settings. You do this by clicking the plus-sign icon below the connection list, and selecting Wi-Fi as the interface in the sheet that opens. Select Join other network from the Network Name menu, then select your network. Enter the password when prompted and save it in the keychain.
Step 9
Reset the System Management Controller (SMC).

Cannot connect to WIFI - 'connection time out occured' but also says 'no ip address'

Hi,
I've searched the web and found endless issues with the wifi router / etc of the Imac Lion system. On the same wifi network we have a mac book (leopard I think), a pc laptop (which I am using now) and 2 phones + my brand new Imac with Lion osx. The first 4 items all connect with no problems.
I tried some of the sollutions here but it even made it worse as I now not have any connection at all!
http://support.apple.com/kb/HT4628
When I try to connect trhough systems preferences/network I get the message that my password is incorrect and that there is no IP address. Password is definitely correct. When I try to connect from the symbol in the right top corner - I get the message 'connection time out occured'
I am a bit of a Mac dummy ... any help is really appreciated.
Thanks
Billie

Hi BDAqua,
Thanks a lot for getting back to me.
Not so sure what your first questions means - or how to check this?
I tried joining other Wi-Fi network:
If I choose security 'WPA Personal' i get the message: connection time out
If I choose security 'WPA2 Personal' or 'WEP' i get the message@ no network found
hmmmm any suggestions? Thanks so much
Billie

My Mac book pro keeps saying "connection time out occurred" I have a 2011 pro with all the latest updates. It keeps doing it and it really annoys me! Please help!

My Mac book pro keeps saying "connection time out occurred" I have a 2011 pro with all the latest updates. It keeps doing it and it really annoys me! Please help!

Take each of the following steps that you haven't already tried, until the problem is resolved.
Step 1
Restart the router. Many problems are solved that way.
Step 2
Change the name of the wireless network, if applicable, to eliminate any characters other than letters and digits. You do that on your router via its web page, if it's not an Apple device, or via AirPort Utility, if it is an Apple device.
Step 3
From the menu bar, select
 ▹ System Preferences... ▹ Network
Click the Assist me button and select Assistant. Follow the prompts.
Step 4
Back up all data.
Launch the Keychain Access application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Keychain Access in the icon grid.
Enter the name of your wireless network in the search box. You should have one or more "AirPort network password" items with that name. Make a note of the name and password, then delete all the items. Quit Keychain Access. Turn Wi-Fi off and then back on. Reconnect to the network.
Step 5
You may need to change other settings on the router. See the guidelines linked below:
Recommended settings for Wi-Fi routers and access points
Potential sources of interference
Step 6
Make a note of all your settings for Wi-Fi in the Network preference pane, then delete the connection from the connection list and recreate it with the same settings. You do this by clicking the plus-sign icon below the connection list, and selecting Wi-Fi as the interface in the sheet that opens. Select Join other network from the Network Name menu, then select your network. Enter the password when prompted and save it in the keychain.

"Established" connections do not time out.

We have Netscape Directory Server 4.15running on Windows 2000. Our problem is that "established" connections do not time out. The result is that over time, the system runs out of ports/sockets, and the system fails to respond to queries.
Is there any patch or NT tuning available to resolve this issue. I have seen countless message threads in various vendor forums relating to this issue with NS LDAP server.
Any help would be appreciated.

Hi Philippe,
I think you are referring to the bug 557007 existing on DS 4.15 and fixed on 4.16.
Details of this bug from the DS 4.16 release note:
PR_Accept Failed Error Messages in the Logs
In DS 4.15 a regression defect was introduced in which all connections would not be closed and left in a CLOSE_WAIT state. In this case all available file descriptors/handles would eventually be used up. PR_Accept failed error messages would appear in the logs and the server would be non-responisive. This regression is fixed. (557007)
I know that there was a hotfix released on Solaris but do not know if such hotfix existed for Windows. Anyway, as specified by the DS Sustaining people, a hotfix is supported until the next release including that fix is out... and DS 4.16 is available now.
Hope this answers your question.
Cheers / Damien.

TS1368 I can't connect to the iTunes store with my Apple TV. I can see what movies are on offer but when trying to access my account i am advised "Can't connect to server" (times out).

I can't connect to the iTunes store with my Apple TV. I can see what movies are on offer but when trying to access my account i am advised "Can't connect to server" (times out).

I have the same problem with my 3rd gen Apple TV. I can preview iTunes movies, stream from my Mac, Airplay from my other devices but I cannot rent a movie on iTunes. Every time I try I get "Can't connect to ITunes" and "Unable to sign in". Had technical support review the problem over the phone and they agreed to send me a new one. Same problem. Interestingly enough my 2nd gen Apple TV works just fine.

Time out occurred while waiting for memory resources

Team,
I am have Microsoft SQL Server 2008 SP1( 10.0.2734.0) 64bit with application being SCCM 2007
I am getting below error in SQL error log ::
Error 8645: Severity 17, state 1
A time out occurred while waiting for memory resources to execute the query in resource pool ‘internal’. Re-run the query.
At first glance, i thought that it is issue of query not getting enough memory.
Searched on google but could not get way to resolve it or issue creating factor.
Chetan

Well,
Upgrade is what client is not willing to go for as of now.
They have rebooted the server and as of now, their SCCM application is working fine ( Not sure how reboot has solve the issue). We are not getting the above mentioned error also in SQL Log.
Looks like, rebooting server has cleared the memory jam.
Chetan
Restarting sql server service cleared buffer cache and any such query holding or requesting more memory so issue disappeared. You just delayed the issue not solved it. Next time dont reboot find out the cause . If you want to check whether your SQL
Server requires more memory have a look at below counters in link
http://social.technet.microsoft.com/wiki/contents/articles/22316.sql-server-memory-and-troubleshooting.aspx#How_to_test_that_your_SQL_server_is_facing_memory_crunch
If your say to business about what are drawbacks on running unsupported version I am sure they will apply SP3. There are loads of fixes and its quite possible your error may be related to any such fixed issue.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Distiller Start Error, Time-out occured

We are using Acrobat distiller 7 in our Formscape/Bottomline
Project. The incoming file is a pdf from JDE OneWorld XE. WHen Formscape tries to create the pdf, it has an error that says "Distiller start error. time-out occured."
Has anyone else had this issue? What could be causing it? and How do I fix it? Distiller 9 doesn't work with Formscape/Bottomline. I haven't tried 8

This forum is for issues relating to Distiller Server, not Acrobat Distiller. Please repost in the Acrobat Windows forum.

WLS 8.1 SP5 Message bridge doesn't refresh connection after idle time out

Hi,
I am seeing in the log after enabling the debug flags that message bridge intermittently stops refreshing the connection without logging further info and causing a production failure.Bridge is forwarding the message from WLS 8.1..5 DQ to the remote MQ 6.0 queue.
Below is the snippet which doesn't come in the log which suggests that bridge stops refreshing the connection.
<BEA-200027> <Bridge "CASLDNSenderBridge" works in asynchronous mode and has not received messages for the predefined maximum idle time. The connections to the adapters will be interrupted and reestablished.>
The above message does appear everytime but intermittently it stops and the messages put after this leading to the exceptions.The bridge has been configured in asynchronous mode and the idle time out is configured as 60 secs.
Can somebody please let me know if there is any known issue with 8.1 SP5 where message bridge stops refreshing connection intermittently or how to debug this further.

I would normally suggest raising the issue with support, but I recall hearing that 8.1 is nearing the end of its support cycle, so I'm not sure that's an option for you. Other options:
- try upgrading to a newer SP, or better yet, a new version of WebLogic
- try changing to synchronous forwarding
- examine thread dumps from when the bridge appears to be stalled
- post the exception that bridge is throwing when it tries to connect
- try patching MQ (the problem could be on the MQ side, and perhaps an older version of the bridge may not be fully capable of handling all of MQs minor quirks)
- write a program to (A) detect inactivity on the src destination, and (B) somehow restart the bridge and/or all of WL when this occurs
Tom

Airport will not connect to wifi - time out

Hi, I have an iMac that will not connect to my network. I get the greyed out network signal in the menu bar. When I try to connect to my network (it has a black network signal icon) it asks for the password and then times out trying to connect.
The modem is working because I can connect with my MBP.
I have re-booted, repaired permissions, booted, deleted com.apple.airport.airportutility.plist, re-booted.
No luck.
The internet connection cutting out has been happening for a while - it usually comes back after a restart.
Anyone know of anything else I can try?

robcub wrote:
deleted com.apple.airport.airportutility.plist
That file has nothing to do with connecting to a Wi-Fi network, but only with AirPort Utility.
Anyone know of anything else I can try?
You might try resetting your connection settings using the steps listed in this message:
http://discussions.apple.com/thread.jspa?messageID=10695921&start=1
They're not guaranteed to solve the problem, but they'll only take a minute or so to try.

RCA Connection Pool idle Time-Out takes no effect !

My question description goes here.
According to JCA specification, I developed my 'ManagedConnectionImpl' class from the interface 'ManagedConnection'. I realize the 'destroy()' function to send out logout request to the EIS.
Then I deployed the connector in Sun Java System Application Server, I noticed there are two parameters in Connection Pool part, they are:
1. Idle Timeout. It said it's the maximum time that a connection can remain idle in the pool. I assume the connection will be removed after the specific time expired and before it's removed it will call the recallable function, 'destroy()', in my concrete class, 'ManagedConnectionImpl'.
2. Pool Resize Quantity. it said it's number of connections to be removed when pool idle time expired.
I am weird about it. I think EIS had itself session control strategy, if the specific session time-out expired, it will invalidate this session. So I think we will set 'Idle Timeout' in application server to be shorter than the EIS session time-out. If the 'Idle Timeout' in application server expired, it should remove all connections inside otherwise maybe the connection with invalid session will exist! (the background knowledge is our system will return back soap fault when it meets invalid session, so the invalid connections will not be removed by switching on your configuration item, 'On Any Failure')
So I set "inital and minimum pool size" to 8, "maximum pool size" to 32 and "Pool Resize Quantity" to 32. (I expect AS to remove all when pool idle time expired)
After deploying, I send out requests at the first round and wait for the time expired but I can't see the desired logout requests from pool automatically even one. Firstly I guess if my recallable function definition is wrong but when I shut down the Application Server, the desired logout requests are sent out from pool automatically. So I think my recallable function definition is workable.
What's your comments on it?
P.S.
I am using Sun Java System Application Server 8.1.
Thanks in advance!
BRs
/Leo

I have had following test to ensure I sent out notification to listener.
[#|2005-08-23T16:14:25.061+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
It's in managed env!|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
enter matchManagedConnections() !|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
try to find a matching and existing one, reuse it!|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
Found a matching and existing one, reuse it!|#]
[#|2005-08-23T16:14:25.495+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
tearDown() is called, the application-level connection is released!|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
enter calling close() of managed connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
Start calling close() of managed connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
start to notify the listener the completeness of connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
notify the listener the completeness of connection successfully.|#]
Whether it's related with the initial and minimum number parameter? Although I found it will not be created during AS start-up and will be created at the first request.
Whether it shall be kept to meet the minimum requirement? I have failed to set it to 0.

HP Color LaserJet CP1520nw will not connect to network (time out repeatedly)

My HP LaserJet CP1520nw won't connet to my wireless router upon installation, no many how many times I've been asked to connect it to the computer via a USB printer cable. I uninstalled and reinstalled all software, and each time I try to set it up for wireless connectivity by connecting my computer and the printer via a USB printer cable, it gets to 99% installed on the progress bar and sits there until it times out. I suspect one of the follow but am open to other ideas from those more knowledgeable:
1. Is the printer locked onto some old, initial configuration from a previous wireless network that needs to be purged of addresses, etc. before it can accept the new ones?
2. Could my WPA WPA2 PSK AES encrytion be messing it up? Are the modern firmware and updates designed to accept these ? I never have gotten to a screen where it asks for my encyption key or even a WPS pass phrase. What to do if so?
3. Could Church Lady be correct and that it is Satan preventing the installation? If so, what icons does he use to watch out for and will my Norton anti-virus and malware quarantine him to Hell automatically or does it require manual enforcement?

Hi @Marvalina1968,
Welcome to the HP Forums!
I noticed that your HP Color LaserJet CP1520nw will not connect to network with Windows 7. I am sorry to hear this, but happy to help!
First to answer your questions:
It is possible the printer could be locked to an old configuration and needs to be reset.
I don't think your WPA WPA2 PSK AES encrytion could be messing it up, unless you got some really strange characters in your password.
Your Norton antivirus, could possible be causing the installation to fail.
Please take a look through the following guides:
'Printer is offline' Message Displays on the Computer and the HP Printer Will Not Print.
Printer Does Not Maintain Wireless Connection.
If the guides do not resolve the issue, please try the following:
Uninstall the software. Uninstalling the Printer Software.
Clean boot the computer. How to perform a clean boot in Windows.
Disable any antivirus programs. Disable antivirus software.
Disable any firewall programs. Turn Windows Firewall on or off.
Re-install the software. HP LaserJet Full Feature Software and Driver.
Hope this solves your problem, and have a good day!
RnRMusicMan
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to say “Thanks” for helping!

Mac Pro does not wakeup 1 of 3 connected monitors: Philips times out

Hi,
(Setup)
I use a Mac Pro from 2014 (End 2013, AMD Firepro, D700 Graphics, 6core, 1TB SSD, 32MB, actual OSX Yosemite 10.10.2).
Connected are three monitors:
Philips BDM 4065 UC (40 great inches) via mini DP to DP cable
2x Dell 2410 (vertical/pivot to the sides of the 40" screen)
(Problem)
The setup is a dream for me, with one glitch:
when the Mac goes to sleep, all monitors nicely sleep with it. Waking the Mac up again, brings the Mac up and the Dells but not the Philips. It tries to get up (a bit of backlight to be seen), then shows a message that it goes to sleep again.
(Troubleshooting so far)
I experimented with it:
- power cycling the monitor brings it back into business
- pulling the DP cable temporarily does the job too ... sometimes
(Assumed root-cause)
Today I believe I found the reason:
In a forum sb. complained that the Philips takes long to wake up. Ok! The Dells that work are back ... instantly.
I tried this: wakeup, wait two seconds, put the Mac to sleep (mouse into active corner) and wake it up immediately.
The description sound a bit like "dance around the tree three times at full moon", but it works. What I believe that happens:
Fail:
- the Mac wakes up
- the Dells are awake instantly
- the Philips slowly wakes up
- the Mac gets impatient about the Philips and times out waiting for the monitor, stopping the signal supply
- the Philips falls back into sleep (and displays this as a message)
Workaround:
- the Mac wakes up, Dells wake up
- waste two seconds, while the Philips is still trying to wake up
- hammer the Mac back into sleep, and wake it up again
- the Philips is so slow it doesn't even notice this "brutal shaking" of the Macs wake-state
- the activite resets the wake-up-timeout of the Mac giving the Philips effectively enough time to report "ready" before even the second wake-up times out.
- et voila: a fully awake set of monitor
Now the big question:
I this timeout that the Mac on wake-up waits for a Monitor to become ready a configurable item? Can I extend this period by a few seconds to get my dream setup actually working? I fear I won't be able to make Philips solve the long wake-up time, so I check on the Apple side.
Thanks in advance.

So update. Boot camp now works...somehow. Not sure how I fixed it but this is what I did that lead to it. As you asked I tried to make a boot drive on a USB for OS X Mavericks, But the App store would not let me download it. So instead I made one with OS X Yosemite. After witch I shut it down, pulled the USB and restarted. At witch point I got a gray screen. I then restarted and opened the startup manager. It only showed a install and a restore drive. Tried restore, but it just brought me back to the gray screen. At witch point I opened disk utility and repaired my main HD, and restarted. Still gray screen. So then I booted in safe mode witch brought me to my account login (and my screen flashed a bit). After I logged in I restarted again. Witch once again brought me back to gray screen. So I tried reseting my NVRAM with no success. Started in safe mode again and went to my start up disk and selected my main boot drive and restarted. All returned to normal and boot camp now works. Not sure what I did to fix the problem as i'm not that computer savvy but thanks for all your help and I hope you can gather some information from my random desperate attempts to get my computer running normally again.
In the end it all worked out
thanks again

Lost internet connection..."A connection time out occurred"

Similar Messages

Maybe you are looking for