Somehow, I thought this would be easier!
There is a Windows XP SP1 computer at the front of our church. It holds songs, karaoke, Powerpoints, etc. We're trying to find a way for someone to control that machine in the back of the church as now, our music director and pastor have to use a wireless presenter to advance slides, choose the next songs, close it down, etc.
I bought a cheap computer with the intent of installing Ubuntu for the sole purpose of controlling the Windows machine. That's it. We bought a 100ft Cat5e patch cable (because I had heard that operating systems now don't care if it's patch or crossover as much as they used to) and hooked up both machines to the same cable as we do not have internet. I had seen two computers hooked up similarly in another office (but they were both using XP), so I thought it wouldn't be too bad.
I tried to set the Windows machine's IP address to 192.168.254.2 and the Ubuntu computer's IP address to 192.168.254.3. Both have a subnet mask of 255.255.255.0 and a gateway of 192.168.254.1.
I installed the tightVNC client on the Windows machine thinking that this would be the best way to handle it. Ubuntu comes with Xvncviewer installed, so I planned to use that.
However, I can't get the two to connect. For my questions:
1. Do I need crossover cable? If so, I saw an adapter that essentially does the same thing as I don't want to run another cable through the roof of our church.
2. How do I get the Windows machine's local area connection to accept that it's 192.168.254.2? The closest I could get was to get the network bridge to have that address, but the local area connection never would acknowledge that a cable was plugged in.
3. Is there an easier way than what I'm thinking?
Ultimately, all I want is for me to be able to see the Windows machine on the Linux desktop so that I can control the powerpoint slides, music, etc. However, I want to still give them the opportunity to use the presenter and still have full control over the Windows machine from the front of the church. Wireless wasn't as effective as we'd hoped. That's why I went the remote desktop route.
Any help will be appreciated! Thanks!