Problem of the week 37

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

We have one exchange server 2003 and two locations.
These locations are connected by VPN. One server is running windows 2000 server, the other windows 2003 server. Exchange is running on the 2000 server.
There was absolutly no problem untill we installed servicepack 2 for windows and service pack 1 for exchange. From that moment on the link would not allow the transmission of data bigger than 1500 bytes.
The MS helpdesk could not find a solution.
Finally we did it!
What did we do to make this work again?

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Reduce the MTU?

MTU problems are common when VPNs are in use.

Harry.

 

Dropped Exchange and went open source?

 

We tried that, but that did not work. The strange thing is that from the 2003 server to the 2000 server there were no problems. From 2000 to 2003, even a dir from a shared folder stranded when there were more than 8 files in the folder. The data send would then be more than 1500 bytes.

 

Hmmm, that's to simple. It would spoil all the fun of beating the system

 

I vaguely remember a client site where this caused an issue a while ago - is it related to Receive Side Scaling? MS 'turned on' some features in SP2 that were meant to speed up the TCP/IP stack in Windows, but some of them broke things horribly in NAT/VPN environments

 

You rebooted.

 

Sometimes the simplest solutions are the best!

 

Was not available at that moment.

 

Very close. We failed to reboot between the installation of the sp of the OS and the sp of exchange. So we uninstalled the sp of exchange, rebooted and reinstalled the SP of exchange and all was well.
The interesting thing was that the MS specialist tried to solve the problem for more than a week and did not find this sollution.

 

something related at renewing the vpn key after a certain amount of traffic.

 

No, the correct answer has allready been given.

 

I think so, but the operator decided not to because he also installed the exchange sp during that session. He figured he could save a reboot this way.

 

Any more questions ?
I like the game !
Nico