Sending mail, timeouts. 3

[Grenage]

The internet connection is ADSL coming through the BT router (this router is not hacked/cracked/configurable in any way). The OS in XP.

The internet connection is working fine and we can browse/download files/download emails perfectly. The trouble we are having is when we try to send an email.

Basically it starts to send a message but times out. There are no/has never been a firewall on this computer. Norton Anti-virus is/has always been running.

I can telnet into the BT email server and send a message from there, but neither outlook nor outlook express will send a message. I have tried repairing the connection, re-installing email acounts and the software but have come up with nothing.

Can anyone think of something I might be overlooking?

PS: while this error occured around the time of the MSBlast worm outbreak, I have given the system a good once over and can find no spyware, virii or worms (Sbybot, Norton & Mcaffee).

 

[bcastner]

1. Date/Time correct?
2. Any problems with other secured (https sites?
3. If you create a new profile, does it work?

To resolve this behavior, create a new profile:
Click Start, point to Settings, and then click Control Panel.
Double-click the Mail icon.
In the Mail Setup dialog box, click Show Profiles.

If you want to be able to select a specific profile each time you start Outlook, click the General tab, click Prompt for a profile to be used, and then click Add.
In the New Profile dialog box, under Profile Name, type a descriptive name for the new profile, and then click OK.
In the E-mail Accounts dialog box, select Add a new e-mail account in the e-mail options, and then click Next.
Click the type of server that your e-mail account works with, and then click Next.
Complete all of the required fields, including those that are on the tabs that appear after you click More Settings.
When you finish providing the required information, click Finish.

4. If you create a new user, setup of OE or Outlook, does that work?

 

[Grenage]

Gretting Bcastner,

Time/Date are good. I will try mail profiles when I get, back to the machine this evening and let you know.

Thanks for the input.

 

[bcastner]

Grenage,

One last thing to watch out for is if the .pst file grows > 2 gigs.

It sure sounds like a corrupt profile, either for OE or Outlook, or the user profile itself; assuming no firewall is in place blocking IGMP traffic.

 

[Grenage]

Good thinking, I shall let you know once I have given it a going over with your suggestions.

 

[jpm121]

Grenage, just to add -- depending on the version of Norton, there may be an Option for "Protect against e-mail timeouts" or something similar. I think it's in the Advanced Options section.

Good luck...

 

[Grenage]

jpm121,
Thanks for your reply, I did try this initially but no luck. I don't think it's norton related in any way because removing it from the system made no difference to the timeouts.

bcastner,
Regarding the profiles, I removed the old and created a new profile. Under mail profiles there is an option to test the email account where it sends a mail out to the account, this worked 50% of the time.

I also created a new user for XP and configured a new profile in that but the same result.

Quite a puzzler.

 

[bcastner]

Grenage,

damn BT.

Try changing the mail connection profile to its IP form.
ping mail.bt.com (or whatever it is)
If it returns a more fully qualified Domain name, try that in the mail server profile.

If no joy, try the IP form in the mail account profile rather than the DNS form.

I had a similar problem when my mail provider began implementing an IGMP handshake before mail could be sent 100% of the time.

My router was not responding to IGMP Type #2 requests. This is in effect a request for a temporary registration as a remote router point. I had to do a firmware upgrade to solve the problem. (A linksys WRT54G)

Final thought for tonight: This can be an MTU issue. Try dropping the client MTU. You certainly want it at 1492 max under DSL, but some DSL providers (AOL is one) use something close to a PPTP protocol and the value should be 1400.

 

[Grenage]

Greetings bcastner,

Thanks for your assistance. I tried replicating the computer's settings on another XP machine but it worked fine (but of course), I will give your further suggestions a going over tonight.

Thanks again.

 

[bcastner]

aye, Grenage. These can be hard to sort.

 

[Grenage]

Well no real luck thus far. Short of re-installing I have absolutely no idea what could cure it.

It worked fine last night for 1 email (although it took a while to send that immense load of 1 sentence) but then stopped again.

I will carry on trying for a few days before I give up and format the drive, will let you know if I find anything that fixes it.

 

[bcastner]

While not exactly on point as a remedy, try rebuilding your Winsock service stacks:

http://members.shaw.ca/techcd/VB_Projects/WinsockFix.zip

I would also be curious what the result of a different ethernet adapter might be.

 

[Grenage]

Ah yes good thinking, I will try out the WinSock rebuilder. I also do have a spare ethernet card so that could be worth a shot ( Damn strange if it fixes it though ).

 

[bcastner]

If it fixes it, do not complain.

Question: when you say you replicated the settings on another XP workstation and it worked fine, was this through the same BT supplied router, or through dial-up or at a different site?

I still am highly suspicious of the router and its firmware at the moment, and if it worked on another XP machine on the same site, you will let me give up on that line of attack.

 

[bcastner]

And aye, Grenage, I know you know how to upgrade the firmware on that BT router if necessary.

Bill

 

[Grenage]

Good morning Bcastner,

The second machine I used for testing was indeed on the same router. There is also 1 other machine on this router, and that seems to be okay with email too.

The swappped network card didn't seem to change anything although I did not have a chance to try the WinSocks fix as I was dragged away.

Hopefully that might work.

ps: I'm always hesitant on changing the firmware on the default BT model as I've seen a couple never work again.

 

[bcastner]

You do not have to play with the BT router as you have already ruled it out as an issue with the success on the second machine.

As new profiles, including user profiles, does not sort the issue it is either:

1. A Winsock issue. You know how to repair that.
2. A NIC issue
3. Possibly an MTU issue. Discussed earlier. Try

http://www.broadbandreports.com/tweaks

and run a tweak test. Use the DrTCP tool on the site to adjust your adapter MTU to 1492 maximum.
4. Possibly an autonegotiation issue. Try forcing the Adapter to 10-Half and retrying. If that succeeds, try other settings until it is stable at the highest speed and duplex setting you can achieve. It if goes to a hub, 10 Half duplex is likely the best setting.

 

[bcastner]

Grenage,

Update needed from you. Any luck?

Bill

 

[Grenage]

Afternoon mate,

Rest assured I have not forgotten. I was unable to get to the machine yesterday but I do have a couple of hours scheduled tonight.

With some luck tomorrows posting will be regarding a sucessful session.

 

[bcastner]

Make sure you check that your cryptographic service is running on the machine. The MS KB article here only gets good towards the end. Often re-registering the crypto components helps:

http://support.microsoft.com/?kbid=813444