Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Thunderbird OK with wired router, fails on same in wireless link

  • 5 replies
  • 1 has this problem
  • 4 views
  • Last reply by paulmoffat

more options

Desk PC connected wired ethernet to wireless router to cable modem. All connection accesses are OK, mail send receive, internet. But the wireless link from a remote PC, same OS etc. connects, ethernet OK, email receive OK, BUT fails to find STMP server on send. Both PCs setup with same parameters and account information. Only other difference is I need to use a wireless extender to contact the house server. Signal is strong at the PC is question.

Desk PC connected wired ethernet to wireless router to cable modem. All connection accesses are OK, mail send receive, internet. But the wireless link from a remote PC, same OS etc. connects, ethernet OK, email receive OK, BUT fails to find STMP server on send. Both PCs setup with same parameters and account information. Only other difference is I need to use a wireless extender to contact the house server. Signal is strong at the PC is question.

All Replies (5)

more options
BUT fails to find STMP server on send.

Sounds like a DNS issue.

more options

Direct connect PC OK on ethernet, Wireless receives OK, no send with same settings. Wireless unit uses Netgear extender to get to router, as remote is 1200 feet from it. The error on send is 'STMP server not found', but the DNS value is the same at both PC's. Could the wireless extender be the cause?. All other internet connections, using Firefox, work without any issues.

more options

You are chasing the wrong dog. Thunderbird does not care what kind of Internet connections that it has, only that it has one.

You need to look at the Outgoing Server (SMTP) settings on both machines and confirm that they are the same. It sounds like something needs to be changed on the problem PC.

Either that or your firewall is blocking Thunderbird on the problem machine.

more options

This is entirely experimental.

open a command prompt. in it type ping and the smtp server name and press enter. On the second line of the response will be the server name followed by the IP address. (The following is the result of "pinging" smtp.gmail.com

C:\Users\Matt>ping smtp.gmail.com
Pinging gmail-smtp-msa.l.google.com [173.194.72.108] with 32 bytes of data:
Reply from 173.194.72.108: bytes=32 time=201ms TTL=42
Reply from 173.194.72.108: bytes=32 time=190ms TTL=42
Reply from 173.194.72.108: bytes=32 time=201ms TTL=42
Reply from 173.194.72.108: bytes=32 time=200ms TTL=42
Ping statistics for 173.194.72.108:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 190ms, Maximum = 201ms, Average = 198ms

Now go into the outgoing server settings (tools menu (alt+T) > account settings) and change the server name to the IP address that was returned by the ping and try again.

If it works with the IP address it is most certainly a DNS issue. It might be the router blocks DNS.

more options

Unfortunately the ping method did not return any connection (timed out), even with known good addresses at several source locations. Sorry. The DNS did return an address resolution anyway. I will check settings again, then see if the firewall settings have effect. System is Windows 7, SP1, 32bit, professional and home versions.