Toshiba Portégé M800-10C , eth0:timed out

So , i'm trying to install archlinux with the new archboot 2008.12 isos
Everything installed fine via a cd install (arch64), so i rebooted on my computer to find that internet via ethernet doesn't work.
Ethernet & Wifi worked just fine on linux mint or ubuntu 8.10
The boot-up process displays an "eth0: timed out" on startup, heres the output of lspci for ethernet and wifi :
07:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 12)
08:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
hwdetect --net
MODULES=(sky2 iwlagn iwlcore)
lsmod correctly shows that iwlagn and iwlcore are loaded
iwlwifi-5000-ucode is correctly installed
eth0 is correctly set as eth0=dhcp in /etc/rc.conf
running dhcpcd eth0 outputs :
eth0: dhcpcd 4.0.4 starting
eth0: broadcasting for a lease
eth0: timed out
Damn i want to use arch so bad :'( help !

mar00n wrote:P.S. I'd like to post the output of commands, but since I don't have internet access through Arch and I only have one PC, I have to reboot under windows to go on the forum...
Save the output to a file:
[karol@black ~]$ ifconfig -a > if.log
[karol@black ~]$ cat if.log
eth0 Link encap:Ethernet HWaddr 00:09:6B:F3:A8:42
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:939338 errors:0 dropped:0 overruns:0 frame:0
TX packets:251922 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1267079090 (1208.3 Mb) TX bytes:27331350 (26.0 Mb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:880 (880.0 b) TX bytes:880 (880.0 b)

Similar Messages

[SOLVED] Issue with eth0 (eth0: timed out)

Hi there people, just installed Arch on my PC (again). The first time I had no problems with this, but now it is really bothering me. Well, my PC only access the net via wireless, so I have no wired connection for it. Here's my /etc/rc.conf:
# /etc/rc.conf
eth0="dhcp"
wlan0="dhcp"
wlan_wlan0="wlan0 essid MySpot key ABCDEFABCDEF1234567ABCDEFC"
INTERFACES=(eth0 wlan0)
Well, everything is working fine, I can get access to the internet on bootup. My only concern is that my system is taking awfully long to boot. It takes about 1-2 minutes on "::Starting Network", then it shows me "eth0: timed out". Then it takes about 10 secs to start my wlan0 interface and the system finishes booting. I had previously installed Arch 2008.12, and the Starting Network only took about 10 secs to start my wlan0. I have already tried commenting out the eth0 line and putting a ! in front of eth0 on INTERFACES, but doing that only shows me an error message for my wlan0 and render my internet unusable on system bootup. So, my questions are:
1) Do I really need the eth0 interface for my connection (since I'm using wlan0 for wireless connection) ? Why can't I comment it out?
2) If I really need eth0, how can I make my boot time go faster, or how can I make it not time out?
Thanks in advance for any help given...
EDIT: problem solved, see Post 8 below for answers...
Last edited by gabscic (2009-03-25 03:40:43)

Thanks for answering. Well, I think eth0 is being detected correctly. Here is the output for ifconfig:
eth0 Link encap: Ethernet Hwaddr 00:18:F3:87:97:41
UP BROADCAST MULTICAST MTU: 1500 Metric: 1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:19
lo Link encap: Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU: 16436 Metric: 1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Link encap: Ethernet Hwaddr 00:15:AF:09:BC:E7
inet addr: 192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric: 1
RX packets:1903 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:615024 (606.6 Kb) TX bytes:1020 (1020.0 b)
wmaster0 Link encap: UNSPEC Hwaddr 00-15-AF-09-BC-E7-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric: 1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Well, I hope that can help. Searched the net and the forums, and every problem related to this is with people who are actually trying to use the eth0 interface for connection. In my case, I don't think I need it, I only need the wlan0. What I'm trying to do is get rid of eth0 while letting wlan0 work.

Monitor a TCP port but alert only if timed out X times

