Jump to content

GrahamCT

Members
  • Posts

    3
  • Joined

  • Last visited

Reputation

0 Neutral

About GrahamCT

Personal Information

  • Occupation
    Computer Engineer
  1. Ahh yes! Change permissions on the share was the fix. Once this was added the fault vanished. Cheers Lafleur1977.
  2. I'm getting this exact fault too at one of our sites. We've got redirected start menus/desktops with Win7 at numerous sites but this one seems to be the only one with this problem so think it's more of a peculiar quirk rather than a Win7/redirected start menus fault. On first login all shortcuts are fine from the redirected start menu but on second login those in the root (\\servername\share$\startmenu\programs\) are inactive as you say. Not able to launch or even right click. We've also found programs within folders (for example \\servername\share$\startmenu\programs\MS Office) are fine. If we delete the locally cached profile then the start menu will be fine on the next login but on subsequent logins the fault returns. Also found that on second logins (and beyond) the search programs bar from the start menu doesn't find any programs whist it does on first login. I don't think this is a security fault because if I create a shortcut on the users desktop to the redirected start menu they are able to launch all shortcuts perfectly. Something must be changing in the local profile from 1st to 2nd login which breaks this part of the start menu. :-/
  3. Hi there, I'm trying to install a managed Wireless LAN using a HP Wireless Edge services module. I've VLAN'd all the switches, APs all adopted and created security profiles that work using a WPA key and also using the web authentication with the inbuilt RADIUS server to authenticate. But what I'd really like to do is authenticate the users via Active Directory on our Server 2008 DC. Going through the manual this definitely looks possible and I've configured all the LDAP server details (pointing to the DC) but I keep getting incorrect password error when when trying to log on. I've made sure the user i'm testing with is a member of a group that exists on the local RADIUS server and in AD. What I'm not sure about is whether the wireless module can natively bind to AD or whether you need something inbetween due to the encryption? Looking at HP's documentation it appears as if the encryption needs to be either ttls and Pap or peap and Gtc. Any help/suggestions greatly appreciated.
×
×
  • Create New...