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?
:
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
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.
:
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
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 -
