General Discussion
  >> General Broadband Chatter


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | 2 | 3 | [4] | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | >> (show all)   Print Thread
Standard User Pheasant
(knowledge is power) Sun 12-Jun-22 17:44:18
Print Post

Re: Email problem


[re: Andrew_W] [link to this post]
 
Still running the DGN2200v4 as per your bio? Is it running up to date firmware?

Also if you're simply using the default DNS server settings form IDNet (212.69.36.23 and 212.69.40.23) - you may wish to re-test, by replacing the primary and secondary DNS servers with something like 1.1.1.1 or 8.8.8.8 respectively.
Standard User Andrew_W
(knowledge is power) Sun 12-Jun-22 17:49:13
Print Post

Re: Email problem


[re: Pheasant] [link to this post]
 
No now using TP Link Archer VR600 v3

However, just pinged 212.69.40.22 and got a response this time!

Andrew
Standard User Pheasant
(knowledge is power) Sun 12-Jun-22 17:54:38
Print Post

Re: Email problem


[re: Andrew_W] [link to this post]
 
...and now successfully ping the reverse, i.e. smtp.idnet.com without timeouts?

What DNS servers new being set on your machines. run ipconfig /all from a command prompt.


Register (or login) on our website and you will not see this ad.

Standard User Andrew_W
(knowledge is power) Sun 12-Jun-22 18:04:28
Print Post

Re: Email problem


[re: Pheasant] [link to this post]
 
ping smtp.idnet.com produced no response.

ipconfig /all produced a quick flash on the screen of something too fast to read!

So grateful for your patience but have to switch off in two minutes!

Andrew
Standard User Pheasant
(knowledge is power) Sun 12-Jun-22 18:08:24
Print Post

Re: Email problem


[re: Andrew_W] [link to this post]
 
ipconfig /all produced a quick flash on the screen of something too fast to read!

You need to open a a command prompt first, by typing cmd
Then from within the command shell there type ipconfig /all

You can then scroll back through the output of the ipconfig /all command at your leisure wink
Standard User Andrew_W
(knowledge is power) Sun 12-Jun-22 18:26:56
Print Post

Re: Email problem


[re: Pheasant] [link to this post]
 
In reply to a post by Pheasant:
ipconfig /all produced a quick flash on the screen of something too fast to read!

You need to open a a command prompt first, by typing cmd
Then from within the command shell there type ipconfig /all

You can then scroll back through the output of the ipconfig /all command at your leisure wink


Got it. Got to lie down now.....!!

Andrew
Standard User Andrew_W
(knowledge is power) Mon 13-Jun-22 10:10:20
Print Post

Re: Email problem


[re: Pheasant] [link to this post]
 
In reply to a post by Pheasant:
ipconfig /all produced a quick flash on the screen of something too fast to read!

You need to open a a command prompt first, by typing cmd
Then from within the command shell there type ipconfig /all

You can then scroll back through the output of the ipconfig /all command at your leisure wink


Morning again!

OK I managed to save a copy of my ipconfig/all What do I look for please?

This morning I have managed to send a couple of emails via Outlook until it stopped again.

I also managed to speak to Idnet support who say the problem is a corruption in my email program. The fact that the same problem exist with my Linux PC appears to Idnet to be irrelevant? And the fact that their server ignores the problem occasionally is confusing.

Idnet say use their Webmail program and wait for the problem to go away. We are on day 5 today!!!

As I said, if I first ping smtp.idnet.com and get a response then I can send emails for a while.🤪

Andrew
Standard User Pheasant
(knowledge is power) Mon 13-Jun-22 10:17:35
Print Post

Re: Email problem


[re: Andrew_W] [link to this post]
 
Morning!

OK. First up. What DNS servers are being set? You can see in the output of the ipconfig /all command.

We can do further testing by temporarily setting the numeric IP address of the SMTP server within Outlook / Thunderbird etc - rather than using the domain name. Just to see if that changes matters

We can also change the DNS servers on your router to see again if that improves matters.
Standard User Andrew_W
(knowledge is power) Mon 13-Jun-22 10:30:20
Print Post

Re: Email problem


[re: Pheasant] [link to this post]
 
DNS servers 192.168.1.1

Andrew
Standard User Pheasant
(knowledge is power) Mon 13-Jun-22 10:39:15
Print Post

Re: Email problem


[re: Andrew_W] [link to this post]
 
Can you log in to the TP Link router and as per settings on page 82 of:
https://static.tp-link.com/manual/2021/202106/202106...

Set the primary DNS to 1.1.1.1 and secondary DNS to 8.8.8.8.

Once done, from a command prompt, type ipconfig /release and then ipconfig /renew

Finally. check to see if it’s picked up the new details by running ipconfig /all
Pages in this thread: 1 | 2 | 3 | [4] | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | >> (show all)   Print Thread

Jump to