Re: PING gets an IP from a name, but no reply from the IP
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Wed, 6 Sep 2006 14:22:45 +0100
Inine
Here is the info for the machines.Ok same subnet.
NAME and IP
DLEC-103-DT 192.168.168.110
DLEC-130-DT 192.168.168.103
Here is the problemOk.
DLEC-130-DT can ping and get a reply from DLEC-103-DT and establish a
remote
desktop connection.
The Name (DLEC-130-DT) gets translated into an IP address, just is notNo replies, check ICMP (Internet Control Message Protocol), "Allow incoming
sending any replies.
echo request".
Even if you don't have Windows FW enabled, please check if you have any
antivirus with builtin FW that is bloking the request.
To confirm that use Portqry.exe
http://support.microsoft.com/kb/310099/
The fact that you are allowed to do Remote Desktop connections doesn't mean
anything, it only means that your server is accepting connections on 3389
TCP - Port. Now For you to see that this isn't a resolution problem try like
this: Connect by using remote desktop, but instead of using the name of the
server use its IPAddress, you'll see that you're allowed to connect either
way.
You can also confir the 3389 Port by using Portqry
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"Scott Sendelbach" <ScottSendelbach@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:1D78706D-74F4-4184-A145-86E690C11F58@xxxxxxxxxxxxxxxx
Okay.
Here is the info for the machines.
NAME and IP
DLEC-103-DT 192.168.168.110
DLEC-130-DT 192.168.168.103
Here is the problem
DLEC-130-DT can ping and get a reply from DLEC-103-DT and establish a
remote
desktop connection.
DLEC-103-DT and other devices can PING but get no replies from DLEC-130-DT
and unable to establish a remote desktop connection.
It would appear that DLEC-130-DT has some issues somewhere down the line.
I have done IPCONFIG/RELEASE IPCONFIG/RENEW IPCONFIG /FLUSHDNS IPCONFIG
/REGISTERDNS NBTSTAT -RR and both machines and the DNS server.
The Name (DLEC-130-DT) gets translated into an IP address, just is not
sending any replies.
This has a standard load on it and nothing different that any other
computer
on the network. It is running XP w/SP2.
The user would like to be able to remote desktop into this so they can
work
from home, but so far it is not working and all the settings are just like
all the other machines on the network.
There is something on this machine that is preventing a response and
establishing a remote desktop connection.
What else can I do to resolve this?
"Jorge Silva" wrote:
Hi
I hope Anthony doesn't mind for me to step in....
Are these machines on different networks?
check routing paths. Check routers configuration.
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"skhips" <skhips@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9C3468E3-7F04-4C81-8ED7-C33EF4852C06@xxxxxxxxxxxxxxxx
after resolving the name ping by default attmepts 4 times, if it is not
replying what message are u getting, e.g "destination host unkown".
"Scott Sendelbach" wrote:
What is going on with this?
I can ping a computer name on the network and PING resolves the name
to
an
IP address, but there is no reply from the IP address.
What setting/configuration do I need to modify to fix this. It has
affected
quite a few users and I am concerned that soon there will be
communication
issues as a result of no reply from the IP address even though it has
been
resolved from a name.
.
- References:
- Re: PING gets an IP from a name, but no reply from the IP
- From: Jorge Silva
- Re: PING gets an IP from a name, but no reply from the IP
- From: Scott Sendelbach
- Re: PING gets an IP from a name, but no reply from the IP
- Prev by Date: Re: Name Resolution oddity...or not?
- Next by Date: How Do I get the Hotfix
- Previous by thread: Re: PING gets an IP from a name, but no reply from the IP
- Next by thread: Re: PING gets an IP from a name, but no reply from the IP
- Index(es):
Relevant Pages
|
