Re: Unclear browstat Output
- From: ed9213 <ed9213@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 15 Mar 2008 08:59:00 -0700
John,
I think you've hit upon something definitive here.
I was able to map to the shares via the command line and copy files in both
directions using both the command line and Windows Explorer.
(I had suffered more consistent crashes if I used "My Network Places" to
find the shares and connect to them in the past, and stopped using that
route. Still suffered crashes, but less often if mapping them directly from
within Windows Explorer: Tools|Map Network Drive| ....)
Large files seemed to choke the system more often, but this time they dd not.
So, using your instructions, I mapped to the shares via the command line and
was able to copy files in both directions without crashing.
What does that indicate? Is there a flaw in Windows Explorer or perhaps a
tweak needed somewhere?
Thanks, again.
--
ed
"John Wunderlich" wrote:
=?Utf-8?B?ZWQ5MjEz?= <ed9213@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in.
news:436D2D17-9D03-4898-9A64-51F48ADB5333@xxxxxxxxxxxxx:
John,
Thanks for the suggestion. I turned off the firewalls on the XP
machines and re-booted them. The others don't have software
firewalls. The LAN is behind the hardware firewall in our router.
The results are identical.
BTW, I can use the other XP machines can see the share on
ERELKES3, but ERELKES3 chokes when trying to read the shares on
the other XP machines or transfer files.
If I read this correctly, you can connect to the other machine OK but
things crash when you try to read or copy. If you are connecting OK,
then you are past the Browser portion of the protocol.
I wonder what would happen if you try to map a network drive from a
command prompt (no explorer window involved) and then access it from
its drive letter...
To map a network drive, try:
Start->run->cmd
then in the command window, enter:
net use * \\computername\sharename
It should respond by returning the drive letter that was mapped (if
successful).
Then try to open an Explorer window and try to access the network
machine from its mapped drive letter.
Good Luck, :-)
John
- Follow-Ups:
- Re: Unclear browstat Output
- From: John Wunderlich
- Re: Unclear browstat Output
- References:
- Re: Unclear browstat Output
- From: John Wunderlich
- Re: Unclear browstat Output
- From: ed9213
- Re: Unclear browstat Output
- From: John Wunderlich
- Re: Unclear browstat Output
- From: John Wunderlich
- Re: Unclear browstat Output
- Prev by Date: Re: NetBios over TCP/IP
- Next by Date: Re: Network Connections dialogue box
- Previous by thread: Re: Unclear browstat Output
- Next by thread: Re: Unclear browstat Output
- Index(es):
Relevant Pages
|