07-30-2002 06:53 AM - edited 02-20-2020 10:11 PM
I'm suprised this problem hasn't come up before with someone? As I can't seem to find an answer...
I have recreated the problem in a lab with a Pix 515 running Nat. We have a Windows 2000 server on the outside interface with 2 Windows 2000 clients on the inside interface. With NAT enabled, I can start a file copy with machine A, but when I map a drive or do a file copy with machine B, client A gets an "network error" message? But machine B can copy file. I ONLY get this with NAT turned on. Turn off NAT and the problem goes away. And this doesn't happen with Windows NT 4.0 (we are upgrading very soon).
Anyone seen this problem?
08-06-2002 01:08 PM
This looks like a problem with the network code of Windows 2000 itself as it changes from version to version of the software.
08-09-2002 09:07 AM
Have you tried setting up a syslog server to see what is happening in the background?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: