Upgrade probs with Outlook

[Cams]

Hi, hope someone can help.

I am currectly rolling out XP to 25 locations (retail store chain) and I am having dificulties with Outlook 98

Previous setup is Win98 and Wingate 4.5.1 using ADSL (NIC) Not using WGIC

New config is Win XP SP2, Wingate 5.2.2 ADSL with NIC.

Problem is sending emails, retrieving via POP3 is fine. When sending emails it will start to send (via SMTP, we send to Mailguard which offer virus and spam protection) the email appears to start sending but then recieve an error being disconnected from mail server. If the email is small it will work but anything larger or replies will fail.

I have disabled XP firewalls and ICS WGIC is not used on clients (cant install it anyway because it thinks firewall or ICS is running.

At present I have 2 sites installed, 1 where Outlook is on the Wingate server and that works fine, 2nd where Outlook is installed on a client, that fails. Have tried dynamic and static IP's on client with no success.

Any thoughts?

Don't really want to upgrade to ver 6, as ver 5 has been built into images.

Colin.

[Nev]

Hi, hope someone can help.

I am currectly rolling out XP to 25 locations (retail store chain) and I am having dificulties with Outlook 98

Previous setup is Win98 and Wingate 4.5.1 using ADSL (NIC) Not using WGIC

New config is Win XP SP2, Wingate 5.2.2 ADSL with NIC.

Problem is sending emails, retrieving via POP3 is fine. When sending emails it will start to send (via SMTP, we send to Mailguard which offer virus and spam protection) the email appears to start sending but then recieve an error being disconnected from mail server. If the email is small it will work but anything larger or replies will fail.

I have disabled XP firewalls and ICS WGIC is not used on clients (cant install it anyway because it thinks firewall or ICS is running.

At present I have 2 sites installed, 1 where Outlook is on the Wingate server and that works fine, 2nd where Outlook is installed on a client, that fails. Have tried dynamic and static IP's on client with no success.

Any thoughts?

Don't really want to upgrade to ver 6, as ver 5 has been built into images.

Colin.

Hi,

This should be easy to track down for you Colin.

Try turning on the debug logging for SMTP server with all options.

Run a session of sending to produce the error and post the portion of the log here so someone can sort this for you.

Log is located under Wingate\Logs\SMTP Server in the Proram Files dir.

Good luck,

Nev.

[Cams]

Thanks Nev.

I will do that once I get back access to the site.

I thought that SMTP Server was more so used if you wanted Wingate to handle emails and deliver. All of our emails will be sent via login to a remote mail server.

[Nev]

Thanks Nev.

I will do that once I get back access to the site.

I thought that SMTP Server was more so used if you wanted Wingate to handle emails and deliver. All of our emails will be sent via login to a remote mail server.

Ah good Colin,

Well I probably know little about the service you are trying to connect to.

To help diagonse though, how does the client configure to access the service?

Is outlook configured to point directly at the server like: Outgoing server smtp.server.isp.net:25 or is it configured to point to Wingate like 192.168.0.1:25 ?

Good luck,
Nev.

[Cams]

Hi Nev,

Outlook points at an external mail server, port 25 is not specified but is used anyway as the standard port for SMTP. I have also tried setting the external client to use our own exchange server for SMTP and this had the same result as well.

Colin

[adrien]

Hi

If you don't want to use the WinGate SMTP server, (i.e. you are using NAT to connect through WinGate to an SMTP server on the Internet), then you should disable it, and make sure that it doesn't have transparent redirects turned on (on the sessions tab). Also, you probably don't need an SMTP proxy either, which probably would have been installed from your 4.5.1 install, and migrated to 5.2.2.

You might also want to upgrade to 5.2.3. But if you were going to do that, I imagine you would be better off still upgrading to 6.0.3, which would require a change to the images you have created. In many ways WinGate 6 is more transportable than 5.x, since its configuration is less tied to the specifics of your machine (i.e. IP addresses etc).

Adrien

[Cams]

Thanks for your help. I decided to try ver 6 on the test setup. I ran the install straight over the top of ver 5. After changing the external NIC from internal to external within Wingate, Outlook worked. Tried it with attachments as well for size and still worked.

Whilst I am happy that it is working it is annoying that I will either have to re create the images or have more work onsite after imaging, at least Wingate does not take to long to install.

Colin.

[Cams]

Hi again,

Well I thought things were looking good.

Went onsite to upgrade to Ver 6, this went smooth. Checked emails from client and they were working fine. Now I have a new similar problem. The server also runs email apps (for our point of sale software) retrieve via POP3 send via SMTP to our exchange server.

I found that retrieving emails was fine but sending was not. A very small email would go (1K) but anything larger would not. The only way I could get the emails working was to disable the extended network driver. This of course stopped evey client from working but system emails take precedence.

I have enabled debugging for the extended network driver and pasted below is a segment of that file.

11/03/04 10:24:01 Debug: NAT message code FFE0B40B, context 1259 OutICMP=0, InICMP=0, OutUDP=0, InUDP=0, OutTCP=1765549, InTcp=7396029
11/03/04 10:24:01 Debug: NAT message code FFE0B40B, context 1267 OutICMP=0, InICMP=224, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
11/03/04 10:24:01 Debug: NAT message code FFE0B40D, context 1273 Total locked memory in use is 191272
11/03/04 10:24:01 Debug: NAT message code FFE0B40E, context 1280 Unknown Frames = 0, Status Queue Size = 128
11/03/04 10:24:06 Debug: NAT message code FFE0B40B, context 1259 OutICMP=0, InICMP=0, OutUDP=0, InUDP=0, OutTCP=1765549, InTcp=7397572
11/03/04 10:24:06 Debug: NAT message code FFE0B40B, context 1267 OutICMP=3, InICMP=227, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
11/03/04 10:24:06 Debug: NAT message code FFE0B40D, context 1273 Total locked memory in use is 191272
11/03/04 10:24:06 Debug: NAT message code FFE0B40E, context 1280 Unknown Frames = 0, Status Queue Size = 128
11/03/04 10:24:11 Debug: NAT message code FFE0B40B, context 1259 OutICMP=0, InICMP=0, OutUDP=0, InUDP=0, OutTCP=1765549, InTcp=7397572
11/03/04 10:24:11 Debug: NAT message code FFE0B40B, context 1267 OutICMP=3, InICMP=227, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
11/03/04 10:24:11 Debug: NAT message code FFE0B40D, context 1273 Total locked memory in use is 191272
11/03/04 10:24:11 Debug: NAT message code FFE0B40E, context 1280 Unknown Frames = 0, Status Queue Size = 128
11/03/04 10:24:16 Debug: NAT message code FFE0B40B, context 1259 OutICMP=0, InICMP=0, OutUDP=0, InUDP=0, OutTCP=1765549, InTcp=7397572
11/03/04 10:24:16 Debug: NAT message code FFE0B40B, context 1267 OutICMP=3, InICMP=227, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
11/03/04 10:24:16 Debug: NAT message code FFE0B40D, context 1273 Total locked memory in use is 191272
11/03/04 10:24:16 Debug: NAT message code FFE0B40E, context 1280 Unknown Frames = 0, Status Queue Size = 128
11/03/04 10:24:21 Debug: NAT message code FFE0B40B, context 1259 OutICMP=0, InICMP=0, OutUDP=0, InUDP=0, OutTCP=1765549, InTcp=7397572
11/03/04 10:24:21 Debug: NAT message code FFE0B40B, context 1267 OutICMP=3, InICMP=227, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
11/03/04 10:24:21 Debug: NAT message code FFE0B40D, context 1273 Total locked memory in use is 191272
11/03/04 10:24:21 Debug: NAT message code FFE0B40E, context 1280 Unknown Frames = 0, Status Queue Size = 128
11/03/04 10:24:26 Debug: NAT message code FFE0B40B, context 1259 OutICMP=0, InICMP=0, OutUDP=0, InUDP=0, OutTCP=1765549, InTcp=7397572
11/03/04 10:24:26 Debug: NAT message code FFE0B40B, context 1267 OutICMP=3, InICMP=227, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
11/03/04 10:24:26 Debug: NAT message code FFE0B40D, context 1273 Total locked memory in use is 191272
11/03/04 10:24:26 Debug: NAT message code FFE0B40E, context 1280 Unknown Frames = 0, Status Queue Size = 128
11/03/04 10:24:32 Debug: NAT message code FFE0B40B, context 1259 OutICMP=0, InICMP=0, OutUDP=0, InUDP=0, OutTCP=1765549, InTcp=7397572
11/03/04 10:24:32 Debug: NAT message code FFE0B40B, context 1267 OutICMP=2, InICMP=227, OutUDP=0, InUDP=0, OutTCP=0, InTcp=0
11/03/04 10:24:32 Debug: NAT message code FFE0B40D, context 1273 Total locked memory in use is 191272
11/03/04 10:24:32 Debug: NAT message code FFE0B40E, context 1280 Unknown Frames = 0, Status Queue Size = 128

This was from the wingate NAT file.

I hope that someone can help me solve this as very soon I will have to give WIngate the flick due to the problems it is causing our organisation.

Thanks

Colin

[Cams]

OK, thanks to the Wingate support staff, problem solved.