Since I'm trying to basically use the 300GL as a dumb computer for internet related tasks, I tried using my intellistation to take over with remote desktop. The only problem is, it won't work. Windows 7 just gives me a stupid nonsensical stock message like "check to see if you are connected" (of course it's connected!)
I can look into the 300GL's network folder and all that, and see any changes dynamically.
At the moment I don't have a spare router, so, I have the intellistation directly hooked into one of the 300GL's ethernet ports, and the other port going into the modem, so it works like this (excuse the bad diagram, I only have paint on the 300GL and no other fancy gfx apps):
Show Image
(http://geekhack.org/attachment.php?attachmentid=12222)
The 300GL's two ethernet ports have one going into the intellistation, and another into the router -- both ethernet ports are good and working.
The green arrows represent that after the intellistation takes over the 300GL with remote desktop, it can then have pseudo-access to the internet by manipulation of the 300GL.
My question is, is remote desktop not working because I'd need a router for dynamic DHCP addressing?
(300GL is running on XP, intellistation is of course on Windows 7).
EDIT:
why would I want to do this?
#1 good stop for viruses (and don't have to muck up my windows install with junk from websites -- I don't go on anything bad, but sometimes other people -- like my dad -- help themselves to going on my intellistation).
#2 gives me a reason to use the 300GL
#3 I can leave stuff download all night on the 300GL while being able to turn off the intellistation.
If there's anything better than bill gates' remote desktop, let me know.
Well, you've got a few issues to deal with. First on the physical layer. As Kishy said, depending on the NICs, you may need a crossover cable to get a link, check for a link light for that bit. Also you will need some form of port forwarding to move the traffic from one interface to the other on the 300GL, like Internet Connection Sharing. And as the NICs won't be getting DHCP assignments from the router in this scenario, you'll need to either statically set them up to a common subnet or do it via your port forwarding software such as you can do with ICS.
If you have a physical connection and have IPs assigned on the same subnet, then check to make sure that RDP is listening. Open a command line window and to a "netstat -a". RDP should be listening on port 3389. If you don't see it, try "netstat -an". It may only be listening on the primary port set as the default route, not sure. If you're running XP on the 300GL then per KB 924927 by default Microsoft Windows XP Remote Desktop and Terminal Services use all available network interfaces to listen for Remote Desktop Protocol (RDP) requests. If you're running something else, you'll have to check. If RDP is listening then is probably either no link or lack of proper IP configuration with the NICs on a common unique subnet.
Actually. Do you need ICS? Perhaps not. Let's see. If you get a link, configure the IPs & same unique private subnet between the two boxes, then you should be able to launch a remote desktop on the 300GL. Once you do that, everything but your unique private subnet between the PCs (an RFC1918 compliant subnet like 192.168.x.x or 10.x.x.x that is different that your router subnet) should go to the default gateway connected to the router. So perhaps you don't need ICS. You certainly would if RDP wasn't in the mix, but maybe not with it.
If you have a spare port on the router it would be much simpler to just plug into that, RDP to the 300GL and out to the Internet from there, then all of these problems go away. So something like this, also quick & dirty.
(http://geekhack.org/attachment.php?attachmentid=12226)