Tricks

Sorry if this has already been asked, but will there be a limit on how far into the future rooms will be bookable?

According to SWGfL their router is configured to allow traffic between new and old subnets. Sure I tested this yesterday but today does seem to work fine.

What should I be looking for to configure our central switch to do this? We have a D-Link DXS-3350SR Layer 3 switch. EDIT: Looking in the manual it looks like IP Multinetting, Static/Default Route Settings and IP Interface Settings may be what I need but want to fully understand it before touching anything.

How are you configuring the network to get the two subnets talking? Probably like you, I just want to get it working as a flat network to extend the number of IP's available nothing overly complicated. If I setup a PC that bridged the two networks that would seem a bit of a bottleneck? must be a better way

Hello, We'd requested more IP's from SWGfL and have been allocated another block but it's not consecutive with our existing range. I have doubts in how to best set this up and was hoping for some advice. Basically we currently have 10.4.x.0/22, 255.255.252.0 and now also have 10.4.y.0/22, 255.255.252.0. What would be the best way to set this up? A) Treat as one big range and just set our DHCP server to only dish out the ranges we have? B) Setup separately and route traffic? C) ? PS. Our router is SWGfL supplied Cisco jobby and they have remotely configured the new range on the same port as our existing range. Thanks guys

Thanks for the updates Oz, is the new release available?

I'm a bit stumped at the moment, going to need another occurrence to test with. You may well be right about my assumption, but given the mixture of hardware (and age) I've seen this happen with I find it hard to believe it's simply hardware failure.

I'm 99% sure it's doing the repair by default - just changing that default would help. I am of course assuming that whatever crash happened it would still boot if you changed the boot menu to normal start up.

I don't know at the moment - I've hunted event logs but not found anything. Unfortunately I've only every found it in hindsight so don't know what time it happens.

Has anyone found Windows 7 automatically doing a System Repair a pain? I seem to regularly have machines, for whatever reason, crash and reboot straight into System Repair which after it's finished as rolled the machine back to a pre-configure state - i.e. has it's old computer name, missing Win updates and AD doesn't recognise the machine so people can't login. It's getting rather frustrating, apparently you can do this to disable it; bcdedit /set {default} bootstatuspolicy ignoreallfailures Disable Windows Startup Repair as Default Option - Windows 7 Forums Has anyone had to overcome this? I'm wary of just disabling it, not just the practicalities of getting round all the machines but incase I actually need system restore.

Well not all that surprised I had no replies given it made no real sense. I have got them working now by disabling Offline Files and Transparent caching - surprising how often that fixes problems that make no sense Still doesn't explain why it was only this specific set of Lenovo laptops that were affected though, we have several laptop trollies and staff laptops as well.

I have a problem I can't make sense of - hoping some bright spark might suggest some things I could try. I found the problem due to users of some Lenovo Windows 7 netbooks finding they didn't have the the right desktop/start menu shortcuts and home drive, while mapped, gave access denied. As far as I'm aware this is an isolated problem with these Lenovo set of netbooks. I'd say over half have this problem, and seem to do it quite consistently - some are fine however. Here's what I've found; - Logging in as local admin and open \\server\home$ (location of our redirected folders) I get access denied. I can however access admin shares on the server (c$ etc) (n.b 'everyone' has read access to home$) - Removed one from the domain, still had the same issue. - Rejoined to domain in Computers OU, confirmed via gpresult but still same. - Hunted through event log on client and other than the folder redirection failures I couldn't see anything useful. Is it possible for the server to black list the computer somehow? I can't think what else it could be.

Thanks for the update altonPM. We've not had this deleting issue yet but am all to wary of doing something that triggers it. I havn't used the %HOMESHARE% variable in our profiles paths which may be why.

Fixed by a mass 'Discovery Data Collection Cycle' as it turned out. Still got that Dundas Chart problem though.