Hello,
I need to build a moniotr that will probe a TCP port but alert only if timed out X times
I was looking at Microsoft.SystemCenter.SyntheticTransactions.TCPPortCheckProbe module but it doesn't have this options
Thanks,
Marius

You can check
http://www.ghacks.net/2010/05/25/tcp-port-monitor-port-alert/
for TCP Port Monitor Port Alert

[solved]eth0: timed out

Hi,
I am having problems getting internet connection bia ethernet.
I have no way of posting the exact files from the arch box, but here is my rc.conf network part:
eth0="dhcp"
INTERFACES=(eth0)
ROUTES=(!gateway)
And i can not connect
It always says it timed out.
Last edited by Fork (2008-06-20 22:43:22)

What is your router's IP address? That will be your gateway's address, and before the "ROUTES=(!gateway)" line, you need to put this:
gateway="default gw 192.168.0.1"
where 192.168.0.1 is the router's IP address; yours may differ (mine is 192.168.1.1, for example).
and it should connect. Also, you should make sure that the "network" daemon is up and running and is in the DAEMONS section at the bottom of /etc/rc.conf.
Last edited by kclive18 (2008-06-20 17:17:13)

[SOLVED] Asus 1005PE ethernet | Atheros AR8132 | dhcpcd eth0:timed out

Hello, this was solved through the following process BUT:
pacman -Syu updated my system and kernel. After that update I needed
to reverse the line that I changed before in rc.conf. I change it back to
MODULes=() [removed !atl1c atl1e] which leads to atl1c being loaded
autmoatically. Seems they fixed the problem in a update.
These threads helped me:
( I )http://bbs.archlinux.org/viewtopic.php?id=78891
( II )http://www.ubuntugeek.com/howto-setup-n … aunty.html
Current driver for AR8132:
( III )AR81Family-linux-v1.0.1.6.tar.gz http://partner.atheros.com/Drivers.aspx
Hardware:
Asus eeePC 1005PE with Atheros AR8132 ethernet device.
uname -r:
2.6.30-ARCH
Problems:
eth0 not showing up at ifconfig
ethernet device not showing up at lspci
at boot error ar "Start Network"
dhcpcd: timed out
ridiculous count of errors Tx, Rx ..
Removing battery and power cord for a while and then booting without lan cable helped
recognizing the ethernet device at lspci (and eth0 at ifconfig if I remeber right). Plugging
the lan cable produced a high count of errors at Tx, Rx.
(II)
Get the driver (III) and get it ready(II):
tar -xzvf AR81Family-linux-v1.0.1.6.tar.gz
cd src
make
make install
(the note about "#define IRQ_HANDLED 1" (II) wasn't necessary for me. My guess is they updated the driver and it is no longer necessary.)
edit the /etc/rc.conf, prevent atl1c from loading, add atl1e:
MODULES=(!atl1c atl1e) [should look similar to this]
reboot
After reboot the error "dhcpcd: timed out" or "eth0: interface not found or invalid" was fixed,
"ping -c 3 www.google.com" was successful.
lsmod shows atl1e and ifconfig shows eth0.
I hope this is useful to someone, it took me a while to figure it out.
===================================================
O L D
===================================================
Hello,
I installed Arch yesterday on my Asus 1005PE and am trying to get online since.
Wired should be easier but there is a problem.
I am connecting through a router with DHCP. While booting it fails after
'Starting Network': 'dhcpcd: eth0: interface not found or invalid'
Same error when I enter '/etc/rc.d/network restart'.
ifconfig -a
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Link encap:Ethernet HWaddr 00:25:D3:D8:CF:CA
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmaster0 Link encap:UNSPEC HWaddr 00-25-D3-D8-CF-CA-00-00-00-00-00-00-00-00-00-00
[NO FLAGS] MTU:0 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lspci
( . . . nothing with Ethernet, just Intel, VGA, .. )
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
I think I saw the lan device recognised once, but rebooting doesn't help.
I read WPA encryption makes WLAN more complicated so I hope you can help me out with my wired connection.
- Felix
Last edited by phlex (2010-03-20 15:48:04)

This is already in my rc.conf:
MOD_AUTOLOAD="yes"
MODULES=()
USELVM="no"
HOSTNAME="newton"
eth0="dhcp"
INTERFACES=(eth0)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
DAEMONS=(syslog-ng network netfs crond)
I don't see lines missing there.
Unplugging the power cord and removing the battery for some minutes helped somehow (found that odd tip through google). I booted without the lan cable connected and the Atheros AR8132 / L1c was recognized.
Got a new problem then. /etc/rc.d/network restart leads to:
:: Stopping Network [DONE]
:: Starting Network [BUSY]
dhcpcd: timed out
[FAIL]
dhcpcd eth0 leads to:
dhcpcd: version 5.0.6 starting
dhcpcd: eth0: waiting for carrier
dhcpcd: timed out
Suprisingly the 1005HA has the same ethernet device and should be working out of the box..

Eth0 timed out after upgrade is driving me crazy!

I just updated my system, and my network has become unreachable, ifconfig shows some weird ip address and I'm REALLY lost here, did some research on the forums but nothing helped me...i think it is cuz of dhcpcd...i guess, added the -A option to it but did not work, and I also do not know how to downgrade the package to an older version to check whether that solves the issue..if someone could instruct me on what to do i'd really appreciate it....
well, thanks in advance for your answers, GO ARCH
Last edited by HighD (2007-11-05 07:19:30)

Hello could you please post here your rc.conf or network-profiles, also check daemon.log will by help full. If you use dhcpcd daemon, weird ip is assigned from /var/lib/dhcpcd/dhcpcd-eth*.info. So you could try remove that file, daemon will create new one.

TNS-12535: TNS:operation timed out

Hi,
Whenever we check Alertlog file according to regular health of Instance. We are facing the below issue very frequently
TNS-12535: TNS:operation timed out
ns secondary err code: 12606
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=172.17.100.108)(PORT=14375))
WARNING: inbound connection timed out (ORA-3136)

