The TCP/IP protocol stack reported that It ran out of memory. Consult your network documentation

Try these options..

1. Increase OS Virtual memory

2. Re-install network driver (tcpip)


~Hemanth

VM is 768MB. What would you recommend increasing it to?

This sounds like it is actually an error reported by the server's TCP/IP stack.  I say this because the message you got about MAX_SESSIONS is saying that to get rid of the problem, have the SERVER reconfigured (i.e., either less clients allowed via MAX_SESSIONS so that TCP/IPneeds less memory, or more memory so TCP/IP can deal with this many clients).

Is anyone else in teh company getting similar error messages? Is there another DOmino server you can connect to to see if your client has problems with just the one server or all servers?

(If you do not have another server to connect to, you can register with OpenNTF.org, and access their Dmino server, assuming you don't have a firewall blocking that traffic.)

I was able to access the server with no problems, using the same id on another workstation.
Seems to be specific to this particular workstation.
Thanks for the suggestions.
cj

Looks like VM is high enough..try tcpip driver

Yea, that's what i figured. I started to download the new driver and before I installed I found a file in her startup called:
\system32\spool\drivers\HPZTSB06.exe - I disabled this and rebooted.
Not sure if this was causing a problem or not but when I tried notes again, it was fine.

I am keeping this ticket open for a few days to see if the problem returns.
I will let you know. Thanks for your help.
cj

just another questions regarding the tcpip driver. Are you referring to the nic drivers?

tcpip is provided by OS.. NIC is provided by manufacturer. They are bound together by OS

In your earlier comment you suggested tying the tcpip driver. I guess my question isn't what is tcpip, but rather, what do you mean when you say "try the tcpip driver".
Since it's Windows XP, uninstalling TCPIP is not an option. But I would like more intruction, if possible, regarding the tcpip driver. I am unclear what your intstruction means.
By the way, the error returned, so I am back to square one.
Thanks for your help.
cj

I did verify XP2 was not installed on this machine. Spybot was run on the machine and removed 19 traces of spyware. Mcafee 4.51 sp1 with updates as of 11/10/04.
It really does seem to be pointing to more spyware. Maybe I will try the ad aware from Lavasoft.
Thanks for the suggestions.

I've found that by using Spybot, quite a number of adware programs came with the product.  If you get hold of the HiJackthis utility you can spot quite a number of spurious programmes from the log file generated when you run a scan.

do you have link?

Check this link: http://support.microsoft.com/default.aspx?scid=kb;en-us;299357&FR=1&PA=1&SD=HSCH

thank you for the information. I ran ad aware and it seems to be working fine, but I suspect this problem will reoccur and if I will follow reset tcpip.
Thanks again for the good info.

rd153,

> I've found that by using Spybot, quite a number of adware programs came with the product.

What on earth are you talking about?  You must have downloaded one of the fake versions of Spybot that just disable all spyware EXCEPT for the publisher's own.

- qwaletee

cjsling,

Can you tell us what exactly happened?  UI'm confised at this poitn as to what fixed it, or even whether it was truly fixed.

- qwaletee

running spyware from Lavasoft, as suggested, resolved the problem.
Thanks for your follow up.
cj

FYI

http://www.liutilities.com/products/wintaskspro/processlibrary/hpztsb06/

Okay, thanks. This computer had a lot of spyware. Lavasoft removed a whole lot more, which ultimately fixed the problem.