Mapping drives to another subnet

hi guys,

This one is baffling me...

I have one PC (A), WXP Pro, SP2 in one subnet (A) of my network and want to map a shared folder from a WNT 4.0 Server (PC B) that lives on another subnet (B). There are no filterings in the router, I believe.

The folder is shared so anyone can map to it (it holds a license for a piece of software).

Under this condition, if I change PC A IP address and move it to a port on subnet (B), it works and can "see" the shared folder and all is well. If I go back to the original settings on subnet A it won't "see" the folder and no mapping occurs.

Summary: Novell client installed, TCP/IP, IPX/SPX, NetBEUI all installed. LMHOSTS lookup active. Me? I'm lost!

Any ideas?

Cheers!

 

With the PC1 on subnet A, is your network routed properly so that it can 'see' the server on subnet B?

Domain or workgroup?

Why do you need NetBEUI?

Moving this from XP to Networking section.

 

NetBEUI: I was desperate and trying everything I could related to Microsoft Networking. No, I don't need it.

Domain or group: As I said above, it is a Novell environment not Microsoft. No domains as such.

Please read again my description of the problem:

PC1 (sub A) does not see PC2 (sub B) if their IPs are in different subnets.
PC1 sees PC2 if their subnets are the same.

Thanks!

 

Which version of Novell?

Is the Win NT server recognised by the Novell system or are you sharing it directly (how did you set up the share?)?

 

Yes, the server is recognized by Novell, it is hanging on the network. The share is set so 30 users only can login (maximum number of concurrent licenses) and the login has a particular name that is set on the logon when the users need to use that particular program. It has been working for years.

I've just found out that the problem is not the networking but some change that happened to the new XP image, probally related to Novell settings. I built a brand new XP from the scratch and could map to the server from other subnet so the problem is in XP not in the network.

At least I isolated the problem...

Cheers!