Hi,
Welcome to OTN form:
WARNING: inbound connection timed out (ORA-3136) please check following link: ORACLE DBA: inbound connection timed out (ORA-3136)
ORA-12535: TNS: operation timed out
Cause: The requested operation could not be completed within the time out period.
reference link: ORA-12535: TNS: operation timed out tips
Thank you

Inbound connection timed out and TNS:operation timed out in Oracle 11g

Hello All,
We are getting the below messages in alert log since yesterday... And we could not see any other messages other than this...Users also complaining slow response from DB,
Could any one please help me to resolve this ...? I believe in 11g inbound connection time out is deprecated ..isn't it ...?
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.2.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
Time: 18-NOV-2011 01:54:50
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.21.0.159)(PORT=4789))
Fri Nov 18 09:43:04 2011
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.2.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
Time: 18-NOV-2011 09:43:04
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12606
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.25.1.65)(PORT=50839))
WARNING: inbound connection timed out (ORA-3136)

889828 wrote:
Hello All,
We are getting the below messages in alert log since yesterday... And we could not see any other messages other than this...Users also complaining slow response from DB,
Could any one please help me to resolve this ...? I believe in 11g inbound connection time out is deprecated ..isn't it ...?
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.2.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
Time: 18-NOV-2011 01:54:50
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.21.0.159)(PORT=4789))
Fri Nov 18 09:43:04 2011
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.2.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
Time: 18-NOV-2011 09:43:04
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12606
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.25.1.65)(PORT=50839))
WARNING: inbound connection timed out (ORA-3136)The most common cause for this error is a firewall between clint & DB Server;
which allows packets on port #1521, but does not allow DB Server to use new high random port.

Connection to server on port 25 timed out

