Re: Win 98 Client Support

From: Shawn (anonymous_at_discussions.microsoft.com)
Date: 03/01/04 

Date: Mon, 1 Mar 2004 10:30:02 -0800

Hi Robin

I'm almost afraid to say it, but watch out for Win98
clients on a SBS2003 network. I have had 2 sites where a
Windows 98 client experiences logon problems, and
intermittently drops off the network. If you check the
security event logs, there are logs saying there were
account lockouts, but there arent any locked out
accounts. The Win98 client will tell you to check
passwords, and you logon has been denied, but doing all
that doesnt solve the problem. Eventually, you'll get the
workstation abck on, then it will be kicked off the net
again. When we initally installed the server, all was fin
on that day, but after the weekend, the network got busy,
then the problems began. We've found a solution to the
problem, but I'm not sure if you will experience the same
problems.

regards
shawn

>-----Original Message-----
>Thanks Ken - sounds as I expected - but I am always wary
of gotchas that get
>you part way through the roll out !!!
>
>Regards
>
>Robin
>
>
>"MCSE_in_PA" <anonymous@discussions.microsoft.com> wrote
in message
>news:AA4ACE1B-F1F0-4FF3-96BA-
1CF9079C4049@microsoft.com...
>> Hi Robin
>>
>> Windows 98SE workstations will work in the SBS2003.
As you noted, you
>will need to manually change the network settings to
access the domain. And
>as I am sure you are aware, security within Windows 98
is mostly
>non-existent. You will want to be sure to install all
Windows Updates.
>>
>> That said, we have several clients that still have
some Windows 98SE
>clients. Updating to Windows XP Pro is not feasible due
to the processor
>and memory requirements.
>>
>> Under Network Neighborhood, be sure the DNS is set to
the SBS Server's IP
>address only. And in "Client for Microsoft Networks, be
sure to check the
>"Log in to NT Domain" and enter the domain name.
>>
>> Regards,
>> Ken Saxe
>> MCSE_in_PA
>> (NO.SPAM.ksaxe@juno.com - remove NO.SPAM. to send
email)
>
>
>.
>

Relevant Pages

  • GPO: User to change TCP/IP settings:
    ... Server: Windows 2003 Standard ... Clients: Windows 2000 SP4 ... GPOs set. ... Administrative Templates -> Network -> Network Connections) there are a ...
    (microsoft.public.win2000.active_directory)
  • printing across network using multifunction printer psc1315
    ... Printing to the HP PSC1315 across a network having windows xp, ... Printing with linux client to linux server and windows xp to windows xp ... With the win98 clients, this was all that was required. ...
    (comp.os.linux.networking)
  • Re: User to change TCP/IP settings:
    ... If you happen to have any Windows XP or Server 2003 member server clients do ... > Administrative Templates -> Network -> Network Connections) there are a ...
    (microsoft.public.win2000.active_directory)
  • Re: Internet Sharing
    ... Configure the NAT Service in Windows 2000 ... Configure Clients to Use a Network Address Translation Server ...
    (microsoft.public.windows.server.general)
  • Re: IP address assignment problem
    ... I have a little problem and seek for ur thoughts, let's assume I'm in a very open environment where everyone can very easily try to get his/her laptop on the network and IP addresses are assigned by a DHCP server and we are in a domain environment, how do I prevent machines that are not part of our domain to be assigned an IP address? ... This approach doesn't stop your rogue clients from connecting to other clients, but merely doesn't give them the information they normally need to do so. ... Using 802.1x, your workstations authenticate through the switch to a radius server before they are allowed any connectivity. ... This authentication can use X.509 certificates, computer account credentials from AD, or whatever else you'd normally configure radius to authenticate with. ...
    (Focus-Microsoft)