Mike, set up a PC acting as a NT server [1] on the server side of the router *but* with TCP only. Then use your client and do the file transfer again. then set the server up on the same side of the switch as the your client and repeat.
This will indicate if the issue is the switch or the server's specific config cheers dean [1] same os and service pack level as the server you are having problems with -----Original Message----- From: Mike Staines [mailto:[EMAIL PROTECTED]] Sent: Thursday, 28 February 2002 4:48 a.m. To: NT 2000 Discussions Subject: RE: Files opening s l o w l y.... OK, I'm sorry, I wasn't very clear in the beginning. The servers are Nt 2000 running tcp/ip. The desktops are win 2000 running tcp/ip. The servers are also running AppleTalk for our Mac clients (very few) to file share with. The desktop are NOT using AppleTalk. I only mentioned the AppleTalk because its common factor. Sorry again, Mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ed Esgro Sent: Wednesday, February 27, 2002 10:26 AM To: NT 2000 Discussions Subject: RE: Files opening s l o w l y.... Mike, The machines that are using appletalk. They are IBM machines? Do they use TCP/IP also? Which protocol is more important to them? The server they are connecting to to retrieve these files... is it using tcp/ip to connect or appletalk? Which ever it is bump up the priority of that protocol in the bindings list. -----Original Message----- From: Mike Staines [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 27, 2002 10:16 AM To: NT 2000 Discussions Subject: RE: Files opening s l o w l y.... The problem is not with Mac machines. The problems is with any machine that connects to the Win 2000 servers that are holding the files. Sorry If I was unclear. Mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ed Esgro Sent: Wednesday, February 27, 2002 9:54 AM To: NT 2000 Discussions Subject: RE: Files opening s l o w l y.... Macintosh has an updated Ethernet driver. Also make sure that you don't have to ports specifying the speed and duplex. I had this similar problem and had to change the ports for the Macs back to auto negotiate. -----Original Message----- From: Mike Staines [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 27, 2002 9:47 AM To: NT 2000 Discussions Subject: Files opening s l o w l y.... OK, Here's a good one. Last weekend My company installed a Cisco 6500 series switch. (big monster machine, huge back plane, lots of ports) Ever since we did this we have had a problem opening files in applications off of the server. When a user tries to open a file IN an application (mostly word and excel) that is saved on a server, it takes forever to open. If I transfer the file from the server to the local machine, it opens up just fine in a few seconds. I looked and found all the servers having this problem, were running AppleTalk and Mac services. Cisco suggested turning off Spanning tree Protocol which I did. but to no avail. so I took a look with a sniffer. When I did a file transfer, the sniffer reported back that the right amount of data was being transferred (If I moved a file of 7 meg the sniffer showed a little more then 7 meg of data was transferred between my machine and the server). When I opened the same file from excel, but off of the server and not my local machine, the sniffer showed over 35 MEG of data was transferred! I am at loss, I cant figure where this data came from, and where it is going. I am more of an old school tech and don't have a lot of experience with theses switches. Any ideas, suggestions, comments are welcome/needed. Thanks Mike Staines. ********************************************************************** This email is not an official statement of the Waikato Regional Council unless otherwise stated. Visit our website http://www.ew.govt.nz ********************************************************************** ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