Can't send mail. Connection to the server "smtp.ca.astound.net" on port 25 timed out.
I keep getting this error when sending mail. I can receive mail but just can't send.
I noticed this problem sometime after installing the Security Update 2006-005, Security Update 2006-007 and Airport Firmware Update 5.7. I don't know that any of these are the cause but I'm trying to provide as much detail surrounding the problem as I can. I had been receiving and sending mail with no problem for the several years that I've had this set up and now I can't send mail.
I am using a 17" Powerbook running OS 10.3.9 and connecting wirelessly to an Airport Extreme. I'm using Apple Mail as my email software, but I have also tried to send through Entourage with no luck. I am using an email account and SMTP server provided by my ISP. I also have an old iMac running 10.3.5 that is wired directly to the Airport. I have an email account set up on the iMac and can't send from there either.
My ISP (Astound), who handles the cable modem, has said that they haven't made any recent changes on their side and confirmed with me that my account settings are correct. I even deleted my account and rebuilt it with no success. Although I am able to send email through webmail using my ISP's website. Based on that test they say that there aren't any problems on their side.
Are there some settings on the airport that may be affecting this? Any ideas on what I'm missing? I'm baffled.
PowerBook G4 17in, 1GHz Mac OS X (10.3.9)

Go to Apple Menu > System Preferences > Network, choose Network Port Configurations from the Show popup menu, and make sure that the configuration used to connect to Internet appears at the top of the list.
Also, try using a different method to connect to Internet, if possible, or connecting the computer to Internet as directly as possible, i.e. bypassing any routers that might be present, using an ethernet cable instead of wireless, etc., and see whether that makes a difference.
It could very well be that the problems are related to having installed a system update, usually not because of the update itself, but rather as a result of not having installed it properly, or having ignored Apple’s "Important: Please read before installing" warnings, etc.
Some (but not all) of the problems caused by not having installed an update properly can be fixed by (properly) reinstalling it. If you suspect a particular update could have a bearing on this, proceed as follows.
Verify/repair the startup disk (not just permissions), as described here:
The Repair functions of Disk Utility: what's it all about?
After having fixed all filesystem issues, if any, reinstall any updates that may not have been installed properly. In some cases, it may also be necessary or convenient to reinstall the Combo Update for the type of computer and the version of Mac OS X you’re using, unless this is the version of Mac OS X that came with your computer:
Mac OS X 10.3.9 Combo Update
Take a look at the following articles for guidelines on how to properly install system updates:
Troubleshooting installation and software updates
Installing software updates
Basically, you should verify/repair the startup disk before installing the update, no applications should be running while installing it, and you may experience unexpected results if you have third-party system software modifications (not normal applications) installed.

Can't sent mail. connection to server on port 25 timed out.

Can't send mail. Connection to the server on port 25 timed out. I keep getting this error when sending mail. I can receive mail but just can't send.
When I connect directly to the cable modem, thus removing the Airport from the set up, the mail sends fine. I recently updated the Airport with firmware update 5.7 and I'm wondering if there are some settings on the airport that may be affecting this? Any ideas on what I'm missing? I'm baffled.
I am using a 17" Powerbook running OS 10.3.9 and connecting wirelessly to an Airport Extreme. I'm using Apple Mail as my email software, but I have also tried to send through Entourage with no luck. I am using an email account and SMTP server provided by my ISP. I also have an old iMac running 10.3.5 that is wired directly to the Airport. I have an email account set up on the iMac and can't send from there either.

