Suddenly can no longer connect to services or ping a windows XP ma

I recently noticed that remote desktop no longer works on a machine of mine.
I had not changed the configuration. All machines on the lan operate fine
with the exception of this one. The ports are listening:

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

but I cannot telnet to them or ping the machine any longer. Where should I
being troubleshooting?

"adandy" wrote in message
...
I recently noticed that remote desktop no longer works on a machine of
mine.
I had not changed the configuration. All machines on the lan operate fine
with the exception of this one. The ports are listening:

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

but I cannot telnet to them or ping the machine any longer. Where should I
being troubleshooting?

You should look and/or report the output from this command:

ipconfig /all

The interbutts is working just fine outbound, im posting this from the
machine but here it is anyhow


Windows IP Configuration

Host Name . . . . . . . . . . . . : myhostname
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Work LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NIC name
Physical Address. . . . . . . . . : 00-1D-7D-07-
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : my IP address
Subnet Mask . . . . . . . . . . . : 255.255.255.
Default Gateway . . . . . . . . . : my gateway address
DNS Servers . . . . . . . . . . . : 208.67.222.2
208.67.220.2
my gateway address
another dns
yet another dns

"Pegasus (MVP)" wrote:


"adandy" wrote in message
...
I recently noticed that remote desktop no longer works on a machine of
mine.
I had not changed the configuration. All machines on the lan operate fine
with the exception of this one. The ports are listening:

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

but I cannot telnet to them or ping the machine any longer. Where should I
being troubleshooting?

You should look and/or report the output from this command:

ipconfig /all

While I understand your wish to remain anonymous, you overdid it a little by
concealing most of your IP addresses. Please try to be a little less
secretive, perhaps my modifying your addresses just a little. Example:
Instead of saying
IP Address 208.67.220.10 you might say
IP Address 209.68.221.10

If you modify all subnet addresses (the first three packets) in the same way
then you're not giving away your real address but you're providing enough
information for respondents to draw some conclusions.

"adandy" wrote in message
...
The interbutts is working just fine outbound, im posting this from the
machine but here it is anyhow


Windows IP Configuration

Host Name . . . . . . . . . . . . : myhostname
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Work LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NIC name
Physical Address. . . . . . . . . : 00-1D-7D-07-
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : my IP address
Subnet Mask . . . . . . . . . . . : 255.255.255.
Default Gateway . . . . . . . . . : my gateway address
DNS Servers . . . . . . . . . . . : 208.67.222.2
208.67.220.2
my gateway address
another dns
yet another dns

"Pegasus (MVP)" wrote:


"adandy" wrote in message
...
I recently noticed that remote desktop no longer works on a machine of
mine.
I had not changed the configuration. All machines on the lan operate
fine
with the exception of this one. The ports are listening:

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

but I cannot telnet to them or ping the machine any longer. Where
should I
being troubleshooting?

You should look and/or report the output from this command:

ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : COMPUTER
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Work LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Work LAN
Physical Address. . . . . . . . . : 00-1D-7D-07-...
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.50
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
192.168.1.1

Does this help?

"Pegasus (MVP)" wrote:

While I understand your wish to remain anonymous, you overdid it a little by
concealing most of your IP addresses. Please try to be a little less
secretive, perhaps my modifying your addresses just a little. Example:
Instead of saying
IP Address 208.67.220.10 you might say
IP Address 209.68.221.10

If you modify all subnet addresses (the first three packets) in the same way
then you're not giving away your real address but you're providing enough
information for respondents to draw some conclusions.

"adandy" wrote in message
...
The interbutts is working just fine outbound, im posting this from the
machine but here it is anyhow


Windows IP Configuration

Host Name . . . . . . . . . . . . : myhostname
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Work LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NIC name
Physical Address. . . . . . . . . : 00-1D-7D-07-
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : my IP address
Subnet Mask . . . . . . . . . . . : 255.255.255.
Default Gateway . . . . . . . . . : my gateway address
DNS Servers . . . . . . . . . . . : 208.67.222.2
208.67.220.2
my gateway address
another dns
yet another dns

"Pegasus (MVP)" wrote:


"adandy" wrote in message
...
I recently noticed that remote desktop no longer works on a machine of
mine.
I had not changed the configuration. All machines on the lan operate
fine
with the exception of this one. The ports are listening:

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

but I cannot telnet to them or ping the machine any longer. Where
should I
being troubleshooting?

You should look and/or report the output from this command:

ipconfig /all

OK, these adresses are fine. Since they are stock-standard internal
addresses, there is no need to hide them from anyone. There are millions of
machines that have addresses in the subnet 192.168.1. Now let's dig a little
deeper:
1. Is the machine with the address 192.168.1.50 the host or the remote for
your RDP session?
2. What is the output of ipconfig /all for the other machine?
3. Are the two machines connected to the same internal network?
4. Did ping or remote desktop ever work?
5. Have you tried turning off your firewall while testing?

Your answers will probably generate another set of questions.


"adandy" wrote in message
...
Windows IP Configuration

Host Name . . . . . . . . . . . . : COMPUTER
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Work LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Work LAN
Physical Address. . . . . . . . . : 00-1D-7D-07-...
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.50
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
192.168.1.1

Does this help?

"Pegasus (MVP)" wrote:

While I understand your wish to remain anonymous, you overdid it a little
by
concealing most of your IP addresses. Please try to be a little less
secretive, perhaps my modifying your addresses just a little. Example:
Instead of saying
IP Address 208.67.220.10 you might say
IP Address 209.68.221.10

If you modify all subnet addresses (the first three packets) in the same
way
then you're not giving away your real address but you're providing enough
information for respondents to draw some conclusions.

"adandy" wrote in message
...
The interbutts is working just fine outbound, im posting this from the
machine but here it is anyhow


Windows IP Configuration

Host Name . . . . . . . . . . . . : myhostname
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Work LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NIC name
Physical Address. . . . . . . . . : 00-1D-7D-07-
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : my IP address
Subnet Mask . . . . . . . . . . . : 255.255.255.
Default Gateway . . . . . . . . . : my gateway address
DNS Servers . . . . . . . . . . . : 208.67.222.2
208.67.220.2
my gateway address
another dns
yet another dns

"Pegasus (MVP)" wrote:


"adandy" wrote in message
...
I recently noticed that remote desktop no longer works on a machine
of
mine.
I had not changed the configuration. All machines on the lan operate
fine
with the exception of this one. The ports are listening:

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

but I cannot telnet to them or ping the machine any longer. Where
should I
being troubleshooting?

You should look and/or report the output from this command:

ipconfig /all

1. The machine I am trouble shooting is the host.
2. The other machines on the lan are running linux and OS X and all operate
fine. The other windows machine was outside the lan and was experiencing the
same as the internal machines, not being able to communicate with the
services any longer. Inside the lan or out through the firewall. The only
thing between the machines on the lan is a switch and its switching
everything fine, and the plugs have been moved. I'm 100% sure its on the host
machine.
3. Some of them, it doesent work at the lan level so I would like to get
that to work first, I can take care of it from that point.
4. Only from localhost
5. firewall has been off, is off on the host machine

thanks for the help

"Pegasus (MVP)" wrote:

OK, these adresses are fine. Since they are stock-standard internal
addresses, there is no need to hide them from anyone. There are millions of
machines that have addresses in the subnet 192.168.1. Now let's dig a little
deeper:
1. Is the machine with the address 192.168.1.50 the host or the remote for
your RDP session?
2. What is the output of ipconfig /all for the other machine?
3. Are the two machines connected to the same internal network?
4. Did ping or remote desktop ever work?
5. Have you tried turning off your firewall while testing?

Your answers will probably generate another set of questions.


"adandy" wrote in message
...
Windows IP Configuration

Host Name . . . . . . . . . . . . : COMPUTER
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Work LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Work LAN
Physical Address. . . . . . . . . : 00-1D-7D-07-...
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.50
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
192.168.1.1

Does this help?

"Pegasus (MVP)" wrote:

While I understand your wish to remain anonymous, you overdid it a little
by
concealing most of your IP addresses. Please try to be a little less
secretive, perhaps my modifying your addresses just a little. Example:
Instead of saying
IP Address 208.67.220.10 you might say
IP Address 209.68.221.10

If you modify all subnet addresses (the first three packets) in the same
way
then you're not giving away your real address but you're providing enough
information for respondents to draw some conclusions.

"adandy" wrote in message
...
The interbutts is working just fine outbound, im posting this from the
machine but here it is anyhow


