In article <0e0801c3b35d$aeb9abc0$(E-Mail Removed)>, "Lawrin Walker"
<(E-Mail Removed)> wrote:
>I am in the process of setting up several machines for a
>beta testing class in our class room. The machines are not
>on a Domain they are in a Workgroup. I am working with
>several different Microsoft Windows Operating Systems. I
>have all of the machines network settings configured the
>same (different IP addresses, of course). I am having
>problems with three of my 98SE systems. I can't get the
>Network Neighborhood icon to show up on the desktop, and
>when the systems boot, I don't get the login screen. I
>have the network settings configured for Client for
>Microsoft Networks. The rest of the configuration is as
>follows:
>
>Specify an IP Address:
> IP Address: 192.168.0.103 (through 105)
> Subnet Mask: 255.255.255.0
>
> WINS Configuration
> Disable WINS Resolution (is checked)
>
> Gateway
> Gateway: 192.168.0.1
>
> DNS Configuration
> Disable DNS (is checked)
>
> Net BIOS
> not configured
> it is grayed
>
> Advanced
> Allow Binding To ATM: no
> Set this protocol to be default protocol. (not checked)
>
> Bindings
> all are checked:
> 'Client for Microsoft Networks'
> 'File and printer sharing for Microsoft Networks'
>
>I checked the 98SE machines against the 98 Original Release
>systems and all of the settings are the same except for the
>settings on the Advanced Tab. The 98 Original Release
>machines show the Advanced Tab settings as None, where the
>98SE systems have the Advanced Tab settings as Allow
>Binding to ATM. I am not sure if this is the problem, and
>I don't know how to get it set back to None. However, I
>noticed that my three Windows ME systems have the Advanced
>Tab Settings set as Allow Binding to ATM, and I can see
>them in Network Neighborhood.
>
>Can anyone help me figure out why I can't get the Login
>prompt or the Network Neighborhood Icon to show up on the
>desktop of my 98SE systems?
>
>Thank you very much
The ATM binding isn't relevant. The missing login prompt is a common
problem in Windows 95/98/Me. It can happen even when you've done
everything right. The most likely fix is to run the registry editor,
open this registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\
Network\Real Mode Net
and delete the value named "AutoLogon". This web site explains how to
do it:
http://www.wown.com/j_helmig/nologon.htm#AutoLogon
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)
Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.
Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com
Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm