RRAS and Master Browser

Hello,
We mistakenly turned on VPN on a Win2003 Server running Exg 2003 & SQL 2K
and our user's Outlook could not connect to Exg. After we turned off VPN the
only way we could get an Outlook connection to Exg was to turn on RRAS. Now
the server in question cannot see the network and the network cannot see the
server. We can get to it by searching directly for it but we need to get to
it in the normal way. Our other four servers show RRAS disabled so we
obviously have something set wrong but cannot figure out what. I'm afraid if
we disable RRAS on this server we may be able to see the network but Outlook
may not be able to connect to Exg again. Can someone help us get back to
normal? Riley


.

Relevant Pages

  • Re: Single user issue; best troubleshooting
    ... COULD be cause by that intermediate 'network access' server ... you do know there is significant logging in Outlook ... form of Integrated Authentication and so all of the OUTLOOK ...
    (microsoft.public.windows.server.active_directory)
  • Re: Which firewall ports to open/reg edits to make for Ex5.5?
    ... They're not accessing thru a public network. ... Ex5.5 server using Outlook 2000 to consult public folders only. ...
    (microsoft.public.exchange.admin)
  • Re: Connection to Exchange stopped working outside of network
    ... Mine must be different because my OWA does not work either. ... Small Business Server 2003 Premium ... Just cannot connect via Outlook 2003 via RPC over HTTP. ... The IP address lease 999.999.999.999 for the Network Card with network ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook Express Not Opening Files after Server Move....
    ... tool to extract mails from dbx files then. ... anyway getting to to work over a network has worked fine ... on all Outlook Express revisions up to now till we tried ... >placement of .DBX files on your server. ...
    (microsoft.public.internet.mail)
  • Outlook and Exchange connection
    ... Subject: Re: Outlook & Exchange Server Connection ... Did you double check the network configuration to make ...
    (microsoft.public.outlook.general)