Corrected Question for j2Buttonsw

[gazzawazza]

Hi j2, I've just realised the info I gave you in my previous question is incorrect, the response I've been getting (it's happening again now) says, 'Your pop3 server has not responded after 60 seconds, would you like to wait another 60 seconds before trying again?'

Is this the same as what I've already asked you, ie can I alter anything myself to remedy the situation?

[lisaj]

what's the POP server you're trying to connect to? Is it pop.ntlworld.com? try bringing up a DOS prompt and typing "tracert pop.ntlworld.com" (or whatever your POP server is). That'll tell you where the communications problem is.

[gazzawazza]

Thanks lisa, yes it is pop.ntlworld.com, but can you tell me how I bring up a DOS prompt!!??

[j2buttonsw]

I think it is the ntlworld.com pop server that is the fault. You have sent a request for information and the server has not responded (it is too busy or is offline). lisaj is suggesting you establish whether the request is reaching the pop server or has been held up on its journey by using the tracert command. You get the DOS box in start-programs-msdos command (for windows 9x) or start-run then typing in command then OK (for windows nt/2000/xp). At the command/dos prompt type in tracert pop.ntlworld.com then return (as lisaj has rightly said). You could also use pathping to see the extent of packet loss on its destination (at the command/dos screen type pathping pop.ntlworld.com then return. I think this is a bit academic because I know for a fact the ntlworld pop servers have been down (and, more worringly, I have lost mail).

[gazzawazza]

Thanks very much to both of you. Gazza.

[lisaj]

OK - new info for you: I was completely stumped by a Windows XP Home machine yesterday. It was fine. No problems. No networking problems. Could ping, traceroute and connect to webpages and servers of all sorts. It just would not open up a connection on port 25 (for sending mail - SMTP) or 110 (for receiving mail - POP3). There were no filters in place anywhere, it was an internal network so there were no firewalls in place, and as I say it completely stumped me. A reboot sorted it. Anyway, I think the implication of this is clear... Microsoft have now made it impossible for us to reliably do something as simple as connect to a mail server so if your problem rears its ugly head again bear in mind there might just be nothing wrong! :-)

[gazzawazza]

Thanks, it's now working again!