I tried changing the MTU on the iMac which is wired directly to the airport.(I have an old iMac running 10.3.5 and a Powerbook G4- the G4 connects wirelessly to the airport) I changed it to 1492 but didn't still wasn't able to send mail. I feel like I'm stabbing in the dark with this, is there a way to determine what the packet size should be?
MTU will vary with connection type. Cable and non-PPPoE, can use up to 1500, whereas PPPoE connections (WinPoet, RASPPPOE, Enternet, etc.) can only use up to 1492. For secure VPN connections (i.e., IPSec) use a MTU value less than 1500.
The best value for MTU is that value just before the packets get fragmented. To test, use the Ping utility.
OS X: ping -D -s 1472 www.dslreports.com
WinXP: ping -f -l 1472 www.dslreports.com
Reduce 1472 by 10 until you no longer get the “packet needs to be fragmented” error message. Then increase by 1 until you are 1 less from getting the same error message. Add 28 more to this (since your ping packet size, not including IP/ICMP header is 28 bytes). This will be your MaxMTU. (Note: If you can ping thru at 1472, stop, you’re done! Add 28 and your MaxMTU is 1500.)
Some typical MTU values:
1500: The biggest sized IP packet that can normally traverse the Internet without getting fragmented. Typical MTU for non PPPoE, non VPN connections.
1492: The MaxMTU recommended for Internet PPPoE implementations.
1472: The maximum ping data payload before fragmentation errors are received on non-PPPoE, non-VPN connections.
1464: The maximum ping data payload before fragmentation errors are received when using PPPoE connected machine.
1460: TCP Data size (MSS) when MTU is 1500 and not using PPPoE.
1452: TCP Data size (MSS) when MTU is 1492 and using PPPoE.
1400: MaxMTU for PPTP Tunneling VPN (Win2K/WinXP).
576: Typically recommended as the MTU for dialup type applications...leaving 536 bytes of TCP data.

"NETDEV WATCHDOG: eth0: transmit timed out" proble

Hi all,
I did a "pacman -Syu" and had to upgrade a lot of packages. After I rebooted this machine, I'm have problem with its network connection...
When I do a scp of a big file to this machine, say 500+ MB, the copy progress will stall for a couple of seconds (2 to 10) and I receive the following errors in /var/log/messages.log: "NETDEV WATCHDOG: eth0: transmit timed out". This happens once or twice in this scp session. If I start a second, both it will stall several times and sometimes don't even finish (e.g; times out completely). I did not have this problem before all the upgrades.
Has anybody seen this before? Is my network broken and happened to be this right after the upgrade by coincidence?
Regards

on some intel chipsets i've had a similar problem. try passing:
pci=noacpi
to the kernel. if that does not help either turn acpi off alltogether with:
acpi=off
then again, this is just a guess on what might solve the problem since i do not know which driver you use.

Mail Version 2.1 Port 0 timed out

Mail Version: 2.1 (752/752.2)
OS Version: 10.4.7
OS Build: 8J135
Duration of problem: 8 Months
<hr />
Error:
Connection Failed
There may be a problem with the mail server or network. Check the settings for account "ISPmail" or try again.
The server error encountered was: The connection to the server "mail.host.com" on port 0 timed out.
<hr />
Seetings are correct. The port is 110, it is a POP server. nothing has been modified prior to receiving this error.
Since I have done the following:
Cleared the cache
Deleted the prefs
Recreated the account
And done everything I could find in these forums to fix the problem
Nothing has worked!
I am currently experiencing this on two computers. It appears to be an intermittened problem as Mail will eventually download the e-mail.
I do not have PGP installed. So that is not the problem, I do not have a folder named bundles so that is not the problem. I can login to the mail server using terminal, and through the web.
This problem will somtimes appear on my iMap account I have set up with a different provider.
I beleive that there is some kind of software issue with Mail itself.
Help!
Powerbook G4 15'' (2004) Mac OS X (10.4.7)

I tried everything that you suggested above with the exception of connecting through dial-up. And the error still persisted.
I procrastinated using dial-up because I did not which to interrupt the service of the rest of the family in order to try that route.
The most amazing thing happened just two days ago. There were no updates to the system. Nothing was changed since I disabled all ports except for the ethernet port. But now it works. I am no longer getting the error.
Since I did nothing to cause this to happen I am not going to mark this answered. I also believe that my respite from this error is temporary. I feel that someone needs to find the cause for this error.
However, Apple may have solved this error in the new version of mail in 10.5...

Help - since 15:00 this afternoon Port 25 timed out and no mail can be sent

Have been sending and receiving mail all day - suddenly with no warning or reason mail cannot be sent from either my account or my wife's (on the same computer using the same ADSL line. The message is that "This message could not be delivered......The connection "smtp.mac.com" on port 25 timed out. All outgoing mail is blocked.

Read the following article, which applies to all versions of Mac OS X (not just Mac OS X 10.4.2 and earlier as the article states) and can be useful for other mail accounts as well (not just .Mac):
.Mac: Server timeout alert message when sending email

The connection to the server "X" on port 143 timed out.

My Mac is running MacOS X 10.6.2,
and Mail 4.2 .
I'm using Mail from my work connexion and it is running without problem.
Today I use it from home connexion and Mail doesn't synchronize any of
my E-mail accounts. I get the following error message:<pre>The server returned the error: The connection to the server “imap.free.fr” on port 143 timed out.</pre>
I tested the said server (from a Terminal window):<pre>telnet imap.free.fr 143
Trying 212.27.48.2...
Connected to imap.free.fr.
Escape character is '^]'.
* OK [CAPABILITY IMAP4REV1 X-NETSCAPE LOGIN-REFERRALS AUTH=LOGIN] IMAP4rev1 Free</pre>
and it is replying perfectly correctly.
I also tested my accounts synchronization with Thunderbird (of course
with the same home connexion), and it is working without a trouble.
Hence there isn't any problem with my Mac, my connexion, my imap server,
my account.
But something is deeply corrupted within Mail.
How may I analyze this serious bug (the application is totally unusable)?
How may I turn Mail in a debug mode to provide any kind of trace so as to
make a usable bug report?
<pre>--------
As long as you'll see students making graphics with pen on paper,
you'll see the missing keystone of the software empire.
dan</pre>

Ernie Stamper wrote:
Click on Window in the menubar of Mail, and choose Connection Doctor -- what does it report?
Connection status: <green bullet> Mail was unable to connect to the Internet.
And for all of my accounts, Mail is displaying the rotating wheel,
and in the column says: Connecting to server…
My connexion is OK:
I'm posting this reply from the same Mac,
and I'm collecting my E-mail on the same accounts with Thunderbird.
As the rotating wheels were still rotating 2 minutes later,
just to be sure I made a check of what's going on my connection
with tcpdump. "Mail Connection Doctor"
isn't doing any connection attempt.
Just to be sure of what my eyes refused to believe,
I just restarted Mail, started a tcpdump and opened the "Mail Connection Doctor".
I see some standard trafic (IPP, http…) but nothing on port 143.
This "Mail Connection Doctor" is plainly lying to me.
Hence my original conclusion seems to stand:
there's something corrupted within Mail.
<pre>--------
As long as you'll see students making graphics with pen on paper,
you'll see the missing keystone of the software empire.
dan</pre>

Frequent "port 110 timed out"

Hi. Hope someone can help with this.
I frequently get the following message when checking my mail accounts:
The server error encountered was: The connection to the server "mail.eclipse.co.uk" on port 110 timed out.
Sometimes I get mail okay, sometimes the POP connection times out - with no change in settings. So I'm guessing that the POP server I'm connecting to really is very slow.
Is there any way of changing the timeout period In Apple Mail?
Bruno.
PowerBook G4 Mac OS X (10.4.8)

Hi
No, there is no way to change the timeout period in
Mail, but chances are that, if this happens often to
you, there is something wrong with your network
settings.
The network works fine for all other purposes, and does send / receive mail okay some of the time.
Go to Apple Menu > System Preferences >
Network, choose Network Port
Configurations from the Show popup menu,
and make sure that the configuration used to connect
to Internet appears at the top of the list.
My primary means of connection (wireless) is the top of the list. What's the significance of this by the way?
Also, try using a different method to connect to
Internet, if possible, or connecting the computer to
Internet as directly as possible, i.e. bypassing any
routers that might be present, using an ethernet
cable instead of wireless, etc., and see whether that
makes a difference.
I tried connecting via ethernet on my home network. Again, all other network protocols work fine, but the same intermittent timeout problem with checking POP accounts.
I also tried connecting using someone else's wireless network. Exactly the same result.
Bruno.

Toshiba Portégé M800-10C , eth0:timed out

Similar Messages

Maybe you are looking for