Re: Authentication Issues with Vista Clients

After a lot of troubleshooting, I've finally gotten it straightened out! On
Sunday afternoon, I decided to go down there and try placing the network on a
different subnet. Well, I changed everything over from the 192.168.2.0/24
subnet to the 192.168.3.0/27 subnet. After doing that, I re-ran the CEICW
wizard. I cleaned out all the old DNS and WINS references to all the
computers. I had to manually create a new DHCP scope (thought CEICW would
have done it for me, guess not). Whatever the problem was, that seemed to
have fixed it. However, that wasn't all.

On early Tuesday morning, for some reason, ISA just decided it wanted to
stop working all together. The Firewall Service and the MSFW database
wouldn't start at all. Windows would come back and say something about how
the service started, but stopped...and how some services do that if they have
no work to do. The funny thing was that there were absolutely no errors at
all in the Event Viewer. I tried re-running the CEICW wizard and repairing
the install of ISA, but I ended up having to completely reinstall ISA. So, I
spent my Tuesday morning doing that. Since then, everything has been great.

Regarding the Windows Search in Vista...for some reason, whenever I first
upgraded them to Vista, they had real performance issues. I narrowed it down
to Windows Defender and the Windows Search. Windows Defender was interfering
with NOD32 and causing the disk to thrash constantly. Disabling Defender
isn't that big of a deal because NOD32 scans for spyware.

The drive was still doing a bit of trashing, although, it wasn't so bad. I
was still receiving complaints about performance. The next step was to
disable Windows Search, and that seemed to do it. I'm not sure why it was
causing the drive to thrash, but this was even a couple weeks after Vista was
installed. There aren't too many files that are stored on individual PCs, as
pretty much everything is kept on Sharepoint. So, I don't think it will be
too much of an issue.

I've done memory upgrades on two of the three PCs that run Vista...upgraded
them from 512MB to 2GB. The third one already had 1GB...these are Dell
machines that were purchased back in 2002-2003, so they've been around for
quite awhile. I think the next step would be to upgrade the hard drives, but
they're running pretty good with the extra memory.

Thanks for your help, Kerry.

"Kerry Brown" wrote:

"Eddie" <Eddie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7AE59EE3-4872-412A-A4A1-7929F0880067@xxxxxxxxxxxxxxxx
As far as I know, everything is configured correctly on the Vista clients.
I
have left everything configured as it was out of the box, except I have
disabled IPv6 and a few un-needed services, such Security Center, Tablet
PC
Input Service, UPnP Device Host, and Windows Search.

In the connection details of the clients, it has the correct WINS server
listed. I've had a look at the WINS console on the server, and it seems as
if
everything is up to date and listed properly. None of the computers have
any
issue accessing file or printer shares. However, I have noticed that the
Vista clients aren't registering themselves in the reverse DNS zone. The
XP
client, the SBS box, and another server are registering themselves just
fine.
I've noticed that exact same thing happening on my home network, in which
I
also use SBS. The Vista clients never seem to register in the reverse DNS,
so
I don't know if that would be an issue or not.

Actually, from what I'm seeing now, ALL the users are experiencing the
password prompts on \\companyweb. I thought about trying to access
\\companyweb from both the SBS box and the secondary server that we have.
Trying to access it from the SBS box also yields the password prompt.
Trying
to access it from the secondary server brings up yet another message, but
not
a password prompt. It says: "You were not connected because a duplicate
name
exists on the network. Go to the System in Control Panel to change the
computer name and try again."

So, currently, there is only one computer on the network, the XP box, that
doesn't have this issue. I'd say just give it some time, and it'll start
doing it like the other ones. At least that narrows it down to not being a
Vista or user specific issue. The message that the secondary server showed
me
definitely points me down the road of DNS issues, but what could it be? I
don't see any duplicate entries listed, and I don't have a computer on the
network named "companyweb."


Check the DNS settings on the server TCP/IP properties. Check both NICs if
you use two. On a SBS server both NICs should be using only the SBS server
itself for DNS. Check the second server as well. With AD and particularly
with SBS it is very important that everything on the network use only the
SBS server for DNS. I don't know if this is the issue though. Re-reading
your posts it sounds like it could be a permissions issue or firewall issue
somewhere.

You're not doing yourself a favour by disabling services in Vista. At least
during troubleshooting you want Vista running in it's default state. In my
exhaustive testing of Vista I haven't found any real performance gains in
disabling any of the default services. Disabling Windows Search disables the
best feature in Vista. If you have users that use Vista at home and get used
to using the Start Search box you will get a lot of complaints if it's not
working. It does impact performance on a new installation while the index is
being built. I usually leave a new system on overnight with all the sleep
functions turned off. This gives it time to build the index and the
performance hit is not noticeable after that. If you notice a performance
hit from the default services in Vista the pc is not really up to running
Vista and nothing you can do other than a hardware upgrade will make it run
Vista well.

--
Kerry Brown
Microsoft MVP - Shell/User
http://www.vistahelp.ca


.

Relevant Pages

  • Re: Problem with Vista 64bit client accessing files on SBS 2003 share
    ... Cris Hanna [SBS - MVP] wrote: ... I think my approach would be flatten it...rejoin to the domain immediately, Apply Vista SP1 if not included. ... Windows Small Business Server 2008 Unleashed ... believe its not a general network issue. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem with Vista 64bit client accessing files on SBS 2003 share
    ... Cris Hanna [SBS - MVP] wrote: ... I think my approach would be flatten it...rejoin to the domain immediately, Apply Vista SP1 if not included. ... Windows Small Business Server 2008 Unleashed ... believe its not a general network issue. ...
    (microsoft.public.windows.server.sbs)
  • Re: Help me add a client from remote with SBS 2003
    ... When you are the person primarily responsible for a network that involves SBS, this is by all means the place to try and get questions answered. ... much tougher in the long term to do that support when you don't have first hand knowledge of the network and little to no experience with SBS. ... You are not going to get remote access to this machine (Vista or XP) via RDP or RWW until it's joined to the domain, using the steps that Larry provided. ... Server), and we actually had an Old W2k3 Server ...
    (microsoft.public.windows.server.sbs)
  • RE: Vista unable to logon with RDP in Remote Web Workplace
    ... Do all Vista workstation have such issue? ... Can you see any error messages when connecting to server desktop? ... Logon a Windows XP computer, visit RWW, can you connect the SBS ... When trying to connect to a terminal server from Windows Vista, ...
    (microsoft.public.windows.server.sbs)
  • Re: Server/Network setup question
    ... Let's keep the P2P network and the ... SBS server's internal NIC to the switch. ... The internal NIC of the SBS server will default to 192.168.16.2 during the ... you change the IP of the rented printer to 192.168.16.8 (or some ...
    (microsoft.public.windows.server.sbs)