RDP

[Guest]

Gurus.
I am new to all this network stuff so easy on me..

I have network1 far location: I run windows 2000 server(dc,dhcp), a few
printers and a few WS
I can ping localhost my server and get good reply, I can ping server from ws
no problem

I have network2 locally : I run windows 2000 server (dc,dhcp) a few printer
and a few WS, I can ping locally from server to ws and from WS to server no
problem.

Both network1 and network2 are connected by vpn to each other, here is my
problem. From network2 I can ping printer and WS on network1 but CAN NOTping
Server on network1. CAN NOT RDP to it.

is this a terminal services problem, it seems like TS is running on server
in network1 but maybe is corrupted should I uninstall it and install it again
to finally rdp to it or should I stop the services and start in order to
accomplish this.

Thanks for the help guys.

 

[Richard G. Harper]

Sounds like you need to set up and run WINS servers at both sites and have
them replicate to each other.

--
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

 

[Herb Martin]

Both network1 and network2 are connected by vpn to each other, here is my

problem. From network2 I can ping printer and WS on network1 but CAN NOTping
Server on network1. CAN NOT RDP to it.

Anytime someone says, "I cannot ping" without
saying "by IP" or "just by Name" without specifying
then the report is too vague.

Once you say, "I cannot ping by IP" it is necessary
to then try "tracert" to show where the traffic seems
to stop, and to supply info about any firewalls or
filters that might be blocking ICMP (used by both
tracert and ping.)

If there is any chance of ICMP being blocked then
the next tool is something like 'telnet to webserver
port 80' (e.g., telnet www.domain.com 80 )
of a web server or something similar to see if
"regulary" (i.e., specific application traffic can
get through.)

[FYI: netcat (nc.exe) is a better tool than telnet
for this, but telnet is ubiquitiout on IP machines
and netcat must be found and added.]

 

[Guest]

Anytime someone says, "I cannot ping" without

saying "by IP" or "just by Name" without specifying
then the report is too vague.

My bad ,if I ping "by IP" I can not see the server on network1 , if I ping
by name I can not see the server on network1. all thi from server on
network2.

Once you say, "I cannot ping by IP" it is necessary
to then try "tracert" to show where the traffic seems
to stop, and to supply info about any firewalls or
filters that might be blocking ICMP (used by both
tracert and ping.)

those this still apply for both situations "by IP" or "by name" , there is a
regular firewall built on the router but nothing else, firewall should not be
as it was working fine a few days ago, but with comp. you never know.

If there is any chance of ICMP being blocked then
the next tool is something like 'telnet to webserver
port 80' (e.g., telnet www.domain.com 80 )
of a web server or something similar to see if
"regulary" (i.e., specific application traffic can
get through.)

Other WS on network1 can rdp network2 and run application I can also ping
"by IP" and "By name" every node on network1


Thanks for the help. and reply from all

Both network1 and network2 are connected by vpn to each other, here is my
problem. From network2 I can ping printer and WS on network1 but CAN NOTping
Server on network1. CAN NOT RDP to it.

Anytime someone says, "I cannot ping" without
saying "by IP" or "just by Name" without specifying
then the report is too vague.

Once you say, "I cannot ping by IP" it is necessary
to then try "tracert" to show where the traffic seems
to stop, and to supply info about any firewalls or
filters that might be blocking ICMP (used by both
tracert and ping.)

If there is any chance of ICMP being blocked then
the next tool is something like 'telnet to webserver
port 80' (e.g., telnet www.domain.com 80 )
of a web server or something similar to see if
"regulary" (i.e., specific application traffic can
get through.)

[FYI: netcat (nc.exe) is a better tool than telnet
for this, but telnet is ubiquitiout on IP machines
and netcat must be found and added.]


--
Herb Martin

Gurus.
I am new to all this network stuff so easy on me..

I have network1 far location: I run windows 2000 server(dc,dhcp), a few
printers and a few WS
I can ping localhost my server and get good reply, I can ping server from ws
no problem

I have network2 locally : I run windows 2000 server (dc,dhcp) a few printer
and a few WS, I can ping locally from server to ws and from WS to server no
problem.

Both network1 and network2 are connected by vpn to each other, here is my
problem. From network2 I can ping printer and WS on network1 but CAN NOTping
Server on network1. CAN NOT RDP to it.

is this a terminal services problem, it seems like TS is running on server
in network1 but maybe is corrupted should I uninstall it and install it again
to finally rdp to it or should I stop the services and start in order to
accomplish this.

Thanks for the help guys.

 

[Herb Martin]

My bad ,if I ping "by IP" I can not see the server on network1

Good report -- this generally means that you
have an IP (or basic network) problem.

BUT we must remember that it COULD just be an
ICMP (ping) problem due to firewalls or other
filtering.

, if I ping
by name I can not see the server on network1. all thi from server on
network2.

Name should always fail if IP fails (since your never
really ping by name but first lookup the name and then
perform the actual ping request.)

those this still apply for both situations "by IP" or "by name" , there is a
regular firewall built on the router but nothing else, firewall should not be
as it was working fine a few days ago, but with comp. you never know.

Normally you do know -- they are very reliable IF
you understand what is happening. If things are acting
"spooky" this is 99% a lack of knowledge on OUR
part (the other 1% are intermittent -- usually hardeware
-- problems and bugs, which might be anything.)

So when you say "still apply" why not be specific and
say, (something like) "there are two routers between
client and target" and "it fails to get a response from even
the FIRST router" or "it gets a response from both routers
but not the actual target" (or whatever really happens)?

Or you could just post the results so we can see them.

Other WS on network1 can rdp network2 and run application I can also ping
"by IP" and "By name" every node on network1


Thanks for the help. and reply from all

Show us your "IPConfig /all" output (copy and
paste the text, don't type it in or use graphics.)

From both client and server.

Tell us about your addressing on each subnet.

Tell us about any intervening routers, IP one each
NIC etc.

 

[Guest]

Herb.

Like I said before I am new to network but willing to learn.

So when you say "still apply" why not be specific and
say, (something like) "there are two routers between
client and target" and "it fails to get a response from even
the FIRST router" or "it gets a response from both routers
but not the actual target" (or whatever really happens)?

On my original post I explained that network1 and network2 and connected
together
by VPN, is there anyway besides router that can accomplish this?

When I said that I could ping WS on network1 from network2 and Ws from
network2 from network1 but could not get responde from server on network1
that does nopt tell you that router are fine and transmitting all messages
but from the target (server), am I missing something here?.

I agree with you in your statement that 99% might be lack of knowledge,
reason why we
have very good forums where people are willing to help as this is voluntary
work, nobody is forced to be here and help.

Thanks again