Server2003 VPN & Terminal Server

I have configured a new Windows 2003 Server. It is multi-
homed. It is on a Windows 2000 Domain. It is not a DC.

1 NIC has a private IP, 1 NIC has a Public IP.

RRAS is configured with VPN support. I can connect, but
only to the Windows 2003 server, not the domain. I can
search for computers by name. but they appear in
the "Unknown" location. Opening any computers asks for
the IPC$ password (meaning I'm not part of the domain).

I also have terminal services running on this system.
Connecting via the Remote desktop generates "The client
could conect to the remote computer." message.

I need to have outside sales and office workers connect
through one or the other method (some only need to get the
exchange server).

Any ideas where to start?

"John Morgus" <(E-Mail Removed)> wrote in message
news:c15601c3ed32$4e279330$(E-Mail Removed)...
> RRAS is configured with VPN support. I can connect, but
> only to the Windows 2003 server, not the domain. I can
> search for computers by name. but they appear in
> the "Unknown" location. Opening any computers asks for
> the IPC$ password (meaning I'm not part of the domain).

IPC$? That implies the "client machine" you are connecting from is a Win9x
machine. Make the worgroup name of the machine the same as the Domain name
you are connecting to. If this was a Win2kPro or newer workstation you
wouldn't have this problem and it would present you with a normal login
prompt.

> I also have terminal services running on this system.
> Connecting via the Remote desktop generates "The client
> could conect to the remote computer." message.

Maybe the same as above, but TS configuration is not a "area" I am strong
in. Maybe it has a way to configure the "type" of authentication.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Connecting from an XP system allows connection to the TS
cpu as the domain. I can then access the domain computers
by name, although I'm still not authenticated to the
domain (from what I can determine). Also, the RDC fails
to connect, saying the TS is busy.


>-----Original Message-----
>"John Morgus" <(E-Mail Removed)> wrote in message
>news:c15601c3ed32$4e279330$(E-Mail Removed)...
>> RRAS is configured with VPN support. I can connect, but
>> only to the Windows 2003 server, not the domain. I can
>> search for computers by name. but they appear in
>> the "Unknown" location. Opening any computers asks for
>> the IPC$ password (meaning I'm not part of the domain).
>
>IPC$? That implies the "client machine" you are
connecting from is a Win9x
>machine. Make the worgroup name of the machine the same
as the Domain name
>you are connecting to. If this was a Win2kPro or newer
workstation you
>wouldn't have this problem and it would present you with
a normal login
>prompt.
>
>> I also have terminal services running on this system.
>> Connecting via the Remote desktop generates "The client
>> could conect to the remote computer." message.
>
>Maybe the same as above, but TS configuration is not
a "area" I am strong
>in. Maybe it has a way to configure the "type" of
authentication.
>
>
>--
>
>Phillip Windell [MCP, MVP, CCNA]
>www.wandtv.com
>
>
>
>.
>

Is the VPN Server you are connectiong to also the TS Server as well? TS
isn't a strong area of mine, but if we dig up enough details maybe we can
figure it out or someone who knows will jump in.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"John Morgus" <(E-Mail Removed)> wrote in message
news:da2601c3f04e$04b4f7f0$(E-Mail Removed)...
> Connecting from an XP system allows connection to the TS
> cpu as the domain. I can then access the domain computers
> by name, although I'm still not authenticated to the
> domain (from what I can determine). Also, the RDC fails
> to connect, saying the TS is busy.
>
>
> >-----Original Message-----
> >"John Morgus" <(E-Mail Removed)> wrote in message
> >news:c15601c3ed32$4e279330$(E-Mail Removed)...
> >> RRAS is configured with VPN support. I can connect, but
> >> only to the Windows 2003 server, not the domain. I can
> >> search for computers by name. but they appear in
> >> the "Unknown" location. Opening any computers asks for
> >> the IPC$ password (meaning I'm not part of the domain).
> >
> >IPC$? That implies the "client machine" you are
> connecting from is a Win9x
> >machine. Make the worgroup name of the machine the same
> as the Domain name
> >you are connecting to. If this was a Win2kPro or newer
> workstation you
> >wouldn't have this problem and it would present you with
> a normal login
> >prompt.
> >
> >> I also have terminal services running on this system.
> >> Connecting via the Remote desktop generates "The client
> >> could conect to the remote computer." message.
> >
> >Maybe the same as above, but TS configuration is not
> a "area" I am strong
> >in. Maybe it has a way to configure the "type" of
> authentication.
> >
> >
> >--
> >
> >Phillip Windell [MCP, MVP, CCNA]
> >www.wandtv.com
> >
> >
> >
> >.
> >