I've been using VB since 2012 (and squeezeboxen/LMS for a long time before that). A few months back, I bit the bullet and rebuilt my system to VB 2.5 - my Linux "skills" are somewhat rudimentary, but after a few false starts and blind alleys, my system is up and running (although not without a few oddities, of which I may post later).
After a few weeks of running 2.5 happily, the allocated IP address seemed to change for no apparent reason (from 192.168.1.95 to 192.168.1.somethingelse). That screwed up the mapping of my fileshares on Windows, so I tried to re-assign 192.168.1.95, but somehow have ended up with the VB on 192.168.2.228. I'm not even sure I was aware I could allocate anything to the 192.168.2.subnet, but it's stuck there and I'm not sure how to get it back. Any ideas?
After a few weeks of running 2.5 happily, the allocated IP address seemed to change for no apparent reason (from 192.168.1.95 to 192.168.1.somethingelse). That screwed up the mapping of my fileshares on Windows, so I tried to re-assign 192.168.1.95, but somehow have ended up with the VB on 192.168.2.228. I'm not even sure I was aware I could allocate anything to the 192.168.2.subnet, but it's stuck there and I'm not sure how to get it back. Any ideas?
Comment