Remote Desktop/Networking

  • Thread starter Thread starter David L.
  • Start date Start date
D

David L.

Guest
Hello All,

Any help I can get with this issue is going to be very much appreciated.
I've been stumping myself at this for around 2 weeks now.

I have two computers on my network, one desktop and one tablet. Both are
running XP Pro and both can connect to the Internet.

The final solution I'm trying to arrive at is to have the tablet pc Remote
Desktop connect to the desktop pc. I've followed all of the steps to setting
up Remote Desktop so I think that aspect is configured correctly. Yet when I
try to search the workgroup, I get that "There is no terminal service
running". Alternatively, when I try to connect to the IP address directly, I
get that the computer is unavailable and maynot be accepting new users (or
something to that nature).

Another problem that occurs, which to me implies that the issue is a
networking one. Is that I can't ping the desktop from the tablet. I CAN ping
the tablet from the desktop though and both can ping themselves.

I'm lost. Please help.

Best,
DL
 
"David L." <David L.@discussions.microsoft.com> wrote in message
news:41C9895E-7BBD-439A-841A-D565E2272C53@microsoft.com...
> Hello All,
>
> Any help I can get with this issue is going to be very much appreciated.
> I've been stumping myself at this for around 2 weeks now.
>
> I have two computers on my network, one desktop and one tablet. Both are
> running XP Pro and both can connect to the Internet.
>
> The final solution I'm trying to arrive at is to have the tablet pc Remote
> Desktop connect to the desktop pc. I've followed all of the steps to
> setting
> up Remote Desktop so I think that aspect is configured correctly. Yet when
> I
> try to search the workgroup, I get that "There is no terminal service
> running". Alternatively, when I try to connect to the IP address directly,
> I
> get that the computer is unavailable and maynot be accepting new users (or
> something to that nature).
>
> Another problem that occurs, which to me implies that the issue is a
> networking one. Is that I can't ping the desktop from the tablet. I CAN
> ping
> the tablet from the desktop though and both can ping themselves.
>
> I'm lost. Please help.
>
> Best,
> DL


Turn off the Windows firewall during testing until you get your
ping problem resolved. Make sure to disconnect your network
from the Internet while the firewall is turned off.

Click Start / Help, then look for help on "Remote Desktop" to
see how to enable this facility.

Post again if you need more help.
 
The ping problem remains even with both firewalls turned off.

I've also gone through all of the all articles that I could find about
remote desktop. I don't know if I'm correct but I think once the ping problem
is resolved the remote desktop should work.


"Pegasus (MVP)" wrote:

>
> "David L." <David L.@discussions.microsoft.com> wrote in message
> news:41C9895E-7BBD-439A-841A-D565E2272C53@microsoft.com...
> > Hello All,
> >
> > Any help I can get with this issue is going to be very much appreciated.
> > I've been stumping myself at this for around 2 weeks now.
> >
> > I have two computers on my network, one desktop and one tablet. Both are
> > running XP Pro and both can connect to the Internet.
> >
> > The final solution I'm trying to arrive at is to have the tablet pc Remote
> > Desktop connect to the desktop pc. I've followed all of the steps to
> > setting
> > up Remote Desktop so I think that aspect is configured correctly. Yet when
> > I
> > try to search the workgroup, I get that "There is no terminal service
> > running". Alternatively, when I try to connect to the IP address directly,
> > I
> > get that the computer is unavailable and maynot be accepting new users (or
> > something to that nature).
> >
> > Another problem that occurs, which to me implies that the issue is a
> > networking one. Is that I can't ping the desktop from the tablet. I CAN
> > ping
> > the tablet from the desktop though and both can ping themselves.
> >
> > I'm lost. Please help.
> >
> > Best,
> > DL

>
> Turn off the Windows firewall during testing until you get your
> ping problem resolved. Make sure to disconnect your network
> from the Internet while the firewall is turned off.
>
> Click Start / Help, then look for help on "Remote Desktop" to
> see how to enable this facility.
>
> Post again if you need more help.
>
>
>
 
A couple of suggestions:
- If you have ZoneAlarm installed then you must uninstall it. This
utility is known for blocking network traffic, even while disabled.
- You should post your full IP address details. Do this on each PC:
* Click Start / Run / cmd {OK}
* Type these commands:
ipconfig /all > c:\test.txt
ping 64.233.183.104 >> c:\test.txt
notepad c:\test.txt
- Post the contents of both files.


"David L." <DavidL@discussions.microsoft.com> wrote in message
news:D707117E-BD02-4FF9-AA92-B6D8A911A0E4@microsoft.com...
> The ping problem remains even with both firewalls turned off.
>
> I've also gone through all of the all articles that I could find about
> remote desktop. I don't know if I'm correct but I think once the ping
> problem
> is resolved the remote desktop should work.
>
>
> "Pegasus (MVP)" wrote:
>
>>
>> "David L." <David L.@discussions.microsoft.com> wrote in message
>> news:41C9895E-7BBD-439A-841A-D565E2272C53@microsoft.com...
>> > Hello All,
>> >
>> > Any help I can get with this issue is going to be very much
>> > appreciated.
>> > I've been stumping myself at this for around 2 weeks now.
>> >
>> > I have two computers on my network, one desktop and one tablet. Both
>> > are
>> > running XP Pro and both can connect to the Internet.
>> >
>> > The final solution I'm trying to arrive at is to have the tablet pc
>> > Remote
>> > Desktop connect to the desktop pc. I've followed all of the steps to
>> > setting
>> > up Remote Desktop so I think that aspect is configured correctly. Yet
>> > when
>> > I
>> > try to search the workgroup, I get that "There is no terminal service
>> > running". Alternatively, when I try to connect to the IP address
>> > directly,
>> > I
>> > get that the computer is unavailable and maynot be accepting new users
>> > (or
>> > something to that nature).
>> >
>> > Another problem that occurs, which to me implies that the issue is a
>> > networking one. Is that I can't ping the desktop from the tablet. I CAN
>> > ping
>> > the tablet from the desktop though and both can ping themselves.
>> >
>> > I'm lost. Please help.
>> >
>> > Best,
>> > DL

>>
>> Turn off the Windows firewall during testing until you get your
>> ping problem resolved. Make sure to disconnect your network
>> from the Internet while the firewall is turned off.
>>
>> Click Start / Help, then look for help on "Remote Desktop" to
>> see how to enable this facility.
>>
>> Post again if you need more help.
>>
>>
>>
 
I do not have Zone Alarm, I'm only using the windows firewall software as of
now.

Here are the IP address details for both comps...

*************************************
1st Computer Below (Desired Host)
*************************************

Windows IP Configuration
Host Name . . . . . . . . . . . . : Office
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter Wireless Network Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys Wireless-G PCI Adapter
Physical Address. . . . . . . . . : 00-18-39-14-D6-0A
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 72.45.32.34
72.45.32.37

*************************************
2nd Computer Below (Desired Client)
*************************************
Windows IP Configuration
Host Name . . . . . . . . . . . . : LivingRoom
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : the-beach.net

Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . : the-beach.net
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-0C-6F-00-0B-3D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.107
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 72.45.32.34
72.45.32.37
Lease Obtained. . . . . . . . . . : Friday, October 20, 2006 7:21:20
AM
Lease Expires . . . . . . . . . . : Saturday, October 21, 2006
7:21:20 AM



"Pegasus (MVP)" wrote:

> A couple of suggestions:
> - If you have ZoneAlarm installed then you must uninstall it. This
> utility is known for blocking network traffic, even while disabled.
> - You should post your full IP address details. Do this on each PC:
> * Click Start / Run / cmd {OK}
> * Type these commands:
> ipconfig /all > c:\test.txt
> ping 64.233.183.104 >> c:\test.txt
> notepad c:\test.txt
> - Post the contents of both files.
>
>
> "David L." <DavidL@discussions.microsoft.com> wrote in message
> news:D707117E-BD02-4FF9-AA92-B6D8A911A0E4@microsoft.com...
> > The ping problem remains even with both firewalls turned off.
> >
> > I've also gone through all of the all articles that I could find about
> > remote desktop. I don't know if I'm correct but I think once the ping
> > problem
> > is resolved the remote desktop should work.
> >
> >
> > "Pegasus (MVP)" wrote:
> >
> >>
> >> "David L." <David L.@discussions.microsoft.com> wrote in message
> >> news:41C9895E-7BBD-439A-841A-D565E2272C53@microsoft.com...
> >> > Hello All,
> >> >
> >> > Any help I can get with this issue is going to be very much
> >> > appreciated.
> >> > I've been stumping myself at this for around 2 weeks now.
> >> >
> >> > I have two computers on my network, one desktop and one tablet. Both
> >> > are
> >> > running XP Pro and both can connect to the Internet.
> >> >
> >> > The final solution I'm trying to arrive at is to have the tablet pc
> >> > Remote
> >> > Desktop connect to the desktop pc. I've followed all of the steps to
> >> > setting
> >> > up Remote Desktop so I think that aspect is configured correctly. Yet
> >> > when
> >> > I
> >> > try to search the workgroup, I get that "There is no terminal service
> >> > running". Alternatively, when I try to connect to the IP address
> >> > directly,
> >> > I
> >> > get that the computer is unavailable and maynot be accepting new users
> >> > (or
> >> > something to that nature).
> >> >
> >> > Another problem that occurs, which to me implies that the issue is a
> >> > networking one. Is that I can't ping the desktop from the tablet. I CAN
> >> > ping
> >> > the tablet from the desktop though and both can ping themselves.
> >> >
> >> > I'm lost. Please help.
> >> >
> >> > Best,
> >> > DL
> >>
> >> Turn off the Windows firewall during testing until you get your
> >> ping problem resolved. Make sure to disconnect your network
> >> from the Internet while the firewall is turned off.
> >>
> >> Click Start / Help, then look for help on "Remote Desktop" to
> >> see how to enable this facility.
> >>
> >> Post again if you need more help.
> >>
> >>
> >>

>
>
>
 
David L. wrote:
> I do not have Zone Alarm, I'm only using the windows firewall
> software as of now.
>
> Here are the IP address details for both comps...
>> Lease Obtained. . . . . . . . . . : Friday, October 20, 2006

> 7:21:20 AM
> Lease Expires . . . . . . . . . . : Saturday, October 21, 2006
> 7:21:20 AM
>


Uh, it's November here. Maybe you haven't reset stuff from Daylight Savings
Time?
 
It does not make much sense having one machine on DHCP
and the other on a fixed IP address. I suggest you turn off
DHCP on both machines and assign the following addresses:

Office 192.168.1.20
LivingRoom 192.168.1.21

I recommand that you set the DSN addreses like so
on both machines:
Primary 192.168.1.1
Others 72.45.32.34, 72.45.32.37

After doing this, execute the following commands on Office
and post the result file:
ping 192.168.1.21 > c:\test.txt
ping LivingRoom >> c:\test.txt
ping 64.233.183.104 >> c:\test.txt
netstat -an | find "3389" >> test.txt
Please do not omit the third command this time!

On LivingRoom I would like you to run these commands:
ping 192.168.1.20 > c:\test.txt
ping Office >> c:\test.txt
ping 64.233.183.104 >> c:\test.txt
telnet 192.168.1.20 3389 >> 1c:\test.txt 2>>&1

Lastly I would like you to report the port number at this registry
location on Office:
HKLM\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber


"David L." <DavidL@discussions.microsoft.com> wrote in message
news:840E2823-C8EF-407F-B194-831C8D9326C3@microsoft.com...
>I do not have Zone Alarm, I'm only using the windows firewall software as
>of
> now.
>
> Here are the IP address details for both comps...
>
> *************************************
> 1st Computer Below (Desired Host)
> *************************************
>
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : Office
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : Yes
>
> Ethernet adapter Wireless Network Connection 2:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Linksys Wireless-G PCI Adapter
> Physical Address. . . . . . . . . : 00-18-39-14-D6-0A
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.20
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 72.45.32.34
> 72.45.32.37
>
> *************************************
> 2nd Computer Below (Desired Client)
> *************************************
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : LivingRoom
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : the-beach.net
>
> Ethernet adapter Local Area Connection 2:
> Connection-specific DNS Suffix . : the-beach.net
> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
> Ethernet NIC
> Physical Address. . . . . . . . . : 00-0C-6F-00-0B-3D
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.1.107
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 72.45.32.34
> 72.45.32.37
> Lease Obtained. . . . . . . . . . : Friday, October 20, 2006
> 7:21:20
> AM
> Lease Expires . . . . . . . . . . : Saturday, October 21, 2006
> 7:21:20 AM
>
>
>
> "Pegasus (MVP)" wrote:
>
>> A couple of suggestions:
>> - If you have ZoneAlarm installed then you must uninstall it. This
>> utility is known for blocking network traffic, even while disabled.
>> - You should post your full IP address details. Do this on each PC:
>> * Click Start / Run / cmd {OK}
>> * Type these commands:
>> ipconfig /all > c:\test.txt
>> ping 64.233.183.104 >> c:\test.txt
>> notepad c:\test.txt
>> - Post the contents of both files.
>>
>>
>> "David L." <DavidL@discussions.microsoft.com> wrote in message
>> news:D707117E-BD02-4FF9-AA92-B6D8A911A0E4@microsoft.com...
>> > The ping problem remains even with both firewalls turned off.
>> >
>> > I've also gone through all of the all articles that I could find about
>> > remote desktop. I don't know if I'm correct but I think once the ping
>> > problem
>> > is resolved the remote desktop should work.
>> >
>> >
>> > "Pegasus (MVP)" wrote:
>> >
>> >>
>> >> "David L." <David L.@discussions.microsoft.com> wrote in message
>> >> news:41C9895E-7BBD-439A-841A-D565E2272C53@microsoft.com...
>> >> > Hello All,
>> >> >
>> >> > Any help I can get with this issue is going to be very much
>> >> > appreciated.
>> >> > I've been stumping myself at this for around 2 weeks now.
>> >> >
>> >> > I have two computers on my network, one desktop and one tablet. Both
>> >> > are
>> >> > running XP Pro and both can connect to the Internet.
>> >> >
>> >> > The final solution I'm trying to arrive at is to have the tablet pc
>> >> > Remote
>> >> > Desktop connect to the desktop pc. I've followed all of the steps to
>> >> > setting
>> >> > up Remote Desktop so I think that aspect is configured correctly.
>> >> > Yet
>> >> > when
>> >> > I
>> >> > try to search the workgroup, I get that "There is no terminal
>> >> > service
>> >> > running". Alternatively, when I try to connect to the IP address
>> >> > directly,
>> >> > I
>> >> > get that the computer is unavailable and maynot be accepting new
>> >> > users
>> >> > (or
>> >> > something to that nature).
>> >> >
>> >> > Another problem that occurs, which to me implies that the issue is a
>> >> > networking one. Is that I can't ping the desktop from the tablet. I
>> >> > CAN
>> >> > ping
>> >> > the tablet from the desktop though and both can ping themselves.
>> >> >
>> >> > I'm lost. Please help.
>> >> >
>> >> > Best,
>> >> > DL
>> >>
>> >> Turn off the Windows firewall during testing until you get your
>> >> ping problem resolved. Make sure to disconnect your network
>> >> from the Internet while the firewall is turned off.
>> >>
>> >> Click Start / Help, then look for help on "Remote Desktop" to
>> >> see how to enable this facility.
>> >>
>> >> Post again if you need more help.
>> >>
>> >>
>> >>

>>
>>
>>
 
On Dec 2, 7:16 pm, David L. <Dav...@discussions.microsoft.com> wrote:
> I do not have Zone Alarm, I'm only using the windows firewall software as of
> now.
>
> Here are the IP address details for both comps...
>
> *************************************
> 1st Computer Below (Desired Host)
> *************************************
>
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : Office
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : Yes
>
> Ethernet adapter Wireless Network Connection 2:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Linksys Wireless-G PCI Adapter
> Physical Address. . . . . . . . . : 00-18-39-14-D6-0A
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.20
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 72.45.32.34
> 72.45.32.37
>
> *************************************
> 2nd Computer Below (Desired Client)
> *************************************
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : LivingRoom
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : the-beach.net
>
> Ethernet adapter Local Area Connection 2:
> Connection-specific DNS Suffix . : the-beach.net
> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
> Ethernet NIC
> Physical Address. . . . . . . . . : 00-0C-6F-00-0B-3D
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.1.107
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 72.45.32.34
> 72.45.32.37
> Lease Obtained. . . . . . . . . . : Friday, October 20, 2006 7:21:20
> AM
> Lease Expires . . . . . . . . . . : Saturday, October 21, 2006
> 7:21:20 AM
>
>
>
> "Pegasus (MVP)" wrote:
> > A couple of suggestions:
> > - If you have ZoneAlarm installed then you must uninstall it. This
> > utility is known for blocking network traffic, even while disabled.
> > - You should post your full IP address details. Do this on each PC:
> > * Click Start / Run / cmd {OK}
> > * Type these commands:
> > ipconfig /all > c:\test.txt
> > ping 64.233.183.104 >> c:\test.txt
> > notepad c:\test.txt
> > - Post the contents of both files.

>
> > "David L." <Dav...@discussions.microsoft.com> wrote in message
> >news:D707117E-BD02-4FF9-AA92-B6D8A911A0E4@microsoft.com...
> > > The ping problem remains even with both firewalls turned off.

>
> > > I've also gone through all of the all articles that I could find about
> > > remote desktop. I don't know if I'm correct but I think once the ping
> > > problem
> > > is resolved the remote desktop should work.

>
> > > "Pegasus (MVP)" wrote:

>
> > >> "David L." <David L...@discussions.microsoft.com> wrote in message
> > >>news:41C9895E-7BBD-439A-841A-D565E2272C53@microsoft.com...
> > >> > Hello All,

>
> > >> > Any help I can get with this issue is going to be very much
> > >> > appreciated.
> > >> > I've been stumping myself at this for around 2 weeks now.

>
> > >> > I have two computers on my network, one desktop and one tablet. Both
> > >> > are
> > >> > running XP Pro and both can connect to the Internet.

>
> > >> > The final solution I'm trying to arrive at is to have the tablet pc
> > >> > Remote
> > >> > Desktop connect to the desktop pc. I've followed all of the steps to
> > >> > setting
> > >> > up Remote Desktop so I think that aspect is configured correctly. Yet
> > >> > when
> > >> > I
> > >> > try to search the workgroup, I get that "There is no terminal service
> > >> > running". Alternatively, when I try to connect to the IP address
> > >> > directly,
> > >> > I
> > >> > get that the computer is unavailable and maynot be accepting new users
> > >> > (or
> > >> > something to that nature).

>
> > >> > Another problem that occurs, which to me implies that the issue is a
> > >> > networking one. Is that I can't ping the desktop from the tablet. I CAN
> > >> > ping
> > >> > the tablet from the desktop though and both can ping themselves.

>
> > >> > I'm lost. Please help.

>
> > >> > Best,
> > >> > DL

>
> > >> Turn off the Windows firewall during testing until you get your
> > >> ping problem resolved. Make sure to disconnect your network
> > >> from the Internet while the firewall is turned off.

>
> > >> Click Start / Help, then look for help on "Remote Desktop" to
> > >> see how to enable this facility.

>
> > >> Post again if you need more help.- Hide quoted text -

>
> - Show quoted text -


You should also know that several anti-virus software (like Norton and
McAfee) have modules that "behave" excatly like firewall software.

Remote Desktop needs to be turned on (Pro's install does not turn this
on.)

Remote Desktop does not "like" to use a user account that does not
have a "pasword." You can find a "group policy" to enable the "no
password" account access.
 
Sorry for the delay. work sent me on a day trip around the world (or at least
close to it). It sucked. Anyway... thanks for the help and here is the data
you requested. Also, regarding the other person that mentioned about the
username and passwords, LivingRoom does not have a password - should it?

*******************************
Office Data Below
*******************************
Pinging 192.168.1.21 with 32 bytes of data:
Reply from 192.168.1.21: bytes=32 time=5ms TTL=128
Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
Reply from 192.168.1.21: bytes=32 time=1261ms TTL=128
Reply from 192.168.1.21: bytes=32 time=2ms TTL=128

Ping statistics for 192.168.1.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 1261ms, Average = 317ms

Pinging LivingRoom [192.168.1.21] with 32 bytes of data:
Reply from 192.168.1.21: bytes=32 time=1ms TTL=128
Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
Reply from 192.168.1.21: bytes=32 time=2ms TTL=128

Ping statistics for 192.168.1.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

Pinging 64.233.183.104 with 32 bytes of data:
Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
Reply from 64.233.183.104: bytes=32 time=137ms TTL=231
Reply from 64.233.183.104: bytes=32 time=132ms TTL=231

Ping statistics for 64.233.183.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 132ms, Maximum = 137ms, Average = 133ms
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
Port# in ..\RDP-Tcp\PortNumber = 3389


*******************************
LivingRoom Data Below
*******************************
Pinging 192.168.1.20 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.20:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Ping request could not find host Office. Please check the name and try again.

Pinging 64.233.183.104 with 32 bytes of data:
Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
Reply from 64.233.183.104: bytes=32 time=148ms TTL=231
Reply from 64.233.183.104: bytes=32 time=138ms TTL=231

Ping statistics for 64.233.183.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 134ms, Maximum = 148ms, Average = 138ms

\\When I ran the next telnet command as you gave it to me I kept getting a
syntax error. So I ran it as below and typed in the results (instead of
having them write to the test.txt file), is was://
\\Command:telnet 192.168.1.20 3389
Connecting to 192.168.1.20...Could not open connection to the host, on port
3389: Connect failed.

"Pegasus (MVP)" wrote:

> It does not make much sense having one machine on DHCP
> and the other on a fixed IP address. I suggest you turn off
> DHCP on both machines and assign the following addresses:
>
> Office 192.168.1.20
> LivingRoom 192.168.1.21
>
> I recommand that you set the DSN addreses like so
> on both machines:
> Primary 192.168.1.1
> Others 72.45.32.34, 72.45.32.37
>
> After doing this, execute the following commands on Office
> and post the result file:
> ping 192.168.1.21 > c:\test.txt
> ping LivingRoom >> c:\test.txt
> ping 64.233.183.104 >> c:\test.txt
> netstat -an | find "3389" >> test.txt
> Please do not omit the third command this time!
>
> On LivingRoom I would like you to run these commands:
> ping 192.168.1.20 > c:\test.txt
> ping Office >> c:\test.txt
> ping 64.233.183.104 >> c:\test.txt
> telnet 192.168.1.20 3389 >> 1c:\test.txt 2>>&1
>
> Lastly I would like you to report the port number at this registry
> location on Office:
> HKLM\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber
>
>
> "David L." <DavidL@discussions.microsoft.com> wrote in message
> news:840E2823-C8EF-407F-B194-831C8D9326C3@microsoft.com...
> >I do not have Zone Alarm, I'm only using the windows firewall software as
> >of
> > now.
> >
> > Here are the IP address details for both comps...
> >
> > *************************************
> > 1st Computer Below (Desired Host)
> > *************************************
> >
> > Windows IP Configuration
> > Host Name . . . . . . . . . . . . : Office
> > Primary Dns Suffix . . . . . . . :
> > Node Type . . . . . . . . . . . . : Unknown
> > IP Routing Enabled. . . . . . . . : Yes
> > WINS Proxy Enabled. . . . . . . . : Yes
> >
> > Ethernet adapter Wireless Network Connection 2:
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Linksys Wireless-G PCI Adapter
> > Physical Address. . . . . . . . . : 00-18-39-14-D6-0A
> > Dhcp Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.1.20
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.1.1
> > DNS Servers . . . . . . . . . . . : 72.45.32.34
> > 72.45.32.37
> >
> > *************************************
> > 2nd Computer Below (Desired Client)
> > *************************************
> > Windows IP Configuration
> > Host Name . . . . . . . . . . . . : LivingRoom
> > Primary Dns Suffix . . . . . . . :
> > Node Type . . . . . . . . . . . . : Unknown
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : the-beach.net
> >
> > Ethernet adapter Local Area Connection 2:
> > Connection-specific DNS Suffix . : the-beach.net
> > Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
> > Ethernet NIC
> > Physical Address. . . . . . . . . : 00-0C-6F-00-0B-3D
> > Dhcp Enabled. . . . . . . . . . . : Yes
> > Autoconfiguration Enabled . . . . : Yes
> > IP Address. . . . . . . . . . . . : 192.168.1.107
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.1.1
> > DHCP Server . . . . . . . . . . . : 192.168.1.1
> > DNS Servers . . . . . . . . . . . : 72.45.32.34
> > 72.45.32.37
> > Lease Obtained. . . . . . . . . . : Friday, October 20, 2006
> > 7:21:20
> > AM
> > Lease Expires . . . . . . . . . . : Saturday, October 21, 2006
> > 7:21:20 AM
> >
> >
> >
> > "Pegasus (MVP)" wrote:
> >
> >> A couple of suggestions:
> >> - If you have ZoneAlarm installed then you must uninstall it. This
> >> utility is known for blocking network traffic, even while disabled.
> >> - You should post your full IP address details. Do this on each PC:
> >> * Click Start / Run / cmd {OK}
> >> * Type these commands:
> >> ipconfig /all > c:\test.txt
> >> ping 64.233.183.104 >> c:\test.txt
> >> notepad c:\test.txt
> >> - Post the contents of both files.
> >>
> >>
> >> "David L." <DavidL@discussions.microsoft.com> wrote in message
> >> news:D707117E-BD02-4FF9-AA92-B6D8A911A0E4@microsoft.com...
> >> > The ping problem remains even with both firewalls turned off.
> >> >
> >> > I've also gone through all of the all articles that I could find about
> >> > remote desktop. I don't know if I'm correct but I think once the ping
> >> > problem
> >> > is resolved the remote desktop should work.
> >> >
> >> >
> >> > "Pegasus (MVP)" wrote:
> >> >
> >> >>
> >> >> "David L." <David L.@discussions.microsoft.com> wrote in message
> >> >> news:41C9895E-7BBD-439A-841A-D565E2272C53@microsoft.com...
> >> >> > Hello All,
> >> >> >
> >> >> > Any help I can get with this issue is going to be very much
> >> >> > appreciated.
> >> >> > I've been stumping myself at this for around 2 weeks now.
> >> >> >
> >> >> > I have two computers on my network, one desktop and one tablet. Both
> >> >> > are
> >> >> > running XP Pro and both can connect to the Internet.
> >> >> >
> >> >> > The final solution I'm trying to arrive at is to have the tablet pc
> >> >> > Remote
> >> >> > Desktop connect to the desktop pc. I've followed all of the steps to
> >> >> > setting
> >> >> > up Remote Desktop so I think that aspect is configured correctly.
> >> >> > Yet
> >> >> > when
> >> >> > I
> >> >> > try to search the workgroup, I get that "There is no terminal
> >> >> > service
> >> >> > running". Alternatively, when I try to connect to the IP address
> >> >> > directly,
> >> >> > I
> >> >> > get that the computer is unavailable and maynot be accepting new
> >> >> > users
> >> >> > (or
> >> >> > something to that nature).
> >> >> >
> >> >> > Another problem that occurs, which to me implies that the issue is a
> >> >> > networking one. Is that I can't ping the desktop from the tablet. I
> >> >> > CAN
> >> >> > ping
> >> >> > the tablet from the desktop though and both can ping themselves.
> >> >> >
> >> >> > I'm lost. Please help.
> >> >> >
> >> >> > Best,
> >> >> > DL
> >> >>
> >> >> Turn off the Windows firewall during testing until you get your
> >> >> ping problem resolved. Make sure to disconnect your network
> >> >> from the Internet while the firewall is turned off.
> >> >>
> >> >> Click Start / Help, then look for help on "Remote Desktop" to
> >> >> see how to enable this facility.
> >> >>
> >> >> Post again if you need more help.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>

>
>
>
 
Sorry for the mistake in the telnet command. It seems you
compensated for it quite nicely.

Yes, respondent "smlunatick" is correct: When using
Remote Desktop then you must use an account on that
host machine that has a non-blank passwords. However,
you're not at that stage just yet.

Your tests prove these points:
- Your network appears to be working. Both machines
can set test packets to an external site.
- The Office machine can exchange test packets with the
LivingRoom machine.
- The LivingRoom machine cannot exchange test packets
with the Office machine.

I can think of these reasons why this would happen. I'm
ignoring here what you wrote in your previous notes:
a) The Windows firewall on Office is active.
b) There is a third-party firewall active or installed on Office.
c) The IP address of Office is something other than 192.168.1.20.
d) The network adapter of Office is flawed (unlikely but possible).
e) The network switch port used by the Office machine is
flawed (unlikely but possible).
f) The network switch (or router) is in a funny mode. Rebooting
it would probably fix it.

Why not try it in reverse? Enable Remote Desktop on Living
Room, then type this command on Office: mstsc /v:LivingRoom


"David L." <DavidL@discussions.microsoft.com> wrote in message
news:A0803A17-0E7C-4F81-B690-9AEA11B15949@microsoft.com...
> Sorry for the delay. work sent me on a day trip around the world (or at
> least
> close to it). It sucked. Anyway... thanks for the help and here is the
> data
> you requested. Also, regarding the other person that mentioned about the
> username and passwords, LivingRoom does not have a password - should it?
>
> *******************************
> Office Data Below
> *******************************
> Pinging 192.168.1.21 with 32 bytes of data:
> Reply from 192.168.1.21: bytes=32 time=5ms TTL=128
> Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> Reply from 192.168.1.21: bytes=32 time=1261ms TTL=128
> Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
>
> Ping statistics for 192.168.1.21:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 2ms, Maximum = 1261ms, Average = 317ms
>
> Pinging LivingRoom [192.168.1.21] with 32 bytes of data:
> Reply from 192.168.1.21: bytes=32 time=1ms TTL=128
> Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
>
> Ping statistics for 192.168.1.21:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 1ms, Maximum = 2ms, Average = 1ms
>
> Pinging 64.233.183.104 with 32 bytes of data:
> Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
> Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
> Reply from 64.233.183.104: bytes=32 time=137ms TTL=231
> Reply from 64.233.183.104: bytes=32 time=132ms TTL=231
>
> Ping statistics for 64.233.183.104:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 132ms, Maximum = 137ms, Average = 133ms
> TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
> Port# in ..\RDP-Tcp\PortNumber = 3389
>
>
> *******************************
> LivingRoom Data Below
> *******************************
> Pinging 192.168.1.20 with 32 bytes of data:
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
>
> Ping statistics for 192.168.1.20:
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> Ping request could not find host Office. Please check the name and try
> again.
>
> Pinging 64.233.183.104 with 32 bytes of data:
> Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
> Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
> Reply from 64.233.183.104: bytes=32 time=148ms TTL=231
> Reply from 64.233.183.104: bytes=32 time=138ms TTL=231
>
> Ping statistics for 64.233.183.104:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 134ms, Maximum = 148ms, Average = 138ms
>
> \\When I ran the next telnet command as you gave it to me I kept getting a
> syntax error. So I ran it as below and typed in the results (instead of
> having them write to the test.txt file), is was://
> \\Command:telnet 192.168.1.20 3389
> Connecting to 192.168.1.20...Could not open connection to the host, on
> port
> 3389: Connect failed.
>
> "Pegasus (MVP)" wrote:
>
>> It does not make much sense having one machine on DHCP
>> and the other on a fixed IP address. I suggest you turn off
>> DHCP on both machines and assign the following addresses:
>>
>> Office 192.168.1.20
>> LivingRoom 192.168.1.21
>>
>> I recommand that you set the DSN addreses like so
>> on both machines:
>> Primary 192.168.1.1
>> Others 72.45.32.34, 72.45.32.37
>>
>> After doing this, execute the following commands on Office
>> and post the result file:
>> ping 192.168.1.21 > c:\test.txt
>> ping LivingRoom >> c:\test.txt
>> ping 64.233.183.104 >> c:\test.txt
>> netstat -an | find "3389" >> test.txt
>> Please do not omit the third command this time!
>>
>> On LivingRoom I would like you to run these commands:
>> ping 192.168.1.20 > c:\test.txt
>> ping Office >> c:\test.txt
>> ping 64.233.183.104 >> c:\test.txt
>> telnet 192.168.1.20 3389 >> 1c:\test.txt 2>>&1
>>
>> Lastly I would like you to report the port number at this registry
>> location on Office:
>> HKLM\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber
>>
>>
>> "David L." <DavidL@discussions.microsoft.com> wrote in message
>> news:840E2823-C8EF-407F-B194-831C8D9326C3@microsoft.com...
>> >I do not have Zone Alarm, I'm only using the windows firewall software
>> >as
>> >of
>> > now.
>> >
>> > Here are the IP address details for both comps...
>> >
>> > *************************************
>> > 1st Computer Below (Desired Host)
>> > *************************************
>> >
>> > Windows IP Configuration
>> > Host Name . . . . . . . . . . . . : Office
>> > Primary Dns Suffix . . . . . . . :
>> > Node Type . . . . . . . . . . . . : Unknown
>> > IP Routing Enabled. . . . . . . . : Yes
>> > WINS Proxy Enabled. . . . . . . . : Yes
>> >
>> > Ethernet adapter Wireless Network Connection 2:
>> > Connection-specific DNS Suffix . :
>> > Description . . . . . . . . . . . : Linksys Wireless-G PCI
>> > Adapter
>> > Physical Address. . . . . . . . . : 00-18-39-14-D6-0A
>> > Dhcp Enabled. . . . . . . . . . . : No
>> > IP Address. . . . . . . . . . . . : 192.168.1.20
>> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> > Default Gateway . . . . . . . . . : 192.168.1.1
>> > DNS Servers . . . . . . . . . . . : 72.45.32.34
>> > 72.45.32.37
>> >
>> > *************************************
>> > 2nd Computer Below (Desired Client)
>> > *************************************
>> > Windows IP Configuration
>> > Host Name . . . . . . . . . . . . : LivingRoom
>> > Primary Dns Suffix . . . . . . . :
>> > Node Type . . . . . . . . . . . . : Unknown
>> > IP Routing Enabled. . . . . . . . : No
>> > WINS Proxy Enabled. . . . . . . . : No
>> > DNS Suffix Search List. . . . . . : the-beach.net
>> >
>> > Ethernet adapter Local Area Connection 2:
>> > Connection-specific DNS Suffix . : the-beach.net
>> > Description . . . . . . . . . . . : Realtek RTL8139 Family PCI
>> > Fast
>> > Ethernet NIC
>> > Physical Address. . . . . . . . . : 00-0C-6F-00-0B-3D
>> > Dhcp Enabled. . . . . . . . . . . : Yes
>> > Autoconfiguration Enabled . . . . : Yes
>> > IP Address. . . . . . . . . . . . : 192.168.1.107
>> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> > Default Gateway . . . . . . . . . : 192.168.1.1
>> > DHCP Server . . . . . . . . . . . : 192.168.1.1
>> > DNS Servers . . . . . . . . . . . : 72.45.32.34
>> > 72.45.32.37
>> > Lease Obtained. . . . . . . . . . : Friday, October 20, 2006
>> > 7:21:20
>> > AM
>> > Lease Expires . . . . . . . . . . : Saturday, October 21, 2006
>> > 7:21:20 AM
>> >
>> >
>> >
>> > "Pegasus (MVP)" wrote:
>> >
>> >> A couple of suggestions:
>> >> - If you have ZoneAlarm installed then you must uninstall it. This
>> >> utility is known for blocking network traffic, even while disabled.
>> >> - You should post your full IP address details. Do this on each PC:
>> >> * Click Start / Run / cmd {OK}
>> >> * Type these commands:
>> >> ipconfig /all > c:\test.txt
>> >> ping 64.233.183.104 >> c:\test.txt
>> >> notepad c:\test.txt
>> >> - Post the contents of both files.
>> >>
>> >>
>> >> "David L." <DavidL@discussions.microsoft.com> wrote in message
>> >> news:D707117E-BD02-4FF9-AA92-B6D8A911A0E4@microsoft.com...
>> >> > The ping problem remains even with both firewalls turned off.
>> >> >
>> >> > I've also gone through all of the all articles that I could find
>> >> > about
>> >> > remote desktop. I don't know if I'm correct but I think once the
>> >> > ping
>> >> > problem
>> >> > is resolved the remote desktop should work.
>> >> >
>> >> >
>> >> > "Pegasus (MVP)" wrote:
>> >> >
>> >> >>
>> >> >> "David L." <David L.@discussions.microsoft.com> wrote in message
>> >> >> news:41C9895E-7BBD-439A-841A-D565E2272C53@microsoft.com...
>> >> >> > Hello All,
>> >> >> >
>> >> >> > Any help I can get with this issue is going to be very much
>> >> >> > appreciated.
>> >> >> > I've been stumping myself at this for around 2 weeks now.
>> >> >> >
>> >> >> > I have two computers on my network, one desktop and one tablet.
>> >> >> > Both
>> >> >> > are
>> >> >> > running XP Pro and both can connect to the Internet.
>> >> >> >
>> >> >> > The final solution I'm trying to arrive at is to have the tablet
>> >> >> > pc
>> >> >> > Remote
>> >> >> > Desktop connect to the desktop pc. I've followed all of the steps
>> >> >> > to
>> >> >> > setting
>> >> >> > up Remote Desktop so I think that aspect is configured correctly.
>> >> >> > Yet
>> >> >> > when
>> >> >> > I
>> >> >> > try to search the workgroup, I get that "There is no terminal
>> >> >> > service
>> >> >> > running". Alternatively, when I try to connect to the IP address
>> >> >> > directly,
>> >> >> > I
>> >> >> > get that the computer is unavailable and maynot be accepting new
>> >> >> > users
>> >> >> > (or
>> >> >> > something to that nature).
>> >> >> >
>> >> >> > Another problem that occurs, which to me implies that the issue
>> >> >> > is a
>> >> >> > networking one. Is that I can't ping the desktop from the tablet.
>> >> >> > I
>> >> >> > CAN
>> >> >> > ping
>> >> >> > the tablet from the desktop though and both can ping themselves.
>> >> >> >
>> >> >> > I'm lost. Please help.
>> >> >> >
>> >> >> > Best,
>> >> >> > DL
>> >> >>
>> >> >> Turn off the Windows firewall during testing until you get your
>> >> >> ping problem resolved. Make sure to disconnect your network
>> >> >> from the Internet while the firewall is turned off.
>> >> >>
>> >> >> Click Start / Help, then look for help on "Remote Desktop" to
>> >> >> see how to enable this facility.
>> >> >>
>> >> >> Post again if you need more help.
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>

>>
>>
>>
 
Ok, So you've raised a very valid point. Here's some more history:

LivingRoom is a tablet pc that a friend was using for work - ie. it got real
cluttered but the machine was completly functional, def the wirelss aspect.
So I reformated it and installed a fresh copy of XP Pro (that's why the time
is off. I haven't cleaned it up yet, it's brand new). Since it's a tablet pc
there were a bunch of funky drivers that it requires (for touch control and
other compact hardware).

After I installed all the dirvers (recommended by the manufacturer, one of
them still seemed not to work) - the wireless adapter. Whenever I try to
configure it with the Realtek software provided w/ the dirver (via the link
below) I get "No Wireless Network Adapter Found". I know it worked prior to
my reinstall of XP but I can't get it to work now. The manufacturer will not
respond to me beyond thier "here try this" link to a .zip file, supposidly
containing all the drivers for this particular issue. It obviously is lacking
one. This is the file they say should have fixed this...

http://www.tabletkiosk.com/support/files/Sahara_SDV-T01/Wireless.zip

In device manager under Network Adapters I have 1339 & Realtek 8139, then
Other Devices has a "?" as well as it's subcategory Network Contorler has a
"?".

I didn't think this was going to be a problem because it was going to be a
stationary computer and I could connect w/ a cat5, however based on your last
response I see it is an issue.

Is there a way to find out exactly which wireless network adapter I have?
There is a folder in that zip file titled "802MR-W". I think that's it but I
do not see a setup.exe for it. I assume that its what is showing up as Other
Devices and therefore has no driver. am I correct?


"Pegasus (MVP)" wrote:

> Sorry for the mistake in the telnet command. It seems you
> compensated for it quite nicely.
>
> Yes, respondent "smlunatick" is correct: When using
> Remote Desktop then you must use an account on that
> host machine that has a non-blank passwords. However,
> you're not at that stage just yet.
>
> Your tests prove these points:
> - Your network appears to be working. Both machines
> can set test packets to an external site.
> - The Office machine can exchange test packets with the
> LivingRoom machine.
> - The LivingRoom machine cannot exchange test packets
> with the Office machine.
>
> I can think of these reasons why this would happen. I'm
> ignoring here what you wrote in your previous notes:
> a) The Windows firewall on Office is active.
> b) There is a third-party firewall active or installed on Office.
> c) The IP address of Office is something other than 192.168.1.20.
> d) The network adapter of Office is flawed (unlikely but possible).
> e) The network switch port used by the Office machine is
> flawed (unlikely but possible).
> f) The network switch (or router) is in a funny mode. Rebooting
> it would probably fix it.
>
> Why not try it in reverse? Enable Remote Desktop on Living
> Room, then type this command on Office: mstsc /v:LivingRoom
>
>
> "David L." <DavidL@discussions.microsoft.com> wrote in message
> news:A0803A17-0E7C-4F81-B690-9AEA11B15949@microsoft.com...
> > Sorry for the delay. work sent me on a day trip around the world (or at
> > least
> > close to it). It sucked. Anyway... thanks for the help and here is the
> > data
> > you requested. Also, regarding the other person that mentioned about the
> > username and passwords, LivingRoom does not have a password - should it?
> >
> > *******************************
> > Office Data Below
> > *******************************
> > Pinging 192.168.1.21 with 32 bytes of data:
> > Reply from 192.168.1.21: bytes=32 time=5ms TTL=128
> > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > Reply from 192.168.1.21: bytes=32 time=1261ms TTL=128
> > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> >
> > Ping statistics for 192.168.1.21:
> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > Approximate round trip times in milli-seconds:
> > Minimum = 2ms, Maximum = 1261ms, Average = 317ms
> >
> > Pinging LivingRoom [192.168.1.21] with 32 bytes of data:
> > Reply from 192.168.1.21: bytes=32 time=1ms TTL=128
> > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> >
> > Ping statistics for 192.168.1.21:
> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > Approximate round trip times in milli-seconds:
> > Minimum = 1ms, Maximum = 2ms, Average = 1ms
> >
> > Pinging 64.233.183.104 with 32 bytes of data:
> > Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
> > Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
> > Reply from 64.233.183.104: bytes=32 time=137ms TTL=231
> > Reply from 64.233.183.104: bytes=32 time=132ms TTL=231
> >
> > Ping statistics for 64.233.183.104:
> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > Approximate round trip times in milli-seconds:
> > Minimum = 132ms, Maximum = 137ms, Average = 133ms
> > TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
> > Port# in ..\RDP-Tcp\PortNumber = 3389
> >
> >
> > *******************************
> > LivingRoom Data Below
> > *******************************
> > Pinging 192.168.1.20 with 32 bytes of data:
> > Request timed out.
> > Request timed out.
> > Request timed out.
> > Request timed out.
> >
> > Ping statistics for 192.168.1.20:
> > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> > Ping request could not find host Office. Please check the name and try
> > again.
> >
> > Pinging 64.233.183.104 with 32 bytes of data:
> > Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
> > Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
> > Reply from 64.233.183.104: bytes=32 time=148ms TTL=231
> > Reply from 64.233.183.104: bytes=32 time=138ms TTL=231
> >
> > Ping statistics for 64.233.183.104:
> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > Approximate round trip times in milli-seconds:
> > Minimum = 134ms, Maximum = 148ms, Average = 138ms
> >
> > \\When I ran the next telnet command as you gave it to me I kept getting a
> > syntax error. So I ran it as below and typed in the results (instead of
> > having them write to the test.txt file), is was://
> > \\Command:telnet 192.168.1.20 3389
> > Connecting to 192.168.1.20...Could not open connection to the host, on
> > port
> > 3389: Connect failed.
> >
> > "Pegasus (MVP)" wrote:
> >
> >> It does not make much sense having one machine on DHCP
> >> and the other on a fixed IP address. I suggest you turn off
> >> DHCP on both machines and assign the following addresses:
> >>
> >> Office 192.168.1.20
> >> LivingRoom 192.168.1.21
> >>
> >> I recommand that you set the DSN addreses like so
> >> on both machines:
> >> Primary 192.168.1.1
> >> Others 72.45.32.34, 72.45.32.37
> >>
> >> After doing this, execute the following commands on Office
> >> and post the result file:
> >> ping 192.168.1.21 > c:\test.txt
> >> ping LivingRoom >> c:\test.txt
> >> ping 64.233.183.104 >> c:\test.txt
> >> netstat -an | find "3389" >> test.txt
> >> Please do not omit the third command this time!
> >>
> >> On LivingRoom I would like you to run these commands:
> >> ping 192.168.1.20 > c:\test.txt
> >> ping Office >> c:\test.txt
> >> ping 64.233.183.104 >> c:\test.txt
> >> telnet 192.168.1.20 3389 >> 1c:\test.txt 2>>&1
> >>
> >> Lastly I would like you to report the port number at this registry
> >> location on Office:
> >> HKLM\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber
> >>
> >>
> >> "David L." <DavidL@discussions.microsoft.com> wrote in message
> >> news:840E2823-C8EF-407F-B194-831C8D9326C3@microsoft.com...
> >> >I do not have Zone Alarm, I'm only using the windows firewall software
> >> >as
> >> >of
> >> > now.
> >> >
> >> > Here are the IP address details for both comps...
> >> >
> >> > *************************************
> >> > 1st Computer Below (Desired Host)
> >> > *************************************
> >> >
> >> > Windows IP Configuration
> >> > Host Name . . . . . . . . . . . . : Office
> >> > Primary Dns Suffix . . . . . . . :
> >> > Node Type . . . . . . . . . . . . : Unknown
> >> > IP Routing Enabled. . . . . . . . : Yes
> >> > WINS Proxy Enabled. . . . . . . . : Yes
> >> >
> >> > Ethernet adapter Wireless Network Connection 2:
> >> > Connection-specific DNS Suffix . :
> >> > Description . . . . . . . . . . . : Linksys Wireless-G PCI
> >> > Adapter
> >> > Physical Address. . . . . . . . . : 00-18-39-14-D6-0A
> >> > Dhcp Enabled. . . . . . . . . . . : No
> >> > IP Address. . . . . . . . . . . . : 192.168.1.20
> >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >> > Default Gateway . . . . . . . . . : 192.168.1.1
> >> > DNS Servers . . . . . . . . . . . : 72.45.32.34
> >> > 72.45.32.37
> >> >
> >> > *************************************
> >> > 2nd Computer Below (Desired Client)
> >> > *************************************
> >> > Windows IP Configuration
> >> > Host Name . . . . . . . . . . . . : LivingRoom
> >> > Primary Dns Suffix . . . . . . . :
> >> > Node Type . . . . . . . . . . . . : Unknown
> >> > IP Routing Enabled. . . . . . . . : No
> >> > WINS Proxy Enabled. . . . . . . . : No
> >> > DNS Suffix Search List. . . . . . : the-beach.net
> >> >
> >> > Ethernet adapter Local Area Connection 2:
> >> > Connection-specific DNS Suffix . : the-beach.net
> >> > Description . . . . . . . . . . . : Realtek RTL8139 Family PCI
> >> > Fast
> >> > Ethernet NIC
> >> > Physical Address. . . . . . . . . : 00-0C-6F-00-0B-3D
> >> > Dhcp Enabled. . . . . . . . . . . : Yes
> >> > Autoconfiguration Enabled . . . . : Yes
> >> > IP Address. . . . . . . . . . . . : 192.168.1.107
> >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >> > Default Gateway . . . . . . . . . : 192.168.1.1
> >> > DHCP Server . . . . . . . . . . . : 192.168.1.1
> >> > DNS Servers . . . . . . . . . . . : 72.45.32.34
> >> > 72.45.32.37
> >> > Lease Obtained. . . . . . . . . . : Friday, October 20, 2006
> >> > 7:21:20
> >> > AM
> >> > Lease Expires . . . . . . . . . . : Saturday, October 21, 2006
> >> > 7:21:20 AM
> >> >
> >> >
> >> >
> >> > "Pegasus (MVP)" wrote:
> >> >
> >> >> A couple of suggestions:
> >> >> - If you have ZoneAlarm installed then you must uninstall it. This
> >> >> utility is known for blocking network traffic, even while disabled.
> >> >> - You should post your full IP address details. Do this on each PC:
> >> >> * Click Start / Run / cmd {OK}
> >> >> * Type these commands:
> >> >> ipconfig /all > c:\test.txt
> >> >> ping 64.233.183.104 >> c:\test.txt
> >> >> notepad c:\test.txt
> >> >> - Post the contents of both files.
> >> >>
> >> >>
> >> >> "David L." <DavidL@discussions.microsoft.com> wrote in message
> >> >> news:D707117E-BD02-4FF9-AA92-B6D8A911A0E4@microsoft.com...
> >> >> > The ping problem remains even with both firewalls turned off.
> >> >> >
> >> >> > I've also gone through all of the all articles that I could find
> >> >> > about
> >> >> > remote desktop. I don't know if I'm correct but I think once the
> >> >> > ping
> >> >> > problem
> >> >> > is resolved the remote desktop should work.
> >> >> >
> >> >> >
> >> >> > "Pegasus (MVP)" wrote:
> >> >> >
> >> >> >>
> >> >> >> "David L." <David L.@discussions.microsoft.com> wrote in message
> >> >> >> news:41C9895E-7BBD-439A-841A-D565E2272C53@microsoft.com...
> >> >> >> > Hello All,
> >> >> >> >
> >> >> >> > Any help I can get with this issue is going to be very much
> >> >> >> > appreciated.
> >> >> >> > I've been stumping myself at this for around 2 weeks now.
> >> >> >> >
> >> >> >> > I have two computers on my network, one desktop and one tablet.
> >> >> >> > Both
> >> >> >> > are
> >> >> >> > running XP Pro and both can connect to the Internet.
> >> >> >> >
> >> >> >> > The final solution I'm trying to arrive at is to have the tablet
> >> >> >> > pc
> >> >> >> > Remote
> >> >> >> > Desktop connect to the desktop pc. I've followed all of the steps
> >> >> >> > to
> >> >> >> > setting
> >> >> >> > up Remote Desktop so I think that aspect is configured correctly.
> >> >> >> > Yet
> >> >> >> > when
> >> >> >> > I
> >> >> >> > try to search the workgroup, I get that "There is no terminal
> >> >> >> > service
> >> >> >> > running". Alternatively, when I try to connect to the IP address
> >> >> >> > directly,
> >> >> >> > I
> >> >> >> > get that the computer is unavailable and maynot be accepting new
> >> >> >> > users
> >> >> >> > (or
> >> >> >> > something to that nature).
> >> >> >> >
> >> >> >> > Another problem that occurs, which to me implies that the issue
> >> >> >> > is a
> >> >> >> > networking one. Is that I can't ping the desktop from the tablet.
> >> >> >> > I
> >> >> >> > CAN
> >> >> >> > ping
> >> >> >> > the tablet from the desktop though and both can ping themselves.
> >> >> >> >
> >> >> >> > I'm lost. Please help.
> >> >> >> >
> >> >> >> > Best,
> >> >> >> > DL
> >> >> >>
> >> >> >> Turn off the Windows firewall during testing until you get your
> >> >> >> ping problem resolved. Make sure to disconnect your network
> >> >> >> from the Internet while the firewall is turned off.
> >> >> >>
> >> >> >> Click Start / Help, then look for help on "Remote Desktop" to
> >> >> >> see how to enable this facility.
> >> >> >>
> >> >> >> Post again if you need more help.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
 
Aida32 will tell you what hardware you have:
http://www.aumha.org/freeware/freeware.php#aida32


"David L." <DavidL@discussions.microsoft.com> wrote in message
news:15CAB32D-F8E6-460C-BB7D-F2CAE2BD6AE3@microsoft.com...
> Ok, So you've raised a very valid point. Here's some more history:
>
> LivingRoom is a tablet pc that a friend was using for work - ie. it got
> real
> cluttered but the machine was completly functional, def the wirelss
> aspect.
> So I reformated it and installed a fresh copy of XP Pro (that's why the
> time
> is off. I haven't cleaned it up yet, it's brand new). Since it's a tablet
> pc
> there were a bunch of funky drivers that it requires (for touch control
> and
> other compact hardware).
>
> After I installed all the dirvers (recommended by the manufacturer, one of
> them still seemed not to work) - the wireless adapter. Whenever I try to
> configure it with the Realtek software provided w/ the dirver (via the
> link
> below) I get "No Wireless Network Adapter Found". I know it worked prior
> to
> my reinstall of XP but I can't get it to work now. The manufacturer will
> not
> respond to me beyond thier "here try this" link to a .zip file, supposidly
> containing all the drivers for this particular issue. It obviously is
> lacking
> one. This is the file they say should have fixed this...
>
> http://www.tabletkiosk.com/support/files/Sahara_SDV-T01/Wireless.zip
>
> In device manager under Network Adapters I have 1339 & Realtek 8139, then
> Other Devices has a "?" as well as it's subcategory Network Contorler has
> a
> "?".
>
> I didn't think this was going to be a problem because it was going to be a
> stationary computer and I could connect w/ a cat5, however based on your
> last
> response I see it is an issue.
>
> Is there a way to find out exactly which wireless network adapter I have?
> There is a folder in that zip file titled "802MR-W". I think that's it but
> I
> do not see a setup.exe for it. I assume that its what is showing up as
> Other
> Devices and therefore has no driver. am I correct?
>
>
> "Pegasus (MVP)" wrote:
>
>> Sorry for the mistake in the telnet command. It seems you
>> compensated for it quite nicely.
>>
>> Yes, respondent "smlunatick" is correct: When using
>> Remote Desktop then you must use an account on that
>> host machine that has a non-blank passwords. However,
>> you're not at that stage just yet.
>>
>> Your tests prove these points:
>> - Your network appears to be working. Both machines
>> can set test packets to an external site.
>> - The Office machine can exchange test packets with the
>> LivingRoom machine.
>> - The LivingRoom machine cannot exchange test packets
>> with the Office machine.
>>
>> I can think of these reasons why this would happen. I'm
>> ignoring here what you wrote in your previous notes:
>> a) The Windows firewall on Office is active.
>> b) There is a third-party firewall active or installed on Office.
>> c) The IP address of Office is something other than 192.168.1.20.
>> d) The network adapter of Office is flawed (unlikely but possible).
>> e) The network switch port used by the Office machine is
>> flawed (unlikely but possible).
>> f) The network switch (or router) is in a funny mode. Rebooting
>> it would probably fix it.
>>
>> Why not try it in reverse? Enable Remote Desktop on Living
>> Room, then type this command on Office: mstsc /v:LivingRoom
>>
>>
>> "David L." <DavidL@discussions.microsoft.com> wrote in message
>> news:A0803A17-0E7C-4F81-B690-9AEA11B15949@microsoft.com...
>> > Sorry for the delay. work sent me on a day trip around the world (or at
>> > least
>> > close to it). It sucked. Anyway... thanks for the help and here is the
>> > data
>> > you requested. Also, regarding the other person that mentioned about
>> > the
>> > username and passwords, LivingRoom does not have a password - should
>> > it?
>> >
>> > *******************************
>> > Office Data Below
>> > *******************************
>> > Pinging 192.168.1.21 with 32 bytes of data:
>> > Reply from 192.168.1.21: bytes=32 time=5ms TTL=128
>> > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
>> > Reply from 192.168.1.21: bytes=32 time=1261ms TTL=128
>> > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
>> >
>> > Ping statistics for 192.168.1.21:
>> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>> > Approximate round trip times in milli-seconds:
>> > Minimum = 2ms, Maximum = 1261ms, Average = 317ms
>> >
>> > Pinging LivingRoom [192.168.1.21] with 32 bytes of data:
>> > Reply from 192.168.1.21: bytes=32 time=1ms TTL=128
>> > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
>> > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
>> > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
>> >
>> > Ping statistics for 192.168.1.21:
>> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>> > Approximate round trip times in milli-seconds:
>> > Minimum = 1ms, Maximum = 2ms, Average = 1ms
>> >
>> > Pinging 64.233.183.104 with 32 bytes of data:
>> > Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
>> > Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
>> > Reply from 64.233.183.104: bytes=32 time=137ms TTL=231
>> > Reply from 64.233.183.104: bytes=32 time=132ms TTL=231
>> >
>> > Ping statistics for 64.233.183.104:
>> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>> > Approximate round trip times in milli-seconds:
>> > Minimum = 132ms, Maximum = 137ms, Average = 133ms
>> > TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
>> > Port# in ..\RDP-Tcp\PortNumber = 3389
>> >
>> >
>> > *******************************
>> > LivingRoom Data Below
>> > *******************************
>> > Pinging 192.168.1.20 with 32 bytes of data:
>> > Request timed out.
>> > Request timed out.
>> > Request timed out.
>> > Request timed out.
>> >
>> > Ping statistics for 192.168.1.20:
>> > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>> > Ping request could not find host Office. Please check the name and try
>> > again.
>> >
>> > Pinging 64.233.183.104 with 32 bytes of data:
>> > Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
>> > Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
>> > Reply from 64.233.183.104: bytes=32 time=148ms TTL=231
>> > Reply from 64.233.183.104: bytes=32 time=138ms TTL=231
>> >
>> > Ping statistics for 64.233.183.104:
>> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>> > Approximate round trip times in milli-seconds:
>> > Minimum = 134ms, Maximum = 148ms, Average = 138ms
>> >
>> > \\When I ran the next telnet command as you gave it to me I kept
>> > getting a
>> > syntax error. So I ran it as below and typed in the results (instead of
>> > having them write to the test.txt file), is was://
>> > \\Command:telnet 192.168.1.20 3389
>> > Connecting to 192.168.1.20...Could not open connection to the host, on
>> > port
>> > 3389: Connect failed.
>> >
>> > "Pegasus (MVP)" wrote:
>> >
>> >> It does not make much sense having one machine on DHCP
>> >> and the other on a fixed IP address. I suggest you turn off
>> >> DHCP on both machines and assign the following addresses:
>> >>
>> >> Office 192.168.1.20
>> >> LivingRoom 192.168.1.21
>> >>
>> >> I recommand that you set the DSN addreses like so
>> >> on both machines:
>> >> Primary 192.168.1.1
>> >> Others 72.45.32.34, 72.45.32.37
>> >>
>> >> After doing this, execute the following commands on Office
>> >> and post the result file:
>> >> ping 192.168.1.21 > c:\test.txt
>> >> ping LivingRoom >> c:\test.txt
>> >> ping 64.233.183.104 >> c:\test.txt
>> >> netstat -an | find "3389" >> test.txt
>> >> Please do not omit the third command this time!
>> >>
>> >> On LivingRoom I would like you to run these commands:
>> >> ping 192.168.1.20 > c:\test.txt
>> >> ping Office >> c:\test.txt
>> >> ping 64.233.183.104 >> c:\test.txt
>> >> telnet 192.168.1.20 3389 >> 1c:\test.txt 2>>&1
>> >>
>> >> Lastly I would like you to report the port number at this registry
>> >> location on Office:
>> >> HKLM\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber
>> >>
>> >>
>> >> "David L." <DavidL@discussions.microsoft.com> wrote in message
>> >> news:840E2823-C8EF-407F-B194-831C8D9326C3@microsoft.com...
>> >> >I do not have Zone Alarm, I'm only using the windows firewall
>> >> >software
>> >> >as
>> >> >of
>> >> > now.
>> >> >
>> >> > Here are the IP address details for both comps...
>> >> >
>> >> > *************************************
>> >> > 1st Computer Below (Desired Host)
>> >> > *************************************
>> >> >
>> >> > Windows IP Configuration
>> >> > Host Name . . . . . . . . . . . . : Office
>> >> > Primary Dns Suffix . . . . . . . :
>> >> > Node Type . . . . . . . . . . . . : Unknown
>> >> > IP Routing Enabled. . . . . . . . : Yes
>> >> > WINS Proxy Enabled. . . . . . . . : Yes
>> >> >
>> >> > Ethernet adapter Wireless Network Connection 2:
>> >> > Connection-specific DNS Suffix . :
>> >> > Description . . . . . . . . . . . : Linksys Wireless-G PCI
>> >> > Adapter
>> >> > Physical Address. . . . . . . . . : 00-18-39-14-D6-0A
>> >> > Dhcp Enabled. . . . . . . . . . . : No
>> >> > IP Address. . . . . . . . . . . . : 192.168.1.20
>> >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> >> > Default Gateway . . . . . . . . . : 192.168.1.1
>> >> > DNS Servers . . . . . . . . . . . : 72.45.32.34
>> >> > 72.45.32.37
>> >> >
>> >> > *************************************
>> >> > 2nd Computer Below (Desired Client)
>> >> > *************************************
>> >> > Windows IP Configuration
>> >> > Host Name . . . . . . . . . . . . : LivingRoom
>> >> > Primary Dns Suffix . . . . . . . :
>> >> > Node Type . . . . . . . . . . . . : Unknown
>> >> > IP Routing Enabled. . . . . . . . : No
>> >> > WINS Proxy Enabled. . . . . . . . : No
>> >> > DNS Suffix Search List. . . . . . : the-beach.net
>> >> >
>> >> > Ethernet adapter Local Area Connection 2:
>> >> > Connection-specific DNS Suffix . : the-beach.net
>> >> > Description . . . . . . . . . . . : Realtek RTL8139 Family
>> >> > PCI
>> >> > Fast
>> >> > Ethernet NIC
>> >> > Physical Address. . . . . . . . . : 00-0C-6F-00-0B-3D
>> >> > Dhcp Enabled. . . . . . . . . . . : Yes
>> >> > Autoconfiguration Enabled . . . . : Yes
>> >> > IP Address. . . . . . . . . . . . : 192.168.1.107
>> >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> >> > Default Gateway . . . . . . . . . : 192.168.1.1
>> >> > DHCP Server . . . . . . . . . . . : 192.168.1.1
>> >> > DNS Servers . . . . . . . . . . . : 72.45.32.34
>> >> > 72.45.32.37
>> >> > Lease Obtained. . . . . . . . . . : Friday, October 20, 2006
>> >> > 7:21:20
>> >> > AM
>> >> > Lease Expires . . . . . . . . . . : Saturday, October 21,
>> >> > 2006
>> >> > 7:21:20 AM
>> >> >
>> >> >
>> >> >
>> >> > "Pegasus (MVP)" wrote:
>> >> >
>> >> >> A couple of suggestions:
>> >> >> - If you have ZoneAlarm installed then you must uninstall it. This
>> >> >> utility is known for blocking network traffic, even while
>> >> >> disabled.
>> >> >> - You should post your full IP address details. Do this on each PC:
>> >> >> * Click Start / Run / cmd {OK}
>> >> >> * Type these commands:
>> >> >> ipconfig /all > c:\test.txt
>> >> >> ping 64.233.183.104 >> c:\test.txt
>> >> >> notepad c:\test.txt
>> >> >> - Post the contents of both files.
>> >> >>
>> >> >>
>> >> >> "David L." <DavidL@discussions.microsoft.com> wrote in message
>> >> >> news:D707117E-BD02-4FF9-AA92-B6D8A911A0E4@microsoft.com...
>> >> >> > The ping problem remains even with both firewalls turned off.
>> >> >> >
>> >> >> > I've also gone through all of the all articles that I could find
>> >> >> > about
>> >> >> > remote desktop. I don't know if I'm correct but I think once the
>> >> >> > ping
>> >> >> > problem
>> >> >> > is resolved the remote desktop should work.
>> >> >> >
>> >> >> >
>> >> >> > "Pegasus (MVP)" wrote:
>> >> >> >
>> >> >> >>
>> >> >> >> "David L." <David L.@discussions.microsoft.com> wrote in message
>> >> >> >> news:41C9895E-7BBD-439A-841A-D565E2272C53@microsoft.com...
>> >> >> >> > Hello All,
>> >> >> >> >
>> >> >> >> > Any help I can get with this issue is going to be very much
>> >> >> >> > appreciated.
>> >> >> >> > I've been stumping myself at this for around 2 weeks now.
>> >> >> >> >
>> >> >> >> > I have two computers on my network, one desktop and one
>> >> >> >> > tablet.
>> >> >> >> > Both
>> >> >> >> > are
>> >> >> >> > running XP Pro and both can connect to the Internet.
>> >> >> >> >
>> >> >> >> > The final solution I'm trying to arrive at is to have the
>> >> >> >> > tablet
>> >> >> >> > pc
>> >> >> >> > Remote
>> >> >> >> > Desktop connect to the desktop pc. I've followed all of the
>> >> >> >> > steps
>> >> >> >> > to
>> >> >> >> > setting
>> >> >> >> > up Remote Desktop so I think that aspect is configured
>> >> >> >> > correctly.
>> >> >> >> > Yet
>> >> >> >> > when
>> >> >> >> > I
>> >> >> >> > try to search the workgroup, I get that "There is no terminal
>> >> >> >> > service
>> >> >> >> > running". Alternatively, when I try to connect to the IP
>> >> >> >> > address
>> >> >> >> > directly,
>> >> >> >> > I
>> >> >> >> > get that the computer is unavailable and maynot be accepting
>> >> >> >> > new
>> >> >> >> > users
>> >> >> >> > (or
>> >> >> >> > something to that nature).
>> >> >> >> >
>> >> >> >> > Another problem that occurs, which to me implies that the
>> >> >> >> > issue
>> >> >> >> > is a
>> >> >> >> > networking one. Is that I can't ping the desktop from the
>> >> >> >> > tablet.
>> >> >> >> > I
>> >> >> >> > CAN
>> >> >> >> > ping
>> >> >> >> > the tablet from the desktop though and both can ping
>> >> >> >> > themselves.
>> >> >> >> >
>> >> >> >> > I'm lost. Please help.
>> >> >> >> >
>> >> >> >> > Best,
>> >> >> >> > DL
>> >> >> >>
>> >> >> >> Turn off the Windows firewall during testing until you get your
>> >> >> >> ping problem resolved. Make sure to disconnect your network
>> >> >> >> from the Internet while the firewall is turned off.
>> >> >> >>
>> >> >> >> Click Start / Help, then look for help on "Remote Desktop" to
>> >> >> >> see how to enable this facility.
>> >> >> >>
>> >> >> >> Post again if you need more help.
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
 
On Dec 4, 10:37 am, David L. <Dav...@discussions.microsoft.com> wrote:
> Ok, So you've raised a very valid point. Here's some more history:
>
> LivingRoom is a tablet pc that a friend was using for work - ie. it got real
> cluttered but the machine was completly functional, def the wirelss aspect.
> So I reformated it and installed a fresh copy of XP Pro (that's why the time
> is off. I haven't cleaned it up yet, it's brand new). Since it's a tablet pc
> there were a bunch of funky drivers that it requires (for touch control and
> other compact hardware).
>
> After I installed all the dirvers (recommended by the manufacturer, one of
> them still seemed not to work) - the wireless adapter. Whenever I try to
> configure it with the Realtek software provided w/ the dirver (via the link
> below) I get "No Wireless Network Adapter Found". I know it worked prior to
> my reinstall of XP but I can't get it to work now. The manufacturer will not
> respond to me beyond thier "here try this" link to a .zip file, supposidly
> containing all the drivers for this particular issue. It obviously is lacking
> one. This is the file they say should have fixed this...
>
> http://www.tabletkiosk.com/support/files/Sahara_SDV-T01/Wireless.zip
>
> In device manager under Network Adapters I have 1339 & Realtek 8139, then
> Other Devices has a "?" as well as it's subcategory Network Contorler has a
> "?".
>
> I didn't think this was going to be a problem because it was going to be a
> stationary computer and I could connect w/ a cat5, however based on your last
> response I see it is an issue.
>
> Is there a way to find out exactly which wireless network adapter I have?
> There is a folder in that zip file titled "802MR-W". I think that's it but I
> do not see a setup.exe for it. I assume that its what is showing up as Other
> Devices and therefore has no driver. am I correct?
>
>
>
> "Pegasus (MVP)" wrote:
> > Sorry for the mistake in the telnet command. It seems you
> > compensated for it quite nicely.

>
> > Yes, respondent "smlunatick" is correct: When using
> > Remote Desktop then you must use an account on that
> > host machine that has a non-blank passwords. However,
> > you're not at that stage just yet.

>
> > Your tests prove these points:
> > - Your network appears to be working. Both machines
> > can set test packets to an external site.
> > - The Office machine can exchange test packets with the
> > LivingRoom machine.
> > - The LivingRoom machine cannot exchange test packets
> > with the Office machine.

>
> > I can think of these reasons why this would happen. I'm
> > ignoring here what you wrote in your previous notes:
> > a) The Windows firewall on Office is active.
> > b) There is a third-party firewall active or installed on Office.
> > c) The IP address of Office is something other than 192.168.1.20.
> > d) The network adapter of Office is flawed (unlikely but possible).
> > e) The network switch port used by the Office machine is
> > flawed (unlikely but possible).
> > f) The network switch (or router) is in a funny mode. Rebooting
> > it would probably fix it.

>
> > Why not try it in reverse? Enable Remote Desktop on Living
> > Room, then type this command on Office: mstsc /v:LivingRoom

>
> > "David L." <Dav...@discussions.microsoft.com> wrote in message
> >news:A0803A17-0E7C-4F81-B690-9AEA11B15949@microsoft.com...
> > > Sorry for the delay. work sent me on a day trip around the world (or at
> > > least
> > > close to it). It sucked. Anyway... thanks for the help and here is the
> > > data
> > > you requested. Also, regarding the other person that mentioned about the
> > > username and passwords, LivingRoom does not have a password - should it?

>
> > > *******************************
> > > Office Data Below
> > > *******************************
> > > Pinging 192.168.1.21 with 32 bytes of data:
> > > Reply from 192.168.1.21: bytes=32 time=5ms TTL=128
> > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > > Reply from 192.168.1.21: bytes=32 time=1261ms TTL=128
> > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128

>
> > > Ping statistics for 192.168.1.21:
> > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > Approximate round trip times in milli-seconds:
> > > Minimum = 2ms, Maximum = 1261ms, Average = 317ms

>
> > > Pinging LivingRoom [192.168.1.21] with 32 bytes of data:
> > > Reply from 192.168.1.21: bytes=32 time=1ms TTL=128
> > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128

>
> > > Ping statistics for 192.168.1.21:
> > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > Approximate round trip times in milli-seconds:
> > > Minimum = 1ms, Maximum = 2ms, Average = 1ms

>
> > > Pinging 64.233.183.104 with 32 bytes of data:
> > > Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
> > > Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
> > > Reply from 64.233.183.104: bytes=32 time=137ms TTL=231
> > > Reply from 64.233.183.104: bytes=32 time=132ms TTL=231

>
> > > Ping statistics for 64.233.183.104:
> > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > Approximate round trip times in milli-seconds:
> > > Minimum = 132ms, Maximum = 137ms, Average = 133ms
> > > TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
> > > Port# in ..\RDP-Tcp\PortNumber = 3389

>
> > > *******************************
> > > LivingRoom Data Below
> > > *******************************
> > > Pinging 192.168.1.20 with 32 bytes of data:
> > > Request timed out.
> > > Request timed out.
> > > Request timed out.
> > > Request timed out.

>
> > > Ping statistics for 192.168.1.20:
> > > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> > > Ping request could not find host Office. Please check the name and try
> > > again.

>
> > > Pinging 64.233.183.104 with 32 bytes of data:
> > > Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
> > > Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
> > > Reply from 64.233.183.104: bytes=32 time=148ms TTL=231
> > > Reply from 64.233.183.104: bytes=32 time=138ms TTL=231

>
> > > Ping statistics for 64.233.183.104:
> > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > Approximate round trip times in milli-seconds:
> > > Minimum = 134ms, Maximum = 148ms, Average = 138ms

>
> > > \\When I ran the next telnet command as you gave it to me I kept getting a
> > > syntax error. So I ran it as below and typed in the results (instead of
> > > having them write to the test.txt file), is was://
> > > \\Command:telnet 192.168.1.20 3389
> > > Connecting to 192.168.1.20...Could not open connection to the host, on
> > > port
> > > 3389: Connect failed.

>
> > > "Pegasus (MVP)" wrote:

>
> > >> It does not make much sense having one machine on DHCP
> > >> and the other on a fixed IP address. I suggest you turn off
> > >> DHCP on both machines and assign the following addresses:

>
> > >> Office 192.168.1.20
> > >> LivingRoom 192.168.1.21

>
> > >> I recommand that you set the DSN addreses like so
> > >> on both machines:
> > >> Primary 192.168.1.1
> > >> Others 72.45.32.34, 72.45.32.37

>
> > >> After doing this, execute the following commands on Office
> > >> and post the result file:
> > >> ping 192.168.1.21 > c:\test.txt
> > >> ping LivingRoom >> c:\test.txt
> > >> ping 64.233.183.104 >> c:\test.txt
> > >> netstat -an | find "3389" >> test.txt
> > >> Please do not omit the third command this time!

>
> > >> On LivingRoom I would like you to run these commands:
> > >> ping 192.168.1.20 > c:\test.txt
> > >> ping Office >> c:\test.txt
> > >> ping 64.233.183.104 >> c:\test.txt
> > >> telnet 192.168.1.20 3389 >> 1c:\test.txt 2>>&1

>
> > >> Lastly I would like you to report the port number at this registry
> > >> location on Office:
> > >> HKLM\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\Po-rtNumber

>
> > >> "David L." <Dav...@discussions.microsoft.com> wrote in message
> > >>news:840E2823-C8EF-407F-B194-831C8D9326C3@microsoft.com...
> > >> >I do not have Zone Alarm, I'm only using the windows firewall software
> > >> >as
> > >> >of
> > >> > now.

>
> > >> > Here are the IP address details for both comps...

>
> > >> > *************************************
> > >> > 1st Computer Below (Desired Host)
> > >> > *************************************

>
> > >> > Windows IP Configuration
> > >> > Host Name . . . . . . . . . . . . : Office
> > >> > Primary Dns Suffix . . . . . . . :
> > >> > Node Type . . . . . . . . . . . . : Unknown
> > >> > IP Routing Enabled. . . . . . . . : Yes
> > >> > WINS Proxy Enabled. . . . . . . . : Yes

>
> > >> > Ethernet adapter Wireless Network Connection 2:
> > >> > Connection-specific DNS Suffix . :
> > >> > Description . . . . . . . . . . . : Linksys Wireless-G PCI
> > >> > Adapter
> > >> > Physical Address. . . . . . . . . : 00-18-39-14-D6-0A
> > >> > Dhcp Enabled. . . . . . . . . . . : No
> > >> > IP Address. . . . . . . . . . . . : 192.168.1.20
> > >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > >> > Default Gateway . . . . . . . . . : 192.168.1.1
> > >> > DNS Servers . . . . . . . . . . . : 72.45.32.34
> > >> > 72.45.32.37

>
> > >> > *************************************
> > >> > 2nd Computer Below (Desired Client)
> > >> > *************************************
> > >> > Windows IP Configuration
> > >> > Host Name . . . . . . . . . . . . : LivingRoom
> > >> > Primary Dns Suffix . . . . . . . :
> > >> > Node Type . . . . . . . . . . . . : Unknown
> > >> > IP Routing Enabled. . . . . . . . : No
> > >> > WINS Proxy Enabled. . . . . . . . : No
> > >> > DNS Suffix Search List. . . . . . : the-beach.net

>
> > >> > Ethernet adapter Local Area Connection 2:
> > >> > Connection-specific DNS Suffix . : the-beach.net
> > >> > Description . . . . . . . . . . . : Realtek RTL8139 Family PCI
> > >> > Fast
> > >> > Ethernet NIC
> > >> > Physical Address. . . . . . . . . : 00-0C-6F-00-0B-3D
> > >> > Dhcp Enabled. . . . . . . . . . . : Yes
> > >> > Autoconfiguration

>
> ...
>
> read more >>- Hide quoted text -
>
> - Show quoted text -


Did ou re-install the motherboard chipset driver for the tablet?
 
Late last night I finally got it to work. Man it was a task. The Aida32
program was a life saver. The manufacture would offer no support at all. Then
finding the driver was a task all in itself. If you do buy from these guys
http://www.tabletkiosk.com/ don't ever think you'll be getting any tech
support.

Anyway, the wireless is up and running and there are now no exclamations in
device manager.

Remote Desktop is now telling me the same thing on both comps - "The
workgroup/domain does not contain any terminal servers"

I'll run post the current IP address details for the tablet now.


"smlunatick" wrote:

> On Dec 4, 10:37 am, David L. <Dav...@discussions.microsoft.com> wrote:
> > Ok, So you've raised a very valid point. Here's some more history:
> >
> > LivingRoom is a tablet pc that a friend was using for work - ie. it got real
> > cluttered but the machine was completly functional, def the wirelss aspect.
> > So I reformated it and installed a fresh copy of XP Pro (that's why the time
> > is off. I haven't cleaned it up yet, it's brand new). Since it's a tablet pc
> > there were a bunch of funky drivers that it requires (for touch control and
> > other compact hardware).
> >
> > After I installed all the dirvers (recommended by the manufacturer, one of
> > them still seemed not to work) - the wireless adapter. Whenever I try to
> > configure it with the Realtek software provided w/ the dirver (via the link
> > below) I get "No Wireless Network Adapter Found". I know it worked prior to
> > my reinstall of XP but I can't get it to work now. The manufacturer will not
> > respond to me beyond thier "here try this" link to a .zip file, supposidly
> > containing all the drivers for this particular issue. It obviously is lacking
> > one. This is the file they say should have fixed this...
> >
> > http://www.tabletkiosk.com/support/files/Sahara_SDV-T01/Wireless.zip
> >
> > In device manager under Network Adapters I have 1339 & Realtek 8139, then
> > Other Devices has a "?" as well as it's subcategory Network Contorler has a
> > "?".
> >
> > I didn't think this was going to be a problem because it was going to be a
> > stationary computer and I could connect w/ a cat5, however based on your last
> > response I see it is an issue.
> >
> > Is there a way to find out exactly which wireless network adapter I have?
> > There is a folder in that zip file titled "802MR-W". I think that's it but I
> > do not see a setup.exe for it. I assume that its what is showing up as Other
> > Devices and therefore has no driver. am I correct?
> >
> >
> >
> > "Pegasus (MVP)" wrote:
> > > Sorry for the mistake in the telnet command. It seems you
> > > compensated for it quite nicely.

> >
> > > Yes, respondent "smlunatick" is correct: When using
> > > Remote Desktop then you must use an account on that
> > > host machine that has a non-blank passwords. However,
> > > you're not at that stage just yet.

> >
> > > Your tests prove these points:
> > > - Your network appears to be working. Both machines
> > > can set test packets to an external site.
> > > - The Office machine can exchange test packets with the
> > > LivingRoom machine.
> > > - The LivingRoom machine cannot exchange test packets
> > > with the Office machine.

> >
> > > I can think of these reasons why this would happen. I'm
> > > ignoring here what you wrote in your previous notes:
> > > a) The Windows firewall on Office is active.
> > > b) There is a third-party firewall active or installed on Office.
> > > c) The IP address of Office is something other than 192.168.1.20.
> > > d) The network adapter of Office is flawed (unlikely but possible).
> > > e) The network switch port used by the Office machine is
> > > flawed (unlikely but possible).
> > > f) The network switch (or router) is in a funny mode. Rebooting
> > > it would probably fix it.

> >
> > > Why not try it in reverse? Enable Remote Desktop on Living
> > > Room, then type this command on Office: mstsc /v:LivingRoom

> >
> > > "David L." <Dav...@discussions.microsoft.com> wrote in message
> > >news:A0803A17-0E7C-4F81-B690-9AEA11B15949@microsoft.com...
> > > > Sorry for the delay. work sent me on a day trip around the world (or at
> > > > least
> > > > close to it). It sucked. Anyway... thanks for the help and here is the
> > > > data
> > > > you requested. Also, regarding the other person that mentioned about the
> > > > username and passwords, LivingRoom does not have a password - should it?

> >
> > > > *******************************
> > > > Office Data Below
> > > > *******************************
> > > > Pinging 192.168.1.21 with 32 bytes of data:
> > > > Reply from 192.168.1.21: bytes=32 time=5ms TTL=128
> > > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > > > Reply from 192.168.1.21: bytes=32 time=1261ms TTL=128
> > > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128

> >
> > > > Ping statistics for 192.168.1.21:
> > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > > Approximate round trip times in milli-seconds:
> > > > Minimum = 2ms, Maximum = 1261ms, Average = 317ms

> >
> > > > Pinging LivingRoom [192.168.1.21] with 32 bytes of data:
> > > > Reply from 192.168.1.21: bytes=32 time=1ms TTL=128
> > > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128

> >
> > > > Ping statistics for 192.168.1.21:
> > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > > Approximate round trip times in milli-seconds:
> > > > Minimum = 1ms, Maximum = 2ms, Average = 1ms

> >
> > > > Pinging 64.233.183.104 with 32 bytes of data:
> > > > Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
> > > > Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
> > > > Reply from 64.233.183.104: bytes=32 time=137ms TTL=231
> > > > Reply from 64.233.183.104: bytes=32 time=132ms TTL=231

> >
> > > > Ping statistics for 64.233.183.104:
> > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > > Approximate round trip times in milli-seconds:
> > > > Minimum = 132ms, Maximum = 137ms, Average = 133ms
> > > > TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
> > > > Port# in ..\RDP-Tcp\PortNumber = 3389

> >
> > > > *******************************
> > > > LivingRoom Data Below
> > > > *******************************
> > > > Pinging 192.168.1.20 with 32 bytes of data:
> > > > Request timed out.
> > > > Request timed out.
> > > > Request timed out.
> > > > Request timed out.

> >
> > > > Ping statistics for 192.168.1.20:
> > > > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> > > > Ping request could not find host Office. Please check the name and try
> > > > again.

> >
> > > > Pinging 64.233.183.104 with 32 bytes of data:
> > > > Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
> > > > Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
> > > > Reply from 64.233.183.104: bytes=32 time=148ms TTL=231
> > > > Reply from 64.233.183.104: bytes=32 time=138ms TTL=231

> >
> > > > Ping statistics for 64.233.183.104:
> > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > > Approximate round trip times in milli-seconds:
> > > > Minimum = 134ms, Maximum = 148ms, Average = 138ms

> >
> > > > \\When I ran the next telnet command as you gave it to me I kept getting a
> > > > syntax error. So I ran it as below and typed in the results (instead of
> > > > having them write to the test.txt file), is was://
> > > > \\Command:telnet 192.168.1.20 3389
> > > > Connecting to 192.168.1.20...Could not open connection to the host, on
> > > > port
> > > > 3389: Connect failed.

> >
> > > > "Pegasus (MVP)" wrote:

> >
> > > >> It does not make much sense having one machine on DHCP
> > > >> and the other on a fixed IP address. I suggest you turn off
> > > >> DHCP on both machines and assign the following addresses:

> >
> > > >> Office 192.168.1.20
> > > >> LivingRoom 192.168.1.21

> >
> > > >> I recommand that you set the DSN addreses like so
> > > >> on both machines:
> > > >> Primary 192.168.1.1
> > > >> Others 72.45.32.34, 72.45.32.37

> >
> > > >> After doing this, execute the following commands on Office
> > > >> and post the result file:
> > > >> ping 192.168.1.21 > c:\test.txt
> > > >> ping LivingRoom >> c:\test.txt
> > > >> ping 64.233.183.104 >> c:\test.txt
> > > >> netstat -an | find "3389" >> test.txt
> > > >> Please do not omit the third command this time!

> >
> > > >> On LivingRoom I would like you to run these commands:
> > > >> ping 192.168.1.20 > c:\test.txt
> > > >> ping Office >> c:\test.txt
> > > >> ping 64.233.183.104 >> c:\test.txt
> > > >> telnet 192.168.1.20 3389 >> 1c:\test.txt 2>>&1

> >
> > > >> Lastly I would like you to report the port number at this registry
> > > >> location on Office:
> > > >> HKLM\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\Po-rtNumber

> >
> > > >> "David L." <Dav...@discussions.microsoft.com> wrote in message
> > > >>news:840E2823-C8EF-407F-B194-831C8D9326C3@microsoft.com...
> > > >> >I do not have Zone Alarm, I'm only using the windows firewall software
> > > >> >as
> > > >> >of
> > > >> > now.

> >
> > > >> > Here are the IP address details for both comps...

> >
> > > >> > *************************************
> > > >> > 1st Computer Below (Desired Host)
> > > >> > *************************************

> >
> > > >> > Windows IP Configuration
> > > >> > Host Name . . . . . . . . . . . . : Office
> > > >> > Primary Dns Suffix . . . . . . . :
> > > >> > Node Type . . . . . . . . . . . . : Unknown
> > > >> > IP Routing Enabled. . . . . . . . : Yes
> > > >> > WINS Proxy Enabled. . . . . . . . : Yes

> >
> > > >> > Ethernet adapter Wireless Network Connection 2:
> > > >> > Connection-specific DNS Suffix . :
> > > >> > Description . . . . . . . . . . . : Linksys Wireless-G PCI
> > > >> > Adapter
> > > >> > Physical Address. . . . . . . . . : 00-18-39-14-D6-0A
> > > >> > Dhcp Enabled. . . . . . . . . . . : No
> > > >> > IP Address. . . . . . . . . . . . : 192.168.1.20
> > > >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > >> > Default Gateway . . . . . . . . . : 192.168.1.1
> > > >> > DNS Servers . . . . . . . . . . . : 72.45.32.34
> > > >> > 72.45.32.37

> >
> > > >> > *************************************
> > > >> > 2nd Computer Below (Desired Client)
> > > >> > *************************************
> > > >> > Windows IP Configuration
> > > >> > Host Name . . . . . . . . . . . . : LivingRoom
> > > >> > Primary Dns Suffix . . . . . . . :
> > > >> > Node Type . . . . . . . . . . . . : Unknown
> > > >> > IP Routing Enabled. . . . . . . . : No
> > > >> > WINS Proxy Enabled. . . . . . . . : No
> > > >> > DNS Suffix Search List. . . . . . : the-beach.net

> >
> > > >> > Ethernet adapter Local Area Connection 2:
> > > >> > Connection-specific DNS Suffix . : the-beach.net
> > > >> > Description . . . . . . . . . . . : Realtek RTL8139 Family PCI
> > > >> > Fast
> > > >> > Ethernet NIC
> > > >> > Physical Address. . . . . . . . . : 00-0C-6F-00-0B-3D
> > > >> > Dhcp Enabled. . . . . . . . . . . : Yes
> > > >> > Autoconfiguration

> >
> > ...
> >
> > read more >>- Hide quoted text -
> >
> > - Show quoted text -

>
> Did ou re-install the motherboard chipset driver for the tablet?
>
 
Here they are....

Pinging 192.168.1.20 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.20:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Ping request could not find host Office. Please check the name and try again.

Pinging 64.233.183.104 with 32 bytes of data:
Reply from 64.233.183.104: bytes=32 time=136ms TTL=231
Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
Reply from 64.233.183.104: bytes=32 time=136ms TTL=231
Reply from 64.233.183.104: bytes=32 time=130ms TTL=231
Ping statistics for 64.233.183.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 130ms, Maximum = 136ms, Average = 134ms

Connecting To 192.168,20...Could not open connection to the host, on port
3389: Connect Failed


"David L." wrote:

> Late last night I finally got it to work. Man it was a task. The Aida32
> program was a life saver. The manufacture would offer no support at all. Then
> finding the driver was a task all in itself. If you do buy from these guys
> http://www.tabletkiosk.com/ don't ever think you'll be getting any tech
> support.
>
> Anyway, the wireless is up and running and there are now no exclamations in
> device manager.
>
> Remote Desktop is now telling me the same thing on both comps - "The
> workgroup/domain does not contain any terminal servers"
>
> I'll run post the current IP address details for the tablet now.
>
>
> "smlunatick" wrote:
>
> > On Dec 4, 10:37 am, David L. <Dav...@discussions.microsoft.com> wrote:
> > > Ok, So you've raised a very valid point. Here's some more history:
> > >
> > > LivingRoom is a tablet pc that a friend was using for work - ie. it got real
> > > cluttered but the machine was completly functional, def the wirelss aspect.
> > > So I reformated it and installed a fresh copy of XP Pro (that's why the time
> > > is off. I haven't cleaned it up yet, it's brand new). Since it's a tablet pc
> > > there were a bunch of funky drivers that it requires (for touch control and
> > > other compact hardware).
> > >
> > > After I installed all the dirvers (recommended by the manufacturer, one of
> > > them still seemed not to work) - the wireless adapter. Whenever I try to
> > > configure it with the Realtek software provided w/ the dirver (via the link
> > > below) I get "No Wireless Network Adapter Found". I know it worked prior to
> > > my reinstall of XP but I can't get it to work now. The manufacturer will not
> > > respond to me beyond thier "here try this" link to a .zip file, supposidly
> > > containing all the drivers for this particular issue. It obviously is lacking
> > > one. This is the file they say should have fixed this...
> > >
> > > http://www.tabletkiosk.com/support/files/Sahara_SDV-T01/Wireless.zip
> > >
> > > In device manager under Network Adapters I have 1339 & Realtek 8139, then
> > > Other Devices has a "?" as well as it's subcategory Network Contorler has a
> > > "?".
> > >
> > > I didn't think this was going to be a problem because it was going to be a
> > > stationary computer and I could connect w/ a cat5, however based on your last
> > > response I see it is an issue.
> > >
> > > Is there a way to find out exactly which wireless network adapter I have?
> > > There is a folder in that zip file titled "802MR-W". I think that's it but I
> > > do not see a setup.exe for it. I assume that its what is showing up as Other
> > > Devices and therefore has no driver. am I correct?
> > >
> > >
> > >
> > > "Pegasus (MVP)" wrote:
> > > > Sorry for the mistake in the telnet command. It seems you
> > > > compensated for it quite nicely.
> > >
> > > > Yes, respondent "smlunatick" is correct: When using
> > > > Remote Desktop then you must use an account on that
> > > > host machine that has a non-blank passwords. However,
> > > > you're not at that stage just yet.
> > >
> > > > Your tests prove these points:
> > > > - Your network appears to be working. Both machines
> > > > can set test packets to an external site.
> > > > - The Office machine can exchange test packets with the
> > > > LivingRoom machine.
> > > > - The LivingRoom machine cannot exchange test packets
> > > > with the Office machine.
> > >
> > > > I can think of these reasons why this would happen. I'm
> > > > ignoring here what you wrote in your previous notes:
> > > > a) The Windows firewall on Office is active.
> > > > b) There is a third-party firewall active or installed on Office.
> > > > c) The IP address of Office is something other than 192.168.1.20.
> > > > d) The network adapter of Office is flawed (unlikely but possible).
> > > > e) The network switch port used by the Office machine is
> > > > flawed (unlikely but possible).
> > > > f) The network switch (or router) is in a funny mode. Rebooting
> > > > it would probably fix it.
> > >
> > > > Why not try it in reverse? Enable Remote Desktop on Living
> > > > Room, then type this command on Office: mstsc /v:LivingRoom
> > >
> > > > "David L." <Dav...@discussions.microsoft.com> wrote in message
> > > >news:A0803A17-0E7C-4F81-B690-9AEA11B15949@microsoft.com...
> > > > > Sorry for the delay. work sent me on a day trip around the world (or at
> > > > > least
> > > > > close to it). It sucked. Anyway... thanks for the help and here is the
> > > > > data
> > > > > you requested. Also, regarding the other person that mentioned about the
> > > > > username and passwords, LivingRoom does not have a password - should it?
> > >
> > > > > *******************************
> > > > > Office Data Below
> > > > > *******************************
> > > > > Pinging 192.168.1.21 with 32 bytes of data:
> > > > > Reply from 192.168.1.21: bytes=32 time=5ms TTL=128
> > > > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > > > > Reply from 192.168.1.21: bytes=32 time=1261ms TTL=128
> > > > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > >
> > > > > Ping statistics for 192.168.1.21:
> > > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > > > Approximate round trip times in milli-seconds:
> > > > > Minimum = 2ms, Maximum = 1261ms, Average = 317ms
> > >
> > > > > Pinging LivingRoom [192.168.1.21] with 32 bytes of data:
> > > > > Reply from 192.168.1.21: bytes=32 time=1ms TTL=128
> > > > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > > > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > > > > Reply from 192.168.1.21: bytes=32 time=2ms TTL=128
> > >
> > > > > Ping statistics for 192.168.1.21:
> > > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > > > Approximate round trip times in milli-seconds:
> > > > > Minimum = 1ms, Maximum = 2ms, Average = 1ms
> > >
> > > > > Pinging 64.233.183.104 with 32 bytes of data:
> > > > > Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
> > > > > Reply from 64.233.183.104: bytes=32 time=133ms TTL=231
> > > > > Reply from 64.233.183.104: bytes=32 time=137ms TTL=231
> > > > > Reply from 64.233.183.104: bytes=32 time=132ms TTL=231
> > >
> > > > > Ping statistics for 64.233.183.104:
> > > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > > > Approximate round trip times in milli-seconds:
> > > > > Minimum = 132ms, Maximum = 137ms, Average = 133ms
> > > > > TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
> > > > > Port# in ..\RDP-Tcp\PortNumber = 3389
> > >
> > > > > *******************************
> > > > > LivingRoom Data Below
> > > > > *******************************
> > > > > Pinging 192.168.1.20 with 32 bytes of data:
> > > > > Request timed out.
> > > > > Request timed out.
> > > > > Request timed out.
> > > > > Request timed out.
> > >
> > > > > Ping statistics for 192.168.1.20:
> > > > > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> > > > > Ping request could not find host Office. Please check the name and try
> > > > > again.
> > >
> > > > > Pinging 64.233.183.104 with 32 bytes of data:
> > > > > Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
> > > > > Reply from 64.233.183.104: bytes=32 time=134ms TTL=231
> > > > > Reply from 64.233.183.104: bytes=32 time=148ms TTL=231
> > > > > Reply from 64.233.183.104: bytes=32 time=138ms TTL=231
> > >
> > > > > Ping statistics for 64.233.183.104:
> > > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > > > Approximate round trip times in milli-seconds:
> > > > > Minimum = 134ms, Maximum = 148ms, Average = 138ms
> > >
> > > > > \\When I ran the next telnet command as you gave it to me I kept getting a
> > > > > syntax error. So I ran it as below and typed in the results (instead of
> > > > > having them write to the test.txt file), is was://
> > > > > \\Command:telnet 192.168.1.20 3389
> > > > > Connecting to 192.168.1.20...Could not open connection to the host, on
> > > > > port
> > > > > 3389: Connect failed.
> > >
> > > > > "Pegasus (MVP)" wrote:
> > >
> > > > >> It does not make much sense having one machine on DHCP
> > > > >> and the other on a fixed IP address. I suggest you turn off
> > > > >> DHCP on both machines and assign the following addresses:
> > >
> > > > >> Office 192.168.1.20
> > > > >> LivingRoom 192.168.1.21
> > >
> > > > >> I recommand that you set the DSN addreses like so
> > > > >> on both machines:
> > > > >> Primary 192.168.1.1
> > > > >> Others 72.45.32.34, 72.45.32.37
> > >
> > > > >> After doing this, execute the following commands on Office
> > > > >> and post the result file:
> > > > >> ping 192.168.1.21 > c:\test.txt
> > > > >> ping LivingRoom >> c:\test.txt
> > > > >> ping 64.233.183.104 >> c:\test.txt
> > > > >> netstat -an | find "3389" >> test.txt
> > > > >> Please do not omit the third command this time!
> > >
> > > > >> On LivingRoom I would like you to run these commands:
> > > > >> ping 192.168.1.20 > c:\test.txt
> > > > >> ping Office >> c:\test.txt
> > > > >> ping 64.233.183.104 >> c:\test.txt
> > > > >> telnet 192.168.1.20 3389 >> 1c:\test.txt 2>>&1
> > >
> > > > >> Lastly I would like you to report the port number at this registry
> > > > >> location on Office:
> > > > >> HKLM\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\Po-rtNumber
> > >
> > > > >> "David L." <Dav...@discussions.microsoft.com> wrote in message
> > > > >>news:840E2823-C8EF-407F-B194-831C8D9326C3@microsoft.com...
> > > > >> >I do not have Zone Alarm, I'm only using the windows firewall software
> > > > >> >as
> > > > >> >of
> > > > >> > now.
> > >
> > > > >> > Here are the IP address details for both comps...
> > >
> > > > >> > *************************************
> > > > >> > 1st Computer Below (Desired Host)
> > > > >> > *************************************
> > >
> > > > >> > Windows IP Configuration
> > > > >> > Host Name . . . . . . . . . . . . : Office
> > > > >> > Primary Dns Suffix . . . . . . . :
> > > > >> > Node Type . . . . . . . . . . . . : Unknown
> > > > >> > IP Routing Enabled. . . . . . . . : Yes
> > > > >> > WINS Proxy Enabled. . . . . . . . : Yes
> > >
> > > > >> > Ethernet adapter Wireless Network Connection 2:
> > > > >> > Connection-specific DNS Suffix . :
> > > > >> > Description . . . . . . . . . . . : Linksys Wireless-G PCI
> > > > >> > Adapter
> > > > >> > Physical Address. . . . . . . . . : 00-18-39-14-D6-0A
> > > > >> > Dhcp Enabled. . . . . . . . . . . : No
> > > > >> > IP Address. . . . . . . . . . . . : 192.168.1.20
> > > > >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > > >> > Default Gateway . . . . . . . . . : 192.168.1.1
> > > > >> > DNS Servers . . . . . . . . . . . : 72.45.32.34
> > > > >> > 72.45.32.37
> > >
> > > > >> > *************************************
> > > > >> > 2nd Computer Below (Desired Client)
> > > > >> > *************************************
> > > > >> > Windows IP Configuration
> > > > >> > Host Name . . . . . . . . . . . . : LivingRoom
> > > > >> > Primary Dns Suffix . . . . . . . :
> > > > >> > Node Type . . . . . . . . . . . . : Unknown
> > > > >> > IP Routing Enabled. . . . . . . . : No
> > > > >> > WINS Proxy Enabled. . . . . . . . : No
> > > > >> > DNS Suffix Search List. . . . . . : the-beach.net
> > >
> > > > >> > Ethernet adapter Local Area Connection 2:
> > > > >> > Connection-specific DNS Suffix . : the-beach.net
> > > > >> > Description . . . . . . . . . . . : Realtek RTL8139 Family PCI
> > > > >> > Fast
> > > > >> > Ethernet NIC
> > > > >> > Physical Address. . . . . . . . . : 00-0C-6F-00-0B-3D
> > > > >> > Dhcp Enabled. . . . . . . . . . . : Yes
> > > > >> > Autoconfiguration
> > >
> > > ...
> > >
> > > read more >>- Hide quoted text -
> > >
> > > - Show quoted text -

> >
> > Did ou re-install the motherboard chipset driver for the tablet?
> >
 
Back
Top