Mapping drive to shared folder

  • Thread starter Thread starter wesley.d.gibbs
  • Start date Start date
W

wesley.d.gibbs

I know that the IP of the machine that I want to contact.
Why when I ping 164.224.186.232
does it say: Reply from 10.16.0.130
Shouldn't the reply say: Reply from 164.224.186.232?
Why is it a different address?
 
What is the result of a tracert test to that computer? Is it inside or
outside your network?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
 
The machine that I'm trying to ping (eventually map a drive too, once I
can ping it) is on another network. But the machine that I'm typing
the ping command on can ping other servers on the same network as the
server w/ip: 164.224.186.232.
 
The machine that I'm trying to ping (eventually map a drive too, once I
can ping it) is on another network. But the machine that I'm typing
the ping command on can ping other servers on the same network as the
server w/ip: 164.224.186.232.
Click to expand...

You might do best to just post the results of the
Tracert command (post text not graphic, don't retype
it, but get it from copy/paste or redirection.)

A failed ping can return "reply from", e.g., in the
case of an intermediate router returning "host
unreachable."

Is there any relationship between the target IP
and the "reply from IP"?

Are there any "NAT" (address translator routers)
involved?
 
I am unable to do a tracert command, it gives me an "Access denied"
message.

There is no relationship between the target IP and the "reply from IP"
that I can see...

Sorry this message probably doesn't help out that much, but do you have
any suggestions
on the possible problems?

My situation:

I can map drives to three different servers on a Legacy domain called
AAA from a machine on a
domain called BBB. But there is 1 server on domain AAA that I cannot
map a shared folder to
from the machine on domain BBB. The message that I get is: "Network
path not found".....

Any suggestion\thoughts are appreciated. The people administering
domain BBB are not much
help here and I don't have the permissions to do much on this machine
(can't do the tracert command).

Thank you in advance,
Wes
 
I am unable to do a tracert command, it gives me an "Access denied"
message.
Click to expand...

Then either you are not the Admin or your machine is
SICK.

Tracert (and/or Pathping) should be available and probably
should run for anyone logged on.
There is no relationship between the target IP and the "reply from IP"
that I can see...
Click to expand...

What is the rest of the message on the Reply from?
Sorry this message probably doesn't help out that much, but do you have
any suggestions on the possible problems?
Click to expand...

A routing problem.

It seems you are NOT getting a reply from the real destination
so some intermediate (router) station is giving you a "reply
from" with some message.

Without that message we cannot help....
My situation:

I can map drives to three different servers on a Legacy domain called
AAA from a machine on a
domain called BBB. But there is 1 server on domain AAA that I cannot
map a shared folder to
from the machine on domain BBB. The message that I get is: "Network
path not found".....
Click to expand...

Unless you are differentially filter ONLY some ports and
allowing others (common with NAT routers and firewalls)
then a general rule is that if you cannot PING you cannot
do anything else with IP (map drives, web etc.)
Any suggestion\thoughts are appreciated. The people administering
domain BBB are not much
help here and I don't have the permissions to do much on this machine
(can't do the tracert command).
Click to expand...

Isolate and simplify. Mapping drives is generally
too complex to troubleshoot (directly) effectively.

Try "Net Use * \\Server\Share * /user:Domain\User"

See if you can map the share explicitly from the command
line -- the first time, leave OFF the "* user:" and see if
it works before you add this in. If it works ONLY with
the second method (adding user and password) then you
have an AUTHENTICATION problem.

If it doesn't work even with explicit user name and password
then authentication is not likely your issue.

You can also use the IP Address instead of server name you
can eliminate or prove DNS issues.
 
Back
Top