System error 53 on RAS from XP to NT

[Guest]

After upgrading my machine to XP, i can no longer map a drive to my brother's machine when connected over RAS. The ras connections is made fine, I can both ping his IP address and the name of his machine. However when I try to NET USE a drive I get an error 'System error 53 has occurred, The network path was not found'. Neither can I access the machine from explorer by entering the IP address or the Network Name. All this was fine when it was NT to NT. Service packs are upto date on both ends. Unfortunately upgrading his machine is not a runner at the moment. Would appreciate any help as this is driving me nuts

 

[dave]

Hi Paul,
I've forgotten everything I ever new about RAS and NT,
but the first thing I'd check is the ability to see both
machines in the same workgroup. It's very possible that
XP assigns a different default workgroup-name than NT
(such as "MSHOME" instead of "WORKGROUP").

If they have the same workgroup name but still can't see
each other, make sure that 'Client for Windows
Networking' and 'File and Pring Sharing' are enabled over
matching protocols. XP pretty much does away with
NETbeui and older protocols, so ensure your NT machine is
setup to use IP for all Windows Networking stuff.

I hope it's that easy, cause that's all I got.

GL.
/dave

-----Original Message-----
After upgrading my machine to XP, i can no longer map a

drive to my brother's machine when connected over RAS.
The ras connections is made fine, I can both ping his IP
address and the name of his machine. However when I try
to NET USE a drive I get an error 'System error 53 has
occurred, The network path was not found'. Neither can I
access the machine from explorer by entering the IP
address or the Network Name. All this was fine when it
was NT to NT. Service packs are upto date on both ends.
Unfortunately upgrading his machine is not a runner at
the moment. Would appreciate any help as this is driving
me nuts!

 

[Guest]

Thanks Dave, but I have checked all that. Things have no progressed in a very weird direction ! I tried the same thing in my office and got the same result. However, if I put the NT machine on the LAN, fo my NET USE, disconnect the NT from the LAN, ras into it, then I can use my dirve happily away. Not much use to me but strange. I have also found that a customers site reacting in the same way on some of their NT machines, however others work. I have compared all the n/w setting and cannot find anything different. It's now at the stage that I am determined to get to the bottom of this.