having a problem mapping a drive

[spanky]

in office A, a computer named mickey (win xp pro) has two shares. in that same office, another computer named daisy (win xp pro) accesses those shares via mapped drives. now i need to configure a laptop (win 98) to also access those shares via mapped drives. i have it set up to reconnect to these shares upon boot. while in office A, everything works fine.

now, the laptop has been moved to office B. this office is across campus and on a different subnet. in office B, the laptop is unable to reconnect it's mapped drives. any idea's as to what may be going on here? sorry if i am being vague.

 

[futuristicmonkey]

Are you trying to map to the drives using a dns name, or an ip address?

 

[kevnich2]

If office B is on a different subnet, of course you won't be able to reconnect it's mapped drives because it can't see anything in Office A. The simple solution if the two offices are connected to the same network is to change the subnet on the laptop to be able to see computers in office A.

 

[spanky]

Originally posted by: futuristicmonkey
Are you trying to map to the drives using a dns name, or an ip address?

i am mapping the drives via ip

 

[spanky]

Originally posted by: kevnich2
If office B is on a different subnet, of course you won't be able to reconnect it's mapped drives because it can't see anything in Office A. The simple solution if the two offices are connected to the same network is to change the subnet on the laptop to be able to see computers in office A.

in the past, i have been able to map a drive from a different subnet (with the difference now being i am trying to connect to a win xp computer, where as in the past, i was mapping a drive to a linux server).

 

[ColKurtz]

Originally posted by: kevnich2
If office B is on a different subnet, of course you won't be able to reconnect it's mapped drives because it can't see anything in Office A. The simple solution if the two offices are connected to the same network is to change the subnet on the laptop to be able to see computers in office A.

What? No offense, but I'm not sure where to begin with this so let's just file under "bad advice". Google "routers".

OP - Can you ping the remote server? Can you communicate with other systems on the remote subnet? If you do a NET VIEW \\(IP address of remote system), what error do you get?

 

[spanky]

Originally posted by: ColKurtz

Originally posted by: kevnich2
If office B is on a different subnet, of course you won't be able to reconnect it's mapped drives because it can't see anything in Office A. The simple solution if the two offices are connected to the same network is to change the subnet on the laptop to be able to see computers in office A.

What? No offense, but I'm not sure where to begin with this so let's just file under "bad advice". Google "routers".

OP - Can you ping the remote server? Can you communicate with other systems on the remote subnet? If you do a NET VIEW \\(IP address of remote system), what error do you get?

yes, i can ping "mickey" (the remote server). i have not tried to communicate with other computers on office a's subnet. when you say communicate, do you mean ping it, or access a share? i am going to office b now, so i will try "net view" and report back in.

 

[ColKurtz]

Hmm... I would have guessed you could not ping the remote system. If you're mapping to the IP address of the system, there shouldn't be any network name/WINS issues, so if you're able to ping you should be able to connect.

when you say communicate, do you mean ping it, or access a share?

I guess I orginally meant ping but now I'd be interested in both.

 

[spanky]

i can definitely ping mickey's ip, but when i try to use the net view command, i get the following error messege:

"error 53: the computer name specified in the network path cannot be located. make sure you are specifying the computer name correctly, or try again later when the remote computer is available"

the remote computer, mickey, is definitely on. when i try to map a drive from this laptop to mickey, i get the same error as the one mentioned above.

 

[ColKurtz]

(let's assume mickey's IP address is 100.100.100.100)

Are you doing a NET VIEW \\100.100.100.100, or a NET VIEW \\MICKEY?

 

[spanky]

Originally posted by: ColKurtz
(let's assume mickey's IP address is 100.100.100.100)

Are you doing a NET VIEW \\100.100.100.100, or a NET VIEW \\MICKEY?

i've tried both, and recieve the same error messege. this is wierd... i can ping it, and that's about it.

 

[ColKurtz]

I'm stumped. You might try mapping the drive from another system on the remote subnet to see if it's something specific to your laptop and/or win98, or if it's a general router/connection problem.

 

[ehanson]

What shares are listed with the laptop using NET USE ?

 

[spanky]

FYI for those who followed this problem... it was a config issue with the window xp firewall on the host "mickey".