Ok. Then do the registry edit for the vista client and the console
edit for XP.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\LSA\

Change the key LmCompatibilityLevel from "3" to "1".

Check out http://support.microsoft.com/kb/239869 for details.

FYI:

I did your steps but I was not successful. However I also tryed this and
had some amount of success...

I created a TEST folder on the XP and then I shared it and gave it all
permissions. Then I created a text file in that folder. Then I went to the
vista computer and I was actually able to open the file. Thats the first
time I could do that.

Then I copied two smalll files from Vista to the new Test folder on XP and
that worked too.

But when I try to open those files, it times out.

It seems to act like there are too many files on my production shared folder
and perhaps the XP is so slow it times out on the Vista before it finishes
seeing the folder tree...?? Can it be something like that?

BB
wrote in message
...
Ok. Then do the registry edit for the vista client and the console
edit for XP.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\LSA\

Change the key LmCompatibilityLevel from "3" to "1".

Check out http://support.microsoft.com/kb/239869 for details.

I think it would be unlikely that XP is too slow to see the tree, also
if this was the cause, then it would not have been able to see the files
or copy it.

Just to verify, you still have the firewall and anti-virus disabled right?

Sachin

Bikini Browser wrote:
FYI:

I did your steps but I was not successful. However I also tryed this
and had some amount of success...

I created a TEST folder on the XP and then I shared it and gave it all
permissions. Then I created a text file in that folder. Then I went to
the vista computer and I was actually able to open the file. Thats the
first time I could do that.

Then I copied two smalll files from Vista to the new Test folder on XP
and that worked too.

But when I try to open those files, it times out.

It seems to act like there are too many files on my production shared
folder and perhaps the XP is so slow it times out on the Vista before it
finishes seeing the folder tree...?? Can it be something like that?

BB
wrote in message
...
Ok. Then do the registry edit for the vista client and the console
edit for XP.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\LSA\

Change the key LmCompatibilityLevel from "3" to "1".

Check out http://support.microsoft.com/kb/239869 for details.

Yes they are still disabled....

I found this on the Event logs on the XP Computer. Could this be causing
some of our problems?

The master browser has received a server announcement from the computer
BENGUZMAN-VISTA that believes that it is the master browser for the domain
on transport NetBT_Tcpip_{26950295-025. The master browser is stopping or an
election is being forced.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


MRxSmb
event id 8003

Dale


"Sachin" wrote in message
...
I think it would be unlikely that XP is too slow to see the tree, also if
this was the cause, then it would not have been able to see the files or
copy it.

Just to verify, you still have the firewall and anti-virus disabled right?

Sachin

Bikini Browser wrote:
FYI:

I did your steps but I was not successful. However I also tryed this
and had some amount of success...

I created a TEST folder on the XP and then I shared it and gave it all
permissions. Then I created a text file in that folder. Then I went to
the vista computer and I was actually able to open the file. Thats the
first time I could do that.

Then I copied two smalll files from Vista to the new Test folder on XP
and that worked too.

But when I try to open those files, it times out.

It seems to act like there are too many files on my production shared
folder and perhaps the XP is so slow it times out on the Vista before it
finishes seeing the folder tree...?? Can it be something like that?

BB
wrote in message
...
Ok. Then do the registry edit for the vista client and the console
edit for XP.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\LSA\

Change the key LmCompatibilityLevel from "3" to "1".

Check out http://support.microsoft.com/kb/239869 for details.

That message is normal in a non-domain environment - it's for the
election of a master browser so you can find machines by netbios name.

Did you follow Mick Murphy's advice?

Check my post for Wired Yes and Wireless NO

Dale


wrote in message
...
Ok. Then do the registry edit for the vista client and the console
edit for XP.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\LSA\

Change the key LmCompatibilityLevel from "3" to "1".

Check out http://support.microsoft.com/kb/239869 for details.