cant configure RRAS on windows 2000

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

Guest

I have a Windows 2000 advanced server box.
I dont get the "enable routing and remote access" when I use the MMC snap in.
In the MMC, I can see the "local" computer in the left pane.

when i right click "routing and remote acccess", i get following choices in

the menu.
1. add server
2. auto refresh
3. refresh rate.....
4. view
5. help

when i right click on server status, ,i get following choices
1 add server
2. rebuild server list
3 export list
4 help
5 refresh

finally, when i right click on the server name, i get
1 view
2 delete
3 refresh
4 export
5 properties
6 help

if i click on the properties, none of the options in "enable this computer

as" are checked. if i check, it asks for a service restart and service does

not start. if i now start the service again, the options are again in

not-checked state.

the server is not part of any domain. i have logged in as local
administator. remote registry service is also on.

can someone help?
thanks in advance.
 
Similar symptoms seen in Post: Missing
Interfaces and folder Ip Routing Nat by BP 2/10/05
win2k sp4. (C:\netsh ras dump) reveals rras configuration
think might have to reset configuration on rras but reluctant
as it functional, but see can reset via netsh command.
 
The symptoms are little similar.
but in my case the option to turn on/off RRAS is _not_ present. :-(

i noticed on another machine that when I try to enable/disable RRAS, windows
runs an EXE - remrras.exe

this file is present on the problem server. but if i run that manually,
nothing happens, as if windows ignores the clicks :-((

OTOH, if I right click "My Computers", option to "Manage" is also absent.
I thought of infection, but the server has the anti-virus running and
definitions are regularly updated. I did a full scan, including a spyware
scan, but no problems found.

I am clueless.
 
Make sure that the remote registry service is running. This is required
even if the MMC and RRAS are on the same server.
 
Bill Grant said:
Make sure that the remote registry service is running. This is required
even if the MMC and RRAS are on the same server.
Click to expand...

I think I already mentioned that in the original post.

Remote registry service is *ON*
 
Also will not keep any changed settings and have to restart manually
as you do, same no start on menu. Can not connect from another servers rras
admin to the broken one although it adds the server
it prompts for user name/pwd then gives you do not have sufficient
permissions then access denied after two attempted authentications.
Can connect to a good rras from bad rras admin machine
and configure all settings of that rras so the admin snapin seems to be ok
Sure seems like security issue of some kind.
 
it prompts for user name/pwd then gives you do not have sufficient
permissions then access denied after two attempted authentications
Click to expand...

i used to get this authentication thing when the remote access service was
"disabled". i made the remote access service "automatic" after that and
authentication went.

as the latest try, i ran system file checker, hoping system files will be
okay. but it still doesnt work. ya but system file checker logged many errors
in the event log, saying cant copy a file...

what to do next? i dont want to rebuild this box
:-(
 
I have the same exact problem. For about a year now (yes, I've been
trying to figure this out for a year), I have been unable to access
Passport.NET sites from any client behind my Windows 2000 Advanced
server (even Linux clients). Recently, within the last 4 or 5 months, I
have been unable to access about 45% of other sites, including secure
and non-secure sites (one in particular, Discovercard.com ;) ).

I accidentally deleted the Internal interface, but from what I have
read, that really doesn't matter unless you are using VPN / NAT.
However, having said that, I am experiencing the problem originally
posted. To reset my RRAS server, I right-clicked my server name in the
MMC and chose Disable Routing and Remote Access and get the warning
that doing so would erase my current configuration...blah blah blah,
yeah yeah yeah...and proceeded. According to MS, I should be able to
then right click my server name in the MMC and choose Configure and
Enable Routing and Remote Access, however, it is a disabled context
menu item. (BTW, I am running SP4).

TO KIRANGHAG: Is this what happened to you as far as RRAS is concerned
and not being able to "reset" it?

TO EVERYONE ELSE: Has anyone had this happen and know of a solution??

TIA

Craig
 
I have the same exact problem. For about a year now (yes, I've been
trying to figure this out for a year), I have been unable to access
Passport.NET sites from any client behind my Windows 2000 Advanced
server (even Linux clients). Recently, within the last 4 or 5 months, I
have been unable to access about 45% of other sites, including secure
and non-secure sites (one in particular, Discovercard.com ;) ).

I accidentally deleted the Internal interface, but from what I have
read, that really doesn't matter unless you are using VPN / NAT.
However, having said that, I am experiencing the problem originally
posted. To reset my RRAS server, I right-clicked my server name in the
MMC and chose Disable Routing and Remote Access and get the warning
that doing so would erase my current configuration...blah blah blah,
yeah yeah yeah...and proceeded. According to MS, I should be able to
then right click my server name in the MMC and choose Configure and
Enable Routing and Remote Access, however, it is a disabled context
menu item. (BTW, I am running SP4).

TO KIRANGHAG: Is this what happened to you as far as RRAS is concerned
and not being able to "reset" it?

TO EVERYONE ELSE: Has anyone had this happen and know of a solution??

TIA

Craig
 
I have the same exact problem. For about a year now (yes, I've been
trying to figure this out for a year), I have been unable to access
Passport.NET sites from any client behind my Windows 2000 Advanced
server (even Linux clients). Recently, within the last 4 or 5 months, I
have been unable to access about 45% of other sites, including secure
and non-secure sites (one in particular, Discovercard.com ;) ).

I accidentally deleted the Internal interface, but from what I have
read, that really doesn't matter unless you are using VPN / NAT.
However, having said that, I am experiencing the problem originally
posted. To reset my RRAS server, I right-clicked my server name in the
MMC and chose Disable Routing and Remote Access and get the warning
that doing so would erase my current configuration...blah blah blah,
yeah yeah yeah...and proceeded. According to MS, I should be able to
then right click my server name in the MMC and choose Configure and
Enable Routing and Remote Access, however, it is a disabled context
menu item. (BTW, I am running SP4).

TO KIRANGHAG: Is this what happened to you as far as RRAS is concerned
and not being able to "reset" it?

TO EVERYONE ELSE: Has anyone had this happen and know of a solution??

TIA

Craig
Click to expand...

Hey everyone:

Ok, by using the netsh command and using 'reset' everywhere I could, as
well as 'uninstall' in every context I could, when I restarted the RRAS
service, the Internal interface I had accidentally deleted a year
earlier and had been unable to "reinstall" mysteriously reappeared. It
appears to me, that once you have gone through the Configure and Enable
Routing and Remote Access wizard, you cannot go through it again,
rather, you must go through all the various property pages of the
different items in the MMC and reconfigure your server the way you
want. Having said that, I am still unable to browse the Internet from
my clients.

HTH.
 
Naah, I hope I dont have to wait for so long... :-)

currently I am using Windows Internet Sharing. surprisingly, MSN messenger
is not working. I have set it to no proxy and direct connection. its own
troubleshooter says everything is okay..i can go to hotmail.com and after
hitting login, i get page cannot be displayed.

I dont want to club this problem in the thread but then I am desparate to
get the RRAS working.

i am not exactly sure so as how to "reset" it. please guide me thru if you
know it.
as i mentioned, the "enable/disable remote access routing" option is
"absent" and NOT disabled :-(

and i am not yet able to configure the server at all, so there is nothing in
the configuration too.

i wish to get the option somehow.

or should i restart the setup and do a "repair". i havent done it for long
and not sure if it will wipe out my installed application settings..

Kiran
 
Looks built into win2k by design not like NT4.0
where we could remove and reinstall the dang ting :(
Tried to run the Win2k server setup on this dc
and it complained of schema level to high stopping
the in place upgrade process : "No disassemble R5" (
Also starting to see same symptoms of dns errors
for certain web sites at client pc's that's when
rras problem was discovered.
 
Looks built into win2k by design not like NT4.0
where we could remove and reinstall the dang ting :(
Click to expand...

exactly!
i dont know what prompted microsoft to take this approach.
it would have been great if we could fix up things by
un-installing/re-installing.

seems i have to rebuild the box from scratch. sigh!
 
It was separate in NT because it was a post-release add-on. The original
release only has RAS.

RRAS was not available until after SP3, and was a download from
Microsoft.
 
RRas is finally fixed believe it or not.
Seems it was security permissions as suspected
but never would believe it was the Remote
Registry Service Account causing it. Setting
the administrator account on service now
allows full administration of rras snapin extensions.
Local System Account default was not allowing access
as it had in the past. Set domain/controller group policy
templates security for the service, Administrators group/
System as was not configured before just as an
added measure of forced behavior. {: ))
 
Hello eveyone.

In case anyone is reading this article and has tried everything here to
fix their internet connectivity problem when routing through a Windows
2000 server using RRAS, I finally fixed the problem after 6 months of
searching for the answer on Google and at MS KB. I actually was
searching for something else totally unrelated and came across it, at
all places, MS's KB site....go figure, and I typed in exactly the
article I was looking for while performing the search... leave it to MS
to be ever so helpful. No wonder why 80% of the world uses Google.

Anyway, in my case, there could be only one thing left that was wrong.
I determined that all of my TCP/IP settings were correct. My DHCP and
DNS were correct, and RRAS was clean. After all, I've been networking
for 10+ years. I should sure hope by now that I know how to configure
these things ;). The only thing I could think was that the TCP/IP stack
got corrupted on the server and wasn't routing through some internet
requests from my clients. But, as we all know, TCP/IP is THE routing
protocol for Windows 2000 server and, until previously discovered, near
impossible to remove without reinstalling the server. BUT, there is a
way to do it documented by Microsoft.

If you go searching for this article, you won't find it easily. I
believe Microsoft purposely hid this article and doesn't really index
it. They'd rather sit back and laugh at you as you take hours and days
to rebuild your server. So here is the link:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;299451

It took me about 3 hours to follow these instructions and complete
them, but, it solved ALL of my connectivity problems. This is the last
resort thing I would try before the VERY last resort of re-installing
your server. By the way, the directions were unclear in one part: they
said to remove all services that use TCP/IP (or something to that
effect, e.g. WINS, DHCP, DNS, etc.). I found that all you need to
remove were the three I just mentioned as examples: WINS, DHCP, and
DNS. The article also said that your DNS and DHCP would stay in tact.
This IS NOT TRUE. Write down every single setting you have in DHCP and
DNS to restore it to the way it was before you perform this procedure.
You DO NOT need to remove IIS, but just make sure you stop the
following services: WWW, FTP, SMTP, NNTP, and the main IIS service
itself (and set them to disabled until you are done with the procedure
outlined in the article link above).

If you have any questions, please feel free to contact me. I know what
a pain this problem is. Thanks.
 
Back
Top