Re: Strange PIX behaviour with PAT

lpaschall · ‎06-01-2004

I have been having trouble transfering large files on my network. When one of my clients uses SQL enterprise mamanger to connect to a group of 5 SQL servers in the DMZ it causes all large file transfers to and from the Internal int to the DMZ int to fail. We get the generic error "The specified network name is no longer available". Only users that are using the same global PAT are effected. I have another machine that has a static NAT that can transfer files to and from the Int to the DMZ with no problems. USing the show xlate command I can see that the SQL enterprise manager is using about 40-50 translations. When he stops using the app, everything is back to normal. I had another user connect to the group of servers using the SQL ent manager and the same thing happened. Anybody know what is going on.

Thanks,

Lonnie

ehirsel · ‎06-01-2004

Are the clients that use sql enterprise manager configured to use the tcp port only and not named pipes? Normally named pipes is on by default and if it is turned on then the ms netbios ports (137 thru 139) are used, I believe on the client as well as the server end. In a case like that, the PAT won't work. However static NAT will work.

What version of enterprise manager, and what version of the pix code are being used?

lpaschall · ‎06-02-2004

The client was configured to use both. But SQL enterprise manager works fine. It was just that when anyone used SQL Enterprise Manager to connect to the group of servers inthe DMZ (4 servers) large (>10MB) file transers failed between the Int and the DMZ. Close the SQL app and transfers resumed again. To solve the prob I created a static translation for the client using the SQL ent mgr and it seems to not cause any problems now. We are using version 8.0 and code 6.2(2)

Thanks,

Lonnie

ehirsel · ‎06-02-2004

How were the file transfers done? Via ftp?

lpaschall · ‎06-03-2004

No just via windows explorer copy and paste. And again when the SQL Enterprise manager disconnects it works, and it is working fine now since I did a static NAT for the client using the sql ent mngr.