MikeTackett 16 Newbie Poster

Was gone for a few days. First question would (and I'm sure you've done it lots) is to check the IP of your router. If you can get to 192.168.0.1 from XP wired you should definitely be able to do it from ubuntu wired. Also check the wired connection on ubuntu overall. Again, if you can get to the 'net wired on ubuntu, we've eliminated the NIC/drivers.
I'm speculating your router uses a web interface to configure it. Check what protocol it's using (is it regular, HTTP or HTTPS). If it's the latter, be sure you can access HTTPS on ubuntu. Just to clarify, are you able to get to the router wirelessly on ubuntu? What about XP?

MikeTackett 16 Newbie Poster

It's likely your router already has what you need to get these devices connected. The router is probably also your DHCP server, if you can connect both computers to the router and get to the internet with both, you're basically good to go with connectivity. Do you have anything else that's going on the network, like a printer?

In terms of file sharing, I follow the school of thought to have a central point of file storage that both computers can access as opposed to constantly connecting to various points between the two. You will want to designate some space on either your windows or linux box for this. I know software exists to get linux to read/write NTFS (assuming you're using NTFS), however I don't know what's available for Windows to read linux file systems. This might influence your decision there. You can basically make a Windows share and have ubuntu mount that. Someone more versed in linux (I've limited use of it, not even running it anywhere right now) should be able to help you there, I'll dig something up either way.

I've never used Synergy but it appears to be something different that just VNC software. It actually sounds pretty interesting, I'm going to check that out sometime.

jingda commented: Nice one +5
MikeTackett 16 Newbie Poster

I consider myself still a novice programmer but I'm starting to develop and maintain applications with end users for the company I'm working for. We don't have a policy on version numbers and I'm looking for advice on when best to update them. I understand the major.minor portion is largely a judgment call. Am I right that "build" is increased every time a working build is made during development and "hotfix' is used when ever a hotfix or patch is rolled out?

Where I'm at, they seem to only really update the hotfix portion regardless of when the software is updated, we're talking v1.0.0.258 or v 1.0.1.98
I don't like this methodology especially since we have scheduled service pack dates of once a month, and have made somewhat drastic changes to the functionality and interfaces of some software yet, everything is still at version 1.0.x.x.

Anyone care to share any thoughts on how they update their version numbers or what is an advisable method?

kvprajapati commented: Good question indeed. +11