Windows IP Configuration

Host Name . . . . . . . . . . . . : myhostname
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Work LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NIC name
Physical Address. . . . . . . . . : 00-1D-7D-07-
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : my IP address
Subnet Mask . . . . . . . . . . . : 255.255.255.
Default Gateway . . . . . . . . . : my gateway address
DNS Servers . . . . . . . . . . . : 208.67.222.2
208.67.220.2
my gateway address
another dns
yet another dns

"Pegasus (MVP)" wrote:


"adandy" wrote in message
...
I recently noticed that remote desktop no longer works on a machine
of
mine.
I had not changed the configuration. All machines on the lan operate
fine
with the exception of this one. The ports are listening:

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

but I cannot telnet to them or ping the machine any longer. Where
should I
being troubleshooting?

You should look and/or report the output from this command:

ipconfig /all

Here is what I would do, in this order:
1. Connect some Windows PC to the internal network. Let's call it
"TestPC" and let's give it an IP address of 192.168.1.99.
2. Make sure that TestPC can ping 192.168.1.50.
3. Type this command from a Command Prompt on TestPC:
telnet 192.168.1.50 3389
4. If you have a problem with Steps 2 or 3, perform the tests
in the reverse direction, i.e. like so:
5. Open a Command Prompt on 192.168.1.50.
6. Make sure that it can ping 192.168.1.99.
7. Type this command from a Command Prompt on the problem PC:
telnet 192.168.1.99 3389

"adandy" wrote in message
...
1. The machine I am trouble shooting is the host.
2. The other machines on the lan are running linux and OS X and all
operate
fine. The other windows machine was outside the lan and was experiencing
the
same as the internal machines, not being able to communicate with the
services any longer. Inside the lan or out through the firewall. The only
thing between the machines on the lan is a switch and its switching
everything fine, and the plugs have been moved. I'm 100% sure its on the
host
machine.
3. Some of them, it doesent work at the lan level so I would like to get
that to work first, I can take care of it from that point.
4. Only from localhost
5. firewall has been off, is off on the host machine

thanks for the help

"Pegasus (MVP)" wrote:

OK, these adresses are fine. Since they are stock-standard internal
addresses, there is no need to hide them from anyone. There are millions
of
machines that have addresses in the subnet 192.168.1. Now let's dig a
little
deeper:
1. Is the machine with the address 192.168.1.50 the host or the remote
for
your RDP session?
2. What is the output of ipconfig /all for the other machine?
3. Are the two machines connected to the same internal network?
4. Did ping or remote desktop ever work?
5. Have you tried turning off your firewall while testing?

Your answers will probably generate another set of questions.


"adandy" wrote in message
...
Windows IP Configuration

Host Name . . . . . . . . . . . . : COMPUTER
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Work LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Work LAN
Physical Address. . . . . . . . . : 00-1D-7D-07-...
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.50
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
192.168.1.1

Does this help?

"Pegasus (MVP)" wrote:

While I understand your wish to remain anonymous, you overdid it a
little
by
concealing most of your IP addresses. Please try to be a little less
secretive, perhaps my modifying your addresses just a little. Example:
Instead of saying
IP Address 208.67.220.10 you might say
IP Address 209.68.221.10

If you modify all subnet addresses (the first three packets) in the
same
way
then you're not giving away your real address but you're providing
enough
information for respondents to draw some conclusions.

"adandy" wrote in message
...
The interbutts is working just fine outbound, im posting this from
the
machine but here it is anyhow


Windows IP Configuration

Host Name . . . . . . . . . . . . : myhostname
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Work LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NIC name
Physical Address. . . . . . . . . : 00-1D-7D-07-
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : my IP address
Subnet Mask . . . . . . . . . . . : 255.255.255.
Default Gateway . . . . . . . . . : my gateway address
DNS Servers . . . . . . . . . . . : 208.67.222.2
208.67.220.2
my gateway address
another dns
yet another dns

"Pegasus (MVP)" wrote:


"adandy" wrote in message
...
I recently noticed that remote desktop no longer works on a
machine
of
mine.
I had not changed the configuration. All machines on the lan
operate
fine
with the exception of this one. The ports are listening:

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

but I cannot telnet to them or ping the machine any longer. Where
should I
being troubleshooting?

You should look and/or report the output from this command:

ipconfig /all