server logon window

Over the last few months, I've run into a frustrating problem with systems
not displaying the Client for Microsoft Networks logon... they come up with
the stupid "Welcome to Windows" logon instead. These systems have flawless
Internet access (Outlook, Internet Explorer, etc.) but can't browse the
local network or connect to the server or local file sharing systems.

At first, I thought it was a problem with Intel's network drivers, but today
I setup a new system that has a built-in Realtek network connection and now
*it* has the problem as well, so I can't even point to that.

Our server is running Windows 2000. It's been patched up to SP4 (although
this problem happened with SP3, so that's not it). The clients are all
running Windows Millennium. Each has a fixed IP address, as does the file
server (192.168.1.x). Originally, I used to have WINS enabled on clients and
WINS server running on the 2K server, but tried disabling that to see if it
had any effect... didn't. Just tried re-enabling it; no difference.

The server has scripts to setup network mapped drives and to set the time on
the clients, so that's how I'm restoring mapped drives. I've tried both the
"quick logon" and "restore connections at startup" in the client properties,
but it had no effect.

I've found references to removing an "AUTOLOGON" variable in the registry,
but it's not at the suggested location.

The clients are setup with three DNS entries in the DNS tab. The first is
the server's IP address (192.168.1.100) and the second two are from our ISP.
The server and all clients are connected through a single HP 4000M switch.

I can't think of anything else to say that would help point out the problem.
Anybody got any ideas?



--
Charles ³Chris² Bailey
Technology Director for Perry Ballard, Inc.
www.perryballard.com
(269) 983-0611 work € (269) 983-0747 fax
(269) 925-4509 home € (269) 369-6695 cell

In your network properties of the affected computers, what protocols and
services are listed?

Please list everything that appears.

Carey

"Chris Bailey" <(E-Mail Removed)> wrote in message
news:BB3356D9.19BA8%(E-Mail Removed)...
> Over the last few months, I've run into a frustrating problem with systems
> not displaying the Client for Microsoft Networks logon... they come up
with
> the stupid "Welcome to Windows" logon instead. These systems have flawless
> Internet access (Outlook, Internet Explorer, etc.) but can't browse the
> local network or connect to the server or local file sharing systems.
>
> At first, I thought it was a problem with Intel's network drivers, but
today
> I setup a new system that has a built-in Realtek network connection and
now
> *it* has the problem as well, so I can't even point to that.
>
> Our server is running Windows 2000. It's been patched up to SP4 (although
> this problem happened with SP3, so that's not it). The clients are all
> running Windows Millennium. Each has a fixed IP address, as does the file
> server (192.168.1.x). Originally, I used to have WINS enabled on clients
and
> WINS server running on the 2K server, but tried disabling that to see if
it
> had any effect... didn't. Just tried re-enabling it; no difference.
>
> The server has scripts to setup network mapped drives and to set the time
on
> the clients, so that's how I'm restoring mapped drives. I've tried both
the
> "quick logon" and "restore connections at startup" in the client
properties,
> but it had no effect.
>
> I've found references to removing an "AUTOLOGON" variable in the registry,
> but it's not at the suggested location.
>
> The clients are setup with three DNS entries in the DNS tab. The first is
> the server's IP address (192.168.1.100) and the second two are from our
ISP.
> The server and all clients are connected through a single HP 4000M switch.
>
> I can't think of anything else to say that would help point out the
problem.
> Anybody got any ideas?
>
>
>
> --
> Charles ³Chris² Bailey
> Technology Director for Perry Ballard, Inc.
> www.perryballard.com
> (269) 983-0611 work ? (269) 983-0747 fax
> (269) 925-4509 home ? (269) 369-6695 cell
>

Rather than under-report what's going on, here's info on all the panes in my
network config. Hope you spot something incorrect...

LISTED IN NETWORK PROPERTIES
Client for Microsoft Networks
Realtek RTL8139/810x Family Fast Ethernet NIC
TCP/IP

CLIENT FOR MICROSOFT NETWORKS
In this panel, I check "log on to Windows NT domain" and enter "KINGDOM" as
the domain (that's what our domain is named). The option "logon on restore
network options" radio button is checked, but I've tried the other option as
well.

TCP/IP PROPERTIES
* static IP address specified as 192.168.1.127 (for this particular PC) with
a subnet mask of 255.255.255.0. "Detect connection to network media" is
checked (by default -- I've never messed with this button)
* WINS is disabled (tried it enabled, no difference)
* only one gateway is specified -- 192.168.1.1 -- which is the IP address
for our Cisco 1721 router.
* DNS configuration is as follows (for this PC) -- host: trista, domain:
perryballard.com, DNS server search order (top to bottom): 192.168.1.100,
204.177.184.10, 204.177.184.15, domain suffix search order: iserv.net. The
two 204.x.x.x addresses and iserv.net come from our ISP. The 192.168.1.100
address is the IP address of our file server -- the contract who setup our
file server told me I had to have that address listed first in the DNS list.
As for the host and domain at the top of the panel, I've always been told to
just put the user's name for the host and our email domain for the domain.
If that's a faulty recommendation, please feel free to point out my error.
* bindings show "Client for Microsoft Networks" only
* advanced lists "allow binding to ATM" as "no" (a default setting I don't
mess with)
* NetBIOS' single option -- enable NetBIOS over TCP/IP -- is checked but
grayed out

NETWORK IDENTIFICATION
Properties for this pane are as follows
* computer name: Trista
* workgroup: KINGDOM
* computer name: Trista Watts

NETWORK ACCESS CONTROL
I never mess with this pane... the default setting of share-level access
control is selected

in article (E-Mail Removed), Carey Holzman at
(E-Mail Removed) wrote on 7/10/03 6:49 PM:

> In your network properties of the affected computers, what protocols and
> services are listed?
>
> Please list everything that appears.
>
> Carey
>
> "Chris Bailey" <(E-Mail Removed)> wrote in message
> news:BB3356D9.19BA8%(E-Mail Removed)...
>> Over the last few months, I've run into a frustrating problem with systems
>> not displaying the Client for Microsoft Networks logon... they come up
> with
>> the stupid "Welcome to Windows" logon instead. These systems have flawless
>> Internet access (Outlook, Internet Explorer, etc.) but can't browse the
>> local network or connect to the server or local file sharing systems.
>>
>> At first, I thought it was a problem with Intel's network drivers, but
> today
>> I setup a new system that has a built-in Realtek network connection and
> now
>> *it* has the problem as well, so I can't even point to that.
>>
>> Our server is running Windows 2000. It's been patched up to SP4 (although
>> this problem happened with SP3, so that's not it). The clients are all
>> running Windows Millennium. Each has a fixed IP address, as does the file
>> server (192.168.1.x). Originally, I used to have WINS enabled on clients
> and
>> WINS server running on the 2K server, but tried disabling that to see if
> it
>> had any effect... didn't. Just tried re-enabling it; no difference.
>>
>> The server has scripts to setup network mapped drives and to set the time
> on
>> the clients, so that's how I'm restoring mapped drives. I've tried both
> the
>> "quick logon" and "restore connections at startup" in the client
> properties,
>> but it had no effect.
>>
>> I've found references to removing an "AUTOLOGON" variable in the registry,
>> but it's not at the suggested location.
>>
>> The clients are setup with three DNS entries in the DNS tab. The first is
>> the server's IP address (192.168.1.100) and the second two are from our
> ISP.
>> The server and all clients are connected through a single HP 4000M switch.
>>
>> I can't think of anything else to say that would help point out the
> problem.
>> Anybody got any ideas?
>>
>>
>>
>> --
>> Charles ³Chris² Bailey
>> Technology Director for Perry Ballard, Inc.
>> www.perryballard.com
>> (269) 983-0611 work ? (269) 983-0747 fax
>> (269) 925-4509 home ? (269) 369-6695 cell
>>
>
>

On Mon, 14 Jul 2003 21:36:26 GMT,Dave Bowman <(E-Mail Removed)>
penned this whopper in news:Xns93B8B210ED96FCharlesivesnu@130.81.64.196:

> On Mon, 14 Jul 2003 18:42:10 GMT,Chris Bailey <(E-Mail Removed)>
> penned this whopper in news:BB3871C2.19F10%(E-Mail Removed):
>
>> Rather than under-report what's going on, here's info on all the
>> panes in my network config. Hope you spot something incorrect...
>>
>> LISTED IN NETWORK PROPERTIES
>> Client for Microsoft Networks
>> Realtek RTL8139/810x Family Fast Ethernet NIC
>> TCP/IP
Oh, sorry, I'm an idiot: you need to add "File and printer sharing for
Microsoft Networks" try that before fooling with anything else. Good luck.

>>
>> CLIENT FOR MICROSOFT NETWORKS
>> In this panel, I check "log on to Windows NT domain" and enter
>> "KINGDOM" as the domain (that's what our domain is named). The option
>> "logon on restore network options" radio button is checked, but I've
>> tried the other option as well.
> That sort of jumped out at me. That's not a valid domain nam, you have
> no TLD, so DNS will neever find it. In fact, you say that's the
> workgroup name. What's the name of your DC? Normally it would be
> perryballard.com but internally, I suppose you could use any valid
> name you want. Everythiung else looks normal, but wait for carey,
> she's the resident expert here.
>>
>> TCP/IP PROPERTIES
>> * static IP address specified as 192.168.1.127 (for this particular
>> PC) with a subnet mask of 255.255.255.0. "Detect connection to
>> network media" is checked (by default -- I've never messed with this
>> button) * WINS is disabled (tried it enabled, no difference)
>> * only one gateway is specified -- 192.168.1.1 -- which is the IP
>> address for our Cisco 1721 router.
>> * DNS configuration is as follows (for this PC) -- host: trista,
>> domain: perryballard.com, DNS server search order (top to bottom):
>> 192.168.1.100, 204.177.184.10, 204.177.184.15, domain suffix search
>> order: iserv.net. The two 204.x.x.x addresses and iserv.net come from
>> our ISP. The 192.168.1.100 address is the IP address of our file
>> server -- the contract who setup our file server told me I had to
>> have that address listed first in the DNS list. As for the host and
>> domain at the top of the panel, I've always been told to just put the
>> user's name for the host and our email domain for the domain. If
>> that's a faulty recommendation, please feel free to point out my
>> error. * bindings show "Client for Microsoft Networks" only *
>> advanced lists "allow binding to ATM" as "no" (a default setting I
>> don't mess with) * NetBIOS' single option -- enable NetBIOS over
>> TCP/IP -- is checked but grayed out
>>
>> NETWORK IDENTIFICATION
>> Properties for this pane are as follows
>> * computer name: Trista
>> * workgroup: KINGDOM
>> * computer name: Trista Watts
>>
>> NETWORK ACCESS CONTROL
>> I never mess with this pane... the default setting of share-level
>> access control is selected
>>
>> in article (E-Mail Removed), Carey Holzman at
>> (E-Mail Removed) wrote on 7/10/03 6:49 PM:
>>
>>> In your network properties of the affected computers, what protocols
>>> and services are listed?
>>>
>>> Please list everything that appears.
>>>
>>> Carey
>>>
>>> "Chris Bailey" <(E-Mail Removed)> wrote in message
>>> news:BB3356D9.19BA8%(E-Mail Removed)...
>>>> Over the last few months, I've run into a frustrating problem with
>>>> systems not displaying the Client for Microsoft Networks logon...
>>>> they come up
>>> with
>>>> the stupid "Welcome to Windows" logon instead. These systems have
>>>> flawless Internet access (Outlook, Internet Explorer, etc.) but
>>>> can't browse the local network or connect to the server or local
>>>> file sharing systems.
>>>>
>>>> At first, I thought it was a problem with Intel's network drivers,
>>>> but
>>> today
>>>> I setup a new system that has a built-in Realtek network connection
>>>> and
>>> now
>>>> *it* has the problem as well, so I can't even point to that.
>>>>
>>>> Our server is running Windows 2000. It's been patched up to SP4
>>>> (although this problem happened with SP3, so that's not it). The
>>>> clients are all running Windows Millennium. Each has a fixed IP
>>>> address, as does the file server (192.168.1.x). Originally, I used
>>>> to have WINS enabled on clients
>>> and
>>>> WINS server running on the 2K server, but tried disabling that to
>>>> see if
>>> it
>>>> had any effect... didn't. Just tried re-enabling it; no difference.
>>>>
>>>> The server has scripts to setup network mapped drives and to set
>>>> the time
>>> on
>>>> the clients, so that's how I'm restoring mapped drives. I've tried
>>>> both
>>> the
>>>> "quick logon" and "restore connections at startup" in the client
>>> properties,
>>>> but it had no effect.
>>>>
>>>> I've found references to removing an "AUTOLOGON" variable in the
>>>> registry, but it's not at the suggested location.
>>>>
>>>> The clients are setup with three DNS entries in the DNS tab. The
>>>> first is the server's IP address (192.168.1.100) and the second two
>>>> are from our
>>> ISP.
>>>> The server and all clients are connected through a single HP 4000M
>>>> switch.
>>>>
>>>> I can't think of anything else to say that would help point out the
>>> problem.
>>>> Anybody got any ideas?
>>>>
>>>>
>>>>
>>>> --
>>>> Charles ³Chris² Bailey
>>>> Technology Director for Perry Ballard, Inc.
>>>> www.perryballard.com
>>>> (269) 983-0611 work ? (269) 983-0747 fax
>>>> (269) 925-4509 home ? (269) 369-6695 cell
>>>>
>>>
>>>
>>
>
>
>



--
"Belief is not the beginning but the end of all knowledge."
Johann Wolfgang von Goethe (1749-1832); German poet and dramatist.
HAND!
Mike

Tried adding "File and Printer Sharing for Microsoft Networks", with Browse
Master either automatic or disabled, but didn't change anything.

Regarding the domain name situation -- our Windows 2000 server provides a
domain named "KINGDOM". Under our previous Windows NT server, our domain was
called "PBIDOM1". I'm certainly no expert on Windows 2000 domain hosting,
but I remember seeing "kingdom.local" somewhere along the line. Should I be
"phrasing" our domain name differently in the "log on to Windows NT domain"
pane? Should it be all lowercase or have this ".local" on it or something?

Any other ideas, still welcome...



in article Xns93B8B437EECB4Charlesivesnu@130.81.64.196, Dave Bowman at
(E-Mail Removed)lid wrote on 7/14/03 5:49 PM:

> On Mon, 14 Jul 2003 21:36:26 GMT,Dave Bowman <(E-Mail Removed)>
> penned this whopper in news:Xns93B8B210ED96FCharlesivesnu@130.81.64.196:
>
>> On Mon, 14 Jul 2003 18:42:10 GMT,Chris Bailey <(E-Mail Removed)>
>> penned this whopper in news:BB3871C2.19F10%(E-Mail Removed):
>>
>>> Rather than under-report what's going on, here's info on all the
>>> panes in my network config. Hope you spot something incorrect...
>>>
>>> LISTED IN NETWORK PROPERTIES
>>> Client for Microsoft Networks
>>> Realtek RTL8139/810x Family Fast Ethernet NIC
>>> TCP/IP
> Oh, sorry, I'm an idiot: you need to add "File and printer sharing for
> Microsoft Networks" try that before fooling with anything else. Good luck.
>
>>>
>>> CLIENT FOR MICROSOFT NETWORKS
>>> In this panel, I check "log on to Windows NT domain" and enter
>>> "KINGDOM" as the domain (that's what our domain is named). The option
>>> "logon on restore network options" radio button is checked, but I've
>>> tried the other option as well.
>> That sort of jumped out at me. That's not a valid domain nam, you have
>> no TLD, so DNS will neever find it. In fact, you say that's the
>> workgroup name. What's the name of your DC? Normally it would be
>> perryballard.com but internally, I suppose you could use any valid
>> name you want. Everythiung else looks normal, but wait for carey,
>> she's the resident expert here.
>>>
>>> TCP/IP PROPERTIES
>>> * static IP address specified as 192.168.1.127 (for this particular
>>> PC) with a subnet mask of 255.255.255.0. "Detect connection to
>>> network media" is checked (by default -- I've never messed with this
>>> button) * WINS is disabled (tried it enabled, no difference)
>>> * only one gateway is specified -- 192.168.1.1 -- which is the IP
>>> address for our Cisco 1721 router.
>>> * DNS configuration is as follows (for this PC) -- host: trista,
>>> domain: perryballard.com, DNS server search order (top to bottom):
>>> 192.168.1.100, 204.177.184.10, 204.177.184.15, domain suffix search
>>> order: iserv.net. The two 204.x.x.x addresses and iserv.net come from
>>> our ISP. The 192.168.1.100 address is the IP address of our file
>>> server -- the contract who setup our file server told me I had to
>>> have that address listed first in the DNS list. As for the host and
>>> domain at the top of the panel, I've always been told to just put the
>>> user's name for the host and our email domain for the domain. If
>>> that's a faulty recommendation, please feel free to point out my
>>> error. * bindings show "Client for Microsoft Networks" only *
>>> advanced lists "allow binding to ATM" as "no" (a default setting I
>>> don't mess with) * NetBIOS' single option -- enable NetBIOS over
>>> TCP/IP -- is checked but grayed out
>>>
>>> NETWORK IDENTIFICATION
>>> Properties for this pane are as follows
>>> * computer name: Trista
>>> * workgroup: KINGDOM
>>> * computer name: Trista Watts
>>>
>>> NETWORK ACCESS CONTROL
>>> I never mess with this pane... the default setting of share-level
>>> access control is selected
>>>
>>> in article (E-Mail Removed), Carey Holzman at
>>> (E-Mail Removed) wrote on 7/10/03 6:49 PM:
>>>
>>>> In your network properties of the affected computers, what protocols
>>>> and services are listed?
>>>>
>>>> Please list everything that appears.
>>>>
>>>> Carey
>>>>
>>>> "Chris Bailey" <(E-Mail Removed)> wrote in message
>>>> news:BB3356D9.19BA8%(E-Mail Removed)...
>>>>> Over the last few months, I've run into a frustrating problem with
>>>>> systems not displaying the Client for Microsoft Networks logon...
>>>>> they come up
>>>> with
>>>>> the stupid "Welcome to Windows" logon instead. These systems have
>>>>> flawless Internet access (Outlook, Internet Explorer, etc.) but
>>>>> can't browse the local network or connect to the server or local
>>>>> file sharing systems.
>>>>>
>>>>> At first, I thought it was a problem with Intel's network drivers,
>>>>> but
>>>> today
>>>>> I setup a new system that has a built-in Realtek network connection
>>>>> and
>>>> now
>>>>> *it* has the problem as well, so I can't even point to that.
>>>>>
>>>>> Our server is running Windows 2000. It's been patched up to SP4
>>>>> (although this problem happened with SP3, so that's not it). The
>>>>> clients are all running Windows Millennium. Each has a fixed IP
>>>>> address, as does the file server (192.168.1.x). Originally, I used
>>>>> to have WINS enabled on clients
>>>> and
>>>>> WINS server running on the 2K server, but tried disabling that to
>>>>> see if
>>>> it
>>>>> had any effect... didn't. Just tried re-enabling it; no difference.
>>>>>
>>>>> The server has scripts to setup network mapped drives and to set
>>>>> the time
>>>> on
>>>>> the clients, so that's how I'm restoring mapped drives. I've tried
>>>>> both
>>>> the
>>>>> "quick logon" and "restore connections at startup" in the client
>>>> properties,
>>>>> but it had no effect.
>>>>>
>>>>> I've found references to removing an "AUTOLOGON" variable in the
>>>>> registry, but it's not at the suggested location.
>>>>>
>>>>> The clients are setup with three DNS entries in the DNS tab. The
>>>>> first is the server's IP address (192.168.1.100) and the second two
>>>>> are from our
>>>> ISP.
>>>>> The server and all clients are connected through a single HP 4000M
>>>>> switch.
>>>>>
>>>>> I can't think of anything else to say that would help point out the
>>>> problem.
>>>>> Anybody got any ideas?
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Charles ³Chris² Bailey
>>>>> Technology Director for Perry Ballard, Inc.
>>>>> www.perryballard.com
>>>>> (269) 983-0611 work ? (269) 983-0747 fax
>>>>> (269) 925-4509 home ? (269) 369-6695 cell
>>>>>
>>>>
>>>>
>>>
>>
>>
>>
>
>

It's all good.


"Dave Bowman" <(E-Mail Removed)> wrote in message
news:Xns93B8E045EA650Charlesivesnu@130.81.64.196.. .
> On Tue, 15 Jul 2003 00:17:25 GMT,"Carey Holzman"
> <(E-Mail Removed)> penned this whopper in
> news:#(E-Mail Removed):
>
> > Carey is a 'he' not a she.
> >
> > I would say Steve Winograd is the resident expert. I more like the
> > intern.
> >
> >
> > Carey
> <snip>
>
> I do be sorry, sir. I only met one other man with that name in my life,
kid
> of threw me. Guess I ass\u\me'd.
>
> --
> "Belief is not the beginning but the end of all knowledge."
> Johann Wolfgang von Goethe (1749-1832); German poet and dramatist.
> HAND!
> Mike