Need Help With Access Across Domains

I have a quandary that's left me scratching my head, and I'm hoping there is
a simple reason for the problem.

First, let me explain the layout: I have a normal Windows 2003 Server and
two Windows 2003 SBS Servers (which I will refer to as SBS1 and SBS2). Each
server has its own domain, as they service their particular branch. SBS1 is
connected via router-controlled VPN to the Windows 2003 Server, and each
exist within their own subnets. SBS2 has just been set up, and is currently
at the same location as the Windows 2003 Server sharing the same subnet.
SBS2 will be moved to a new location in a month, and will then have its own
subnet and also connected via VPN.

A particular set of users will access all three servers, and there have been
matching username/passwords set up on each server for them. In connectivity
testing I have found:

* Windows 2003 Server can be accessed from SBS1
* SBS1 can be accessed from Windows 2003 Server
* SBS2 can be accessed from SBS1
* SBS1 can be accessed from SBS2

It's the SBS2 to Windows Server 2003 connection that's giving me trouble.
I'm getting the following message:

"There are currently no logon servers available to service the logon
request."

I can ping Windows Server 2003 from SBS2, and I can access the Exchange
Server on Windows 2003 Server from Outlook clients in SBS2 (after a
username/password prompt). I just cannot access the file shares, neither by
NETBIOS name or by the direct IP address.

The exception is that I CAN connect when signed on to an account that's
Administrator level on both SBS2 and Windows Server 2003. Then it pops up
right away. The other server connections work for any defined user,
administrator or not.

Having not been there when the Windows 2003 Server and SBS1 was originally
set up, I am not sure what I'm missing. If I can talk between SBS1 and
SBS2, and also SBS1 and Windows Server 2003, then why not SBS2 and Windows
Server?

Any helpful thoughts would be appreciated. Thanks!




Ben Scaithe

A couple corrections: only ONE administrator-level user can access from SBS2
to the Windows 2003 Server; and that is the original Windows 2003 Server
administrator. Also, users from Windows Server 2003 CAN get access to SBS2,
just not the other way around.


"Ben Scaithe" <(E-Mail Removed)> wrote in message
news:uBmHAqt$(E-Mail Removed)...
>I have a quandary that's left me scratching my head, and I'm hoping there
>is
> a simple reason for the problem.
>
> First, let me explain the layout: I have a normal Windows 2003 Server and
> two Windows 2003 SBS Servers (which I will refer to as SBS1 and SBS2).
> Each
> server has its own domain, as they service their particular branch. SBS1
> is
> connected via router-controlled VPN to the Windows 2003 Server, and each
> exist within their own subnets. SBS2 has just been set up, and is
> currently
> at the same location as the Windows 2003 Server sharing the same subnet.
> SBS2 will be moved to a new location in a month, and will then have its
> own
> subnet and also connected via VPN.
>
> A particular set of users will access all three servers, and there have
> been
> matching username/passwords set up on each server for them. In
> connectivity
> testing I have found:
>
> * Windows 2003 Server can be accessed from SBS1
> * SBS1 can be accessed from Windows 2003 Server
> * SBS2 can be accessed from SBS1
> * SBS1 can be accessed from SBS2
>
> It's the SBS2 to Windows Server 2003 connection that's giving me trouble.
> I'm getting the following message:
>
> "There are currently no logon servers available to service the logon
> request."
>
> I can ping Windows Server 2003 from SBS2, and I can access the Exchange
> Server on Windows 2003 Server from Outlook clients in SBS2 (after a
> username/password prompt). I just cannot access the file shares, neither
> by
> NETBIOS name or by the direct IP address.
>
> The exception is that I CAN connect when signed on to an account that's
> Administrator level on both SBS2 and Windows Server 2003. Then it pops up
> right away. The other server connections work for any defined user,
> administrator or not.
>
> Having not been there when the Windows 2003 Server and SBS1 was originally
> set up, I am not sure what I'm missing. If I can talk between SBS1 and
> SBS2, and also SBS1 and Windows Server 2003, then why not SBS2 and Windows
> Server?
>
> Any helpful thoughts would be appreciated. Thanks!
>
>