rwmira01@ULKYVX.BITNET (NEWS_PERSONALNAME) (12/06/90)
I had an interesting problem today as I continue to work with integrating TCP/IP into our network. Here is the situation: Client: StarGROUP 3.3 w/ v3.4 NDIS driver FTP Software's NDIS Packet Driver CUTCP 2.2-D StarGROUP 3.3 Server StarGROUP 3.2 Server PC TCP/IP Server running CUTCP 2.2-D and the AT&T.COM packet driver with no StarGROUP software loaded. They work fine together. I can have both protocol stacks loaded and access the TCP/IP host and both StarGROUP servers. I link a drive to the 3.2 server and switch to it. I run FTPBIN and open a session to the DOS machine. I transfer a small (2K) ASCII file from the TCP/IP host to the linked 3.2 drive. I then do a BINARY and try and transfer a 20K file and it locks up. If I try to do the same, but write the binary file to my local hard drive it works. I haven't tried linking it to the 3.3 drive and do the transfer. Any ideas what could cause this? Are there any of the transfer parameters in the CONFIG.TEL file that need adjusted? I know this is a rather odd combination of things to do, but hey I'm testing this and I am supposed to push limits. Any help would be appreciated. Thanks in advance. Rob Miracle "Egos are for those who need a mental crutch." -- Anton Devious