RE: [FW1] SecuRemote and Win2K

[T.Higgins@FW1-NOSPAMeu.hns.com]

Your statement on packet size issues has jogged my memory on something that may be related - we had a colleague having a problem with IGMP - basically their router(or some form network device) was having problems because it expected 20-byte header but the Microsoft TCP Options added an extra 4 bytes - therefore the router rejected the packets and the multicast attempt failed.

I wonder if this is related to the Outlook/Exchange issues. The (potential) answer to a dicussion-thread question on the IGMP problem was this:-

/cut/
First of all, in your question you say Win2k server, in a later comment you say NT4. But here is your answer anyways. 
The correct answer DOES come from Q120642, you just need to know how to interpret it. 
If you have read RFC791, which is the foundation for IPv4 (can be found at http://rfc.net/rfc0791.html) You may very well realize something about the parameters that you have overlooked. Obviously your server is adding in the extra parameters in your header for a reason. The reason is it's probably added into your registry for something or another. 
Please go to your registry (Start>Run>Regedit) 
and go to this Key. 
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcp ip\Parameters 
Your Adapter may/may not have a folder in between services and Tcpip... then it would be ...\services\'adaptername'\tcpip\parameters. 
and look for the key called "DefaultTOS" It may have been added in there by a program you might have installed, 
with this entry, a value of no options will automatically be added to your header, if you delete it, it will probably drop it back down to the default size (of what it recieved)... 
Note that DefaultTOS is not available in Windows 2000. 
/cut/


I haven't tested the above but hope it may give more clues ?

Tim

"Goetz, Jarrett" <JGoetz@Jenzabar.net> Sent by: owner-fw-1-mailinglist@lists.us.checkpoint.com 13/06/01 05:14

To:        Rob Michayluk <rmichayluk@acdsystems.com>         cc:        "Fw-1-Mailinglist (E-mail)" <fw-1-mailinglist@beethoven.us.checkpoint.com>         Subject:        RE: [FW1] SecuRemote and Win2K

Rob, we use SR and Win2000 extensively.  It works perfectly for us on all fronts EXCEPT we are always running into minor issues with Exchange.  I know very few people who don't have some little issue somewhere along the line with Exchange/Outlook and SR.....  I probably has to do with something related to the size of the packets being sent or something else on the network layer (MTU?) that Exchange/Outlook do in an interesting fashion....    We are doing some research on this now, will let you know....
-----Original Message-----
From: Rob Michayluk [mailto:rmichayluk@acdsystems.com]
Sent: Friday, June 08, 2001 14:32
To: Fw-1-Mailinglist (E-mail)
Subject: [FW1] SecuRemote and Win2K

Hello All,

I am hoping that someone can provide me with information on possible issues with SecuRemote v4.1 SP3 (Build 4176).
The users in my network connect to our Exchange server through SecuRemote when they are outside the network. Sometimes, the connection will seem to freeze and nothing will work. They have to kill the SecuRemote client and restart it or sometimes they have to reboot their machines to have it work again. I have checked things on the Firewall side and nothing seems to be amiss.

None of the users have any MS service packs on their machines.
Has anyone run into problems with SecuRemote and Win2k?

Rob Michayluk
Computer Network Services Analyst
ACD Systems Ltd
The Digital Imaging Company
Tel:  
Fax:
rmichayluk@acdsystems.com
www.ACDSYSTEMS.com

Come meet the ACD Systems Team!

Macworld Conference & Expo, New York, July 18-20, Booth 1331
Digital Imaging ' 01 Conference & Exhibition, Santa Clara, California, September 20-21
Comdex Fall 2001, Las Vegas Convention Center, Nevada, November 12-16, Booth 7651

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature