Can RAS/VPN be on the same server as Terminal Server?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an existing Terminal Server on Windows 2003 server. Everything is
working fine. I also have a Remote Access Server for VPN connections into my
network on a separate server. I was trying to consolidate by installing the
RAS/VPN services on my TS but I am having issues.

I CAN install the RAS services, but the RAS services will not start and I
don't even get an error message in the event logs to do any type of
troubleshooting. Is there a rule that you cannot put these 2 (TS and RAS)
servcies on one server?

That is the only thing that I can think of that could be the issue.??help?
 
Pablo said:
I have an existing Terminal Server on Windows 2003 server. Everything is
working fine. I also have a Remote Access Server for VPN connections into my
network on a separate server. I was trying to consolidate by installing the
RAS/VPN services on my TS but I am having issues.

I CAN install the RAS services, but the RAS services will not start and I
don't even get an error message in the event logs to do any type of
troubleshooting. Is there a rule that you cannot put these 2 (TS and RAS)
servcies on one server?

That is the only thing that I can think of that could be the issue.??help?
I have RRAS and terminal server on a S2K3 box. I don't recall having to
do anything special. What exactly happens when you try to enable RRAS?

....kurt
 
I get an error message saying Routing and Remote Access Service cannot be
started. Error code 340. It also says to check the event log, but there is
nothing logged there. I can't find much on this error.

Thanks for your answer,. I just needed to know if there was some type of
rule that this was not possible.
 
1) Open RRAS console (Start --> run --> rrasmgmt.msc)
2) Rightclick on the server name
3) Click on properties
4) Goto 'Security' tab
5) Make sure that windows authentication and accounting are selected. Apply
changes
6) Try to start RRAS again.

Also, providing the RAS tracing logs will help troubleshooting. Steps to
collect these are listed at
http://blogs.technet.com/rrasblog/archive/2005/12/22/416421.aspx

--
Thanks,
Janani [MSFT]
http://blogs.msdn.com/jananiv

RRAS team blog : http://blogs.msdn.com/rrasblog
 
The items below were fine. This did not help. When I try to start RAS I get
an error message "Routing and Remote cannot start due to server specific
error 340. Check your event logs for more info" But there is nothing in the
event logs.

Janani said:
1) Open RRAS console (Start --> run --> rrasmgmt.msc)
2) Rightclick on the server name
3) Click on properties
4) Goto 'Security' tab
5) Make sure that windows authentication and accounting are selected. Apply
changes
6) Try to start RRAS again.

Also, providing the RAS tracing logs will help troubleshooting. Steps to
collect these are listed at
http://blogs.technet.com/rrasblog/archive/2005/12/22/416421.aspx

--
Thanks,
Janani [MSFT]
http://blogs.msdn.com/jananiv

RRAS team blog : http://blogs.msdn.com/rrasblog
---------------------------------------------------------------------------
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Pablo said:
I get an error message saying Routing and Remote Access Service cannot be
started. Error code 340. It also says to check the event log, but there is
nothing logged there. I can't find much on this error.

Thanks for your answer,. I just needed to know if there was some type of
rule that this was not possible.
 
Back
Top