I am running Windows 2000 Server on my home system (along with w
wWINDOWS XP systems.  They are all part of a WORKGROUP

I have a LAPTOP I use at work within a doomain.  I cannot connect from
the laptop to ANY of the WORKGROUP systems.

I get the message: "... is not accessible."
"There are currently no logon servers available to service the logon request.

Note that I can BROWSE from my home system to the DOMAIN/LAPTOP system
and logon that DIRECTION using my DOMAIN LOGON from work.

I want the access to my home network (including printers) in the WORKGROUP.

What is the trick here?

If you have a server, why aren't you using Domain? The answer must be
that you're using XP Home on something. The laptop should log onto the
laptop computername instead of a domain.

This is a free comment. your results may vary.

My laptop is part of a WORK domain and works fine there.

Unfortunately, when at HOME, I cannot get it to connect to my home
WORKGROUP (my login-is still the domain login for WORK, which
apparently saved on my LAPTOP even while I am not connected to the
WORK domain.

Right, but you said you are running Windows 2000 Server at HOME. So,
the only real reason to not use domain at home is if you are running
Windows XP HOME (instead of Professional).  So, the next thing is to
not log on to your domain saved on your laptop, but log on to the
laptop's computername (local logon). If you could use a domain at
home, you probably wouldn't be asking this question.

The other thing is that your laptop would have a better chance of
browsing if it was on the same workgroup as the other PC's in your
neighborhood. Regardless, your laptop is authenticated to a domain and
until it's set to be on a workgroup, you're going to have problems.
And that is a pain when moving your computer from one network to
another.

And, third, if you don't log off your network at the office,
authentication at home isn't/shoouldn't be a problem, but is still a
different authentication than necessary for workgroup.

Unfortunately when a computer is joined to a domain the authentication
model works a little differently then in workgroups. Windows caches
much information even when your off the corporate network. Also your
corporate network administrators could be using Group Policies to
enforce authentication against a domain controller. This option is
mostly used in high security sitautions.

I would suggest enabling the Guest account on your server to allow
your Domain joined XP box access to shares or printers. Otherwise I
think your pretty much stuck with one way sharing of resources (Server
to Laptop) There may be a registry hack you could do to not require
Domain Controller Authentication with Kerberos, but this may give you
more headaches then its worth when your connected to your corporate
network.