the problem is that we can reproduce it on our machines,my bots are up the last 48 hours without a single problem![]()
hey i just poted this in a thread i started to about this error.
hey so i was messing around with vmware and went to settings for my network adapter. the setting for NAT: used to share the host's IP address was checked. i figure might as well try a different option so i tried out the bridged: connected directly to the physical machine. i was able to run a full act 3 farm profile without DB disconnecting. It was also alot faster logging into DB then it has been. After that 1st clear without a disconnect i changed it back to NAT option and i lost connection to DB in about 20 minutes. Going now on a 3rd run with the bridge option again. If it goes all the way thru i guess this is a fix?