Re: Big problem with Vista clients

I think that as we have an improvement it may indeed be worth doing the IP reset thing again. It's probably not necessary, but... belt and braces.

The problem with not remembering what was done concerning policy is that rather than disabling the policy we may need to disable (rather than 'not configure') the specific policy element, and re-enable the policy to make the change come into effect.

Next time Mike, TAKE NOTES.

I consider myself a bit of a cowboy but most of the servers I look after have an 'excercise book' (and pen!!!) attached by a piece of string. Before making such change the original setting is recorded in the book, with date and time. I do however have to admit that such books are now somewhat ignored due to my implementation of changes via remote access (can't reach the book from here :-) so I rely on my calendar to record such change. (calendar item topic 'system change - servername', original setting, new setting, purpose. This allows me to track changes to all systems/components.)

--
SBS remote support services. (Fees apply)
mickm at mickmalloy dot dyndns dot org

"Mike_in_Nebraska" <mike_webb@xxxxxxxxxxxxxxxxx> wrote in message news:bce2fde6-19ad-4ece-a491-4320670d0e94@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
OK, I'm back. Had the PC off for a bit over 5 minutes after following
your instructions. It worked! I got an IP and the domain options.
However, I still see a red X between the server and the Internet in
Network and Sharing Center. I still can't use Windows Mail, and
Outlook 2007 won't or can't connect. While I was waiting, I went
around to the other Vista machines that are on and saw that all are
experiencing the same problems as mine. The boss's laptop, running XP
Pro SP3, is doing just fine. All I had to do to his was manually
input the name of the server in the Firewall Client. For whatever
reason it's not picking it up automatically -- and neither are anyone
elses.

To answer your questions .... DHCP comes from the server, not my
router.

I did the TCP/IP and Winsock rebuilds last night; no change. I can
try again, if you think it'd work now that I have an IP.

I don't remember what I did in GPMC; however, remember that I reset my
GP's to the default settings either late last night or early today,
and disabled all GP's that directly or might possibly affect Vista.
Did a gpupdate /force all around with reboots, no change. Even went
so far as to reset my Local Security Policy to the installation
defaults. No change. So that is probably a moot point.

Mike

.

Relevant Pages

  • Re: How to allow users to create groups and shares
    ... Add the user/group to the Computer configuration, windows settings, security settings, Local policies, "Allow logon locally" in the Default domain controllers policy and on a existing or new created policy for the member servers. ... Filtering: Not Applied ... check with GPMC on the server or from a client the policy settings. ...
    (microsoft.public.windows.server.active_directory)
  • Domain Controller Security Policy errors
    ... Security Policy or the Domain Controller Security Policy. ... The DC is also a print and file server. ... The domain controller for Group Policy operations is not available. ...
    (microsoft.public.win2000.active_directory)
  • RE: Cant set Local Security policies. They fail to save
    ... predefined Security Template on SBS 2003 to restore security groups ... run "gpupdate.exe /force" under command prompt to force the policy ... reboot the Server to test. ... and then logon to client computer to test if user can save system logs. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant access companyweb or other website on IIS after installi
    ... Let's re-run CEICW to reset the network configuration. ... How to configure Internet access in Windows Small Business Server 2003 ... suggest you try it again and reset all the settings. ... Install MBExplorer by installing IIS 6 Resource Kit Tools: ...
    (microsoft.public.windows.server.sbs)
  • Re: Security Logon/Logoff Events
    ... I haven't yet set password policy or configured account lockout policy so I ... will do that in due course to fully secure the server. ...
    (microsoft.public.windows.server.sbs)