remote connection

[Guest David Brown]

We have a windows XP laptop with the firewall service stopped and the remote

connect enabled that we still cannot connect or ping the system. What else

can block an IP connection? The system works fine but we can not support it

remotely even with PC anywhere.

Thanks,

-David

[Guest 8n20_C#]

Re: remote connection

 

"David Brown" wrote:

> We have a windows XP laptop with the firewall service stopped and the

> remote connect enabled that we still cannot connect or ping the system.

 

Hi.

If you can't ping the computer, the problem is in the network configuration,

not in remote desktop.

Can you surf the internet with the incriminated computer?

Bye!

[Guest David Brown]

Re: remote connection

 

The system is fully functional. Yes you can surf the internet, connect

wireless, VPN, Outlook, etc all work. No remote connecting.

It has got us stumped!

"8n20_C#" <enzoc73@msn.com> wrote in message

news:52338E2E-E978-4FD2-AB96-BC5EC2D6E62F@microsoft.com...

> "David Brown" wrote:

>> We have a windows XP laptop with the firewall service stopped and the

>> remote connect enabled that we still cannot connect or ping the system.

>

> Hi.

> If you can't ping the computer, the problem is in the network

> configuration,

> not in remote desktop.

> Can you surf the internet with the incriminated computer?

> Bye!

>

>

[Guest 8n20_C#]

Re: remote connection

 

"David Brown" wrote:

> The system is fully functional. Yes you can surf the internet, connect

> wireless, VPN, Outlook, etc all work. No remote connecting.

> It has got us stumped!

 

But if you type "ping pc_name" at the command prompt of a

PC, where pc_name is the name or the IP of the computer you

can't connecto to with remote connection, what's the result?

 

Second, you say remote desktop is active on the pc you

can't connect to. Do you mean that in system properties,

remote connection tab, the check box in the remote desktop

section is checked?

 

Third, try to uncheck that box, then enable Windows firewall.

Confirm and recheck the box, go back to the firewall and

ensure that Windows has added the "remote desktop connection"

exception.

Then try to connect.

 

Bye!

[Guest Big Al]

Re: remote connection

 

David Brown wrote:

> We have a windows XP laptop with the firewall service stopped and the remote

> connect enabled that we still cannot connect or ping the system. What else

> can block an IP connection? The system works fine but we can not support it

> remotely even with PC anywhere.

> Thanks,

> -David

>

>

Maybe your router? And I'm not IT person, but maybe your provider?

The latter is kinda far fetched.

[Guest David Brown]

Re: remote connection

 

The PC is registered with the DNS and pinging by name resolves the IP

address. Ping by name or ip results in a no response message and thus the

reason we cannot remote to the PC. Yes the remote desktop connection is

checked on the remote tab. BTW I stopped the firewall service as well.

 

I have enabled internet remote connect from the advanced tab in the network

configuration and still nothing. What a challenge this one is!

"8n20_C#" <enzoc73@msn.com> wrote in message

news:649C05AE-E91A-4FC0-B1E2-077A285B7BB4@microsoft.com...

> "David Brown" wrote:

>> The system is fully functional. Yes you can surf the internet, connect

>> wireless, VPN, Outlook, etc all work. No remote connecting.

>> It has got us stumped!

>

> But if you type "ping pc_name" at the command prompt of a

> PC, where pc_name is the name or the IP of the computer you

> can't connecto to with remote connection, what's the result?

>

> Second, you say remote desktop is active on the pc you

> can't connect to. Do you mean that in system properties,

> remote connection tab, the check box in the remote desktop

> section is checked?

>

> Third, try to uncheck that box, then enable Windows firewall.

> Confirm and recheck the box, go back to the firewall and

> ensure that Windows has added the "remote desktop connection"

> exception.

> Then try to connect.

>

> Bye!

>

[Guest 8n20_C#]

Re: remote connection

 

"David Brown" ha scritto:

> The PC is registered with the DNS and pinging by name resolves the IP

> address. Ping by name or ip results in a no response message and thus

> the reason we cannot remote to the PC.

 

This is strange...

For this reason i don't think the problem is with remote desktop connection.

 

How are the IPs assigned in your network?

I suppose there's a router with a dhcp server, right?

 

Check the properties of the dhcp server, control that it can assign IPs

(it could have ended the range of IPs it can assign).

Then type ipconfig at the cmd of the PC you cannot connect to:

the ip you see is compatible with IPs of your network?

 

Is the incriminated PC able to receive an IP, or it's configured to

have a static IP?

 

You must resolve this ping problem before using desktop connection.

Bye!

[Guest David Brown]

Re: remote connection

 

There is only one segment and the IP are dynamic. The DHCP is in the L3

Switch and it is a good IP. If I change it to a static from the reserved

range I get the same results.

Mystified!

"8n20_C#" <enzoc73@msn.com> wrote in message

news:7AB27CE3-06C1-439F-A797-75AA6F59E054@microsoft.com...

> "David Brown" ha scritto:

>> The PC is registered with the DNS and pinging by name resolves the IP

>> address. Ping by name or ip results in a no response message and thus

>> the reason we cannot remote to the PC.

>

> This is strange...

> For this reason i don't think the problem is with remote desktop

> connection.

>

> How are the IPs assigned in your network?

> I suppose there's a router with a dhcp server, right?

>

> Check the properties of the dhcp server, control that it can assign IPs

> (it could have ended the range of IPs it can assign).

> Then type ipconfig at the cmd of the PC you cannot connect to:

> the ip you see is compatible with IPs of your network?

>

> Is the incriminated PC able to receive an IP, or it's configured to

> have a static IP?

>

> You must resolve this ping problem before using desktop connection.

> Bye!

>

>

[Guest David Brown]

Re: remote connection

 

figured it out.. had a bad install of the cisco vpn client. uninstalled

and everything cleared up. reinstalled vpn client from another install set

and it is now working.

Thanks to everyone.

"David Brown" <dbrown@tvores.com> wrote in message

news:uFMsNzfsIHA.1316@TK2MSFTNGP06.phx.gbl...

> There is only one segment and the IP are dynamic. The DHCP is in the L3

> Switch and it is a good IP. If I change it to a static from the reserved

> range I get the same results.

> Mystified!

> "8n20_C#" <enzoc73@msn.com> wrote in message

> news:7AB27CE3-06C1-439F-A797-75AA6F59E054@microsoft.com...

>> "David Brown" ha scritto:

>>> The PC is registered with the DNS and pinging by name resolves the IP

>>> address. Ping by name or ip results in a no response message and thus

>>> the reason we cannot remote to the PC.

>>

>> This is strange...

>> For this reason i don't think the problem is with remote desktop

>> connection.

>>

>> How are the IPs assigned in your network?

>> I suppose there's a router with a dhcp server, right?

>>

>> Check the properties of the dhcp server, control that it can assign IPs

>> (it could have ended the range of IPs it can assign).

>> Then type ipconfig at the cmd of the PC you cannot connect to:

>> the ip you see is compatible with IPs of your network?

>>

>> Is the incriminated PC able to receive an IP, or it's configured to

>> have a static IP?

>>

>> You must resolve this ping problem before using desktop connection.

>> Bye!

>>

>>

>

>

[Guest 8n20_C#]

Re: remote connection

 

"David Brown" wrote:

> had a bad install of the cisco vpn client. uninstalled and everything

> cleared up. reinstalled vpn client from another install set and it is now

> working.

> Thanks to everyone.

 

Thank you for the feedback.

I'm glad you've solved your problem.

Bye!