indie Posted January 16, 2006 Posted January 16, 2006 So what interesting "features" have you found with LNM? The first one I have found is during setup where it want's me to specify IP addresses for the DHCP scope. I just ran the installer on a spare machine to see what it's like, I left it with the defult DHCP settings it came up with: Start IP: 192.168.0.50 End IP: 192.168.0.254 Then when I press next it says that the End IP must be higher than the Start IP! Changed the Start to 192.168.0.10 and the end to 192.168.0.200 and it works, maybe it's only validating the IP address by the 1st digit in the fourth octet?
russdev Posted January 16, 2006 Posted January 16, 2006 lol on serious note if we do found things i think it is worth us feeding it back to ms via our contact... what you think tony? russ
TechMonkey Posted January 16, 2006 Posted January 16, 2006 So what interesting "features" have you found with LNM? The first one I have found is during setup where it want's me to specify IP addresses for the DHCP scope. I just ran the installer on a spare machine to see what it's like, I left it with the defult DHCP settings it came up with: Start IP: 192.168.0.50 End IP: 192.168.0.254 Then when I press next it says that the End IP must be higher than the Start IP! Changed the Start to 192.168.0.10 and the end to 192.168.0.200 and it works, maybe it's only validating the IP address by the 1st digit in the fourth octet? Could it actually be validating the final 50 as 500, so the 50 should 050? Being overly clever, or overly stupid.
ajbritton Posted January 16, 2006 Posted January 16, 2006 Possibly its doing an ASCII compare. "50" is > "254" whereas "10" < "200".
Ric_ Posted January 16, 2006 Posted January 16, 2006 I spotted that - went "oh!" and duly changed the range to 10.0.0.50 -> 10.0.0.99 It's the bloody message at the end that's pissing me off!
wesleyw Posted January 16, 2006 Posted January 16, 2006 I can actually believe MS would do that (Probably without the cult phrase all your base are belong to us lol)
_Rob_ Posted January 22, 2006 Posted January 22, 2006 Yeah, we had an issue with the IP settings, it didn't like our subnet mask of 255.255.252.0!
petectid Posted January 30, 2006 Posted January 30, 2006 Yeah, we had an issue with the IP settings, it didn't like our subnet mask of 255.255.252.0! I found this Rob I could only get it to use a 24 bit subnet, would not recognise our 22 bit mask, like yours.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now