[Personal Alpha] No IP access to Host but ping (again)

[Jon Pinkley]

Didier,

To disable the tcp offloading, it had previously written "Several recommendations for method 2 in following Microsoft knowledgebase article 948496."

That should have been Article 8887750

method 2 posted at http://support.microsoft.com/kb/888750

Method 2
Disable TCP task offloading in the registry of the host computer. To do this, follow these steps.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. Click Edit, point to New, and then click DWORD Value.
4. Type DisableTaskOffload as the entry name, and then press ENTER.
5. Right-click DisableTaskOffload, and then click Modify.
6. In the Value data box, type a value of 1, and then click OK.
7. Quit Registry Editor.
8. Restart your computer.


See the referring thread at http://social.technet.microsoft.com/Forums/en/winserverPN/thread/814a4a85-3f36-4fe3-826f-fedf7fa23a44

Jon

[Didier DTL Morandi]

B I N G O

Don't try to explain to me why "it works", I'm too ashamed because of the work I gave to you all.

"The Network is the System", we used to say at DEC.

Thank you friends,

And a Merry Christmas to come !
Cheers.

[Jon Pinkley]

Didier,

Did you use method 2 posted at

http://support.microsoft.com/kb/888750

or did you use some other method to disable tcp offload?

Have you noticed any bad side effects from disabling the offload? (Perhaps the method suggested by Greg on the Stomasys forum)

Please let us know what you did in case someone else had the problem. Also please update the thread at the Sromasys PA forum.

http://forum.stromasys.com/userforum/index.php?t=msg&th=13&start=0&S=0a146afba08b0d415aae6c5683a1d971

I'll have to download and try out PA :-)

Thanks,

Jon

[Jon Pinkley]

I see that I did a poor job of editing.

I wrote:
--------------------
or did you use some other method to disable tcp offload?

Have you noticed any bad side effects from disabling the offload? (Perhaps the method suggested by Greg on the Stomasys forum)
---------------------

Which should have been

or did you use some other method to disable tcp offload? (Perhaps the method suggested by Greg on the Stomasys forum)

Have you noticed any bad side effects from disabling the offload?

---------------------

I did not intend that to suggest that Greg's method was more error prone.

Jon

[Didier DTL Morandi]

I did this :

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. Click Edit, point to New, and then click DWORD Value.
4. Type DisableTaskOffload as the entry name, and then press ENTER.
5. Right-click DisableTaskOffload, and then click Modify.
6. In the Value data box, type a value of 1, and then click OK.
7. Quit Registry Editor.
8. Restart your computer.

[Hoff]

You've done a yeoman job here at finding what look to be a number of "hardware" problems with the emulator.

These details really need to be documented over at Stromasys and preferably within the installation notes within these kits, or (better) implemented within the installation kit itself.

[Didier DTL Morandi]

Well, this is the very first hard one I encountered, and to me it ahs nothing to do with the emulator. Looks like it is a network hardware problem, no ?

[Volker Halle]

Didier,

thanks for following up on this.

For a better understanding, here is a pointer to a Wikipedia article on TOE - TCP Offload Engine:

http://en.wikipedia.org/wiki/TCP_Offload_Engine

There is one sentence, which seems to explain why this may be causing a problem for the NDIS driver used in PersonalAlpha:

'Complexity - TOE breaks the assumption that kernels make about having access to all resources at all times - details such as memory used by open connections are not available with TOE. TOE also requires very large changes to a networking stack in order to be supported properly, and even when that is done, features like Quality of Service and packet filtering typically do not work.'

Volker.

[Didier DTL Morandi]

Problem solved.
Thanks to all and

MERRY CHRISTMAS

[Hoff]

Prospero ano y felicidad, DTL.

> "Looks like it is a network hardware problem, no?"

Didn't some bonehead here say that all the way back in the beginning? Bad hardware is bad hardware, even if it's really bad (emulated) hardware.

It is most excellent that you've gotten this working.

Now please do us all a _huge_ favor and write this stuff up as an article, and post it somewhere. Or submit the article for VTJ. Or something.

And if you don't have a spot to post the article that you're writing here, send it along; I do. I'm happy to assist with reviewing the article, too.