Networking
cancel
Showing results for 
Search instead for 
Did you mean: 

GUI v cmd listing of remote files

Robert A. Pierce
Frequent Advisor

GUI v cmd listing of remote files

Good afternoon.

I'm having an issue with a server at another location in our wan.

If I run at a command prompt:

c> dir \\remotesvr\share

I get a list of directories and files:

[snip]
8 File(s) 929 bytes
140 Dir(s) 2,099,658,973,184 bytes free

HOWEVER

if I run

start \\remotesvr\share
OR map a drive to \\remotesvr\share,
all I get is the flashlight for about fifteen minutes before I get a response.

On the same server, \\remotesvr\OtherShare has
40 File(s) 513,553,062 bytes
99 Dir(s) 2,099,659,321,344 bytes free

and it pops right up.

Is there a number of directories, over which the gui freezes when getting directory information?

Why would it take so long to show the directory?

Thanks,

Rob

9 REPLIES
Omar Senussi
Honored Contributor

Re: GUI v cmd listing of remote files

Hi Rob,
How are you connecting to the remote server?
Does start->run \\remotesvr\share work?
If you can keep your head whilst all around you are losing theirs... You haven't understood the situation!
Robert A. Pierce
Frequent Advisor

Re: GUI v cmd listing of remote files

Omar,

> Does start->run \\remotesvr\share work?

It works the same as

start \\remotesvr\share
OR map a drive to \\remotesvr\share --

Long wait time with the flashlight.

Thanks,

Rob
Omar Senussi
Honored Contributor

Re: GUI v cmd listing of remote files

Hi again Robert,
Sorry, don't think you mentioned OS'es on your servers.. but take a look at the following.. hope it helps http://search.microsoft.com/search/results.aspx?view=en-us&st=b&na=82&qu=directory+enumeration+remote+server+slow
If you can keep your head whilst all around you are losing theirs... You haven't understood the situation!
Robert A. Pierce
Frequent Advisor

Re: GUI v cmd listing of remote files

Omar,

Remote server is 2000 server; we're looking at it from XP Pro and 2000 clients.

Thanks,

Rob
Omar Senussi
Honored Contributor

Re: GUI v cmd listing of remote files

Ok, So when u say remote server, is there a local server? and do the servers see each other the way you are trying to do with the workstations?
Is the share a default share?.. if so try creating a new one with a name.
Have you checked permissions on the remote share?
Also, are you connecting using VPN?? how remote is remote?
If you can keep your head whilst all around you are losing theirs... You haven't understood the situation!
Jon Finley
Honored Contributor

Re: GUI v cmd listing of remote files

Does this server behave in the same way from both XP and the 2000 clients?

Jon
"Do or do not. There is no try!" - Yoda
Omar Senussi
Honored Contributor

Re: GUI v cmd listing of remote files

Also..
You might get some hints and checks here http://support.microsoft.com/default.aspx?scid=kb;en-us;314067#19
and
http://forums1.itrc.hp.com/service/forums/bizsupport/categoryhome.do?categoryId=185
If you can keep your head whilst all around you are losing theirs... You haven't understood the situation!
Norman_21
Honored Contributor

Re: GUI v cmd listing of remote files

Hi

Map a drive from the command prompt:

net use m: \\remotesvr\share

To restore current connection at each logon:

net use /persistent:yes

If the net use worked, then just create a batch file and setup the logon script in the remote server.

As far as the delay. If the remote 2000 Server is a WINS and DNS server, add the the ip address of WINS & DNS in your WinXP Client and make bind them to be the first in the list. Now see if you still have the same delay.

I think that it's a good idea to re-organize the folders and give permissions accordingly since I'm sure it consumes bandwidth when users try to connect at the same time?

Hope this help
"Attitudes are contagious, is yours worth catching"/ My first point was given by SEP on January 31, 2003
Guy Humphreys
Valued Contributor

Re: GUI v cmd listing of remote files

Rob,

What is the bandwidth between your client and the remote server? is it heavily loaded?

If it is small or heavily used, then the GUI listing may just time out, by comparison the CLI version is requesting and sending far less data and so will come back fine.

I used to see this happen all the time over 64K links, I know these are pretty rare nowadays but if the link is saturated by other traffic you could have only this amount or less 'free'.

Cheers
Guy
'If it ain't broke, don't fix it!'