Shared Folder access with VPN in windows 2003

I have a Domain Controller set up as a RRAS server with
VPN. It only has one nic so it is set up using
the 'custom' option when I added the RRAS service.
It worked fine and I could browse the network and access
shared folders on the RRAS PC. I did have the issue that
after I used a VPN connection no one in the office could
browse the network and I applied the registry edits in KB
292822.
Now I can VPN in but I can't connect to shared folders on
the RRAS server? I also can't ping the nic address of the
server only the VPN address it created.
Any help out there
Thanks
Jim

posting the results of both vpn client and server here may help.

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"Jim Bowie" <(E-Mail Removed)> wrote in message
news:119ca01c441e4$b058e020$(E-Mail Removed)...
>I have a Domain Controller set up as a RRAS server with
> VPN. It only has one nic so it is set up using
> the 'custom' option when I added the RRAS service.
> It worked fine and I could browse the network and access
> shared folders on the RRAS PC. I did have the issue that
> after I used a VPN connection no one in the office could
> browse the network and I applied the registry edits in KB
> 292822.
> Now I can VPN in but I can't connect to shared folders on
> the RRAS server? I also can't ping the nic address of the
> server only the VPN address it created.
> Any help out there
> Thanks
> Jim

Hi,

I'm experiencing the same problem. But in my case I can
ping all the servers ip adresses; VPN pool ip and ip
adresses bound to the fysical NIC.

I tried enabling the "Client for Microsoft networks"
and "File and Printer sharing" network services. Didn't
work either.

So I'm also still looking for a solutions.

With kind regards,
Sander van Beek

>-----Original Message-----
>From reading around it seams that having Windows 2003 be
the effective PDC and therefore the browse master and be
the RRAS server is not easy if possible. Since RRAS uses
another IP address other than the physical NIC IP address
there is no 'route' between the two. It can route back
onto the LAN and I can connect to all other resources but
not to itself.
>So, should I buy another PC or can the RRAS server
connect VPN clients to itself somehow? I would rather not
buy more licenses and hardware as I thought this was
possible (how does Small Business Server do it?)
>Jim
>.
>

The main problem with connecting remotely to a DC (especially the
first/only DC in a domain) it the browsing problem. Because the DC is now
multihomed, you have the old multihomed PDC problem from NT days. You can
have similar problems with DNS names if you are using dynamic DNS, because
the server has multiple entries.

This is discussed in KB 292822 . For the browsing problem, disabling
Netbios over TCP/IP on the RRAS interface solved this problem. Only the LAN
IP was used by the browser service.

After W2k SP3 introduced some security updates, this fix caused logon
and browsing problems for some clients. These problems and a possible
workaround are discussed in KB 830063 .

"Sander van Beek" <(E-Mail Removed)> wrote in message
news:1461801c444ef$57708180$(E-Mail Removed)...
> Hi,
>
> I'm experiencing the same problem. But in my case I can
> ping all the servers ip adresses; VPN pool ip and ip
> adresses bound to the fysical NIC.
>
> I tried enabling the "Client for Microsoft networks"
> and "File and Printer sharing" network services. Didn't
> work either.
>
> So I'm also still looking for a solutions.
>
> With kind regards,
> Sander van Beek
>
> >-----Original Message-----
> >From reading around it seams that having Windows 2003 be
> the effective PDC and therefore the browse master and be
> the RRAS server is not easy if possible. Since RRAS uses
> another IP address other than the physical NIC IP address
> there is no 'route' between the two. It can route back
> onto the LAN and I can connect to all other resources but
> not to itself.
> >So, should I buy another PC or can the RRAS server
> connect VPN clients to itself somehow? I would rather not
> buy more licenses and hardware as I thought this was
> possible (how does Small Business Server do it?)
> >Jim
> >.
> >