VPN Connections and port forwarding

Still unable to connect to resources other than the VPN Server (DC, DHCP,
DNS, RRAS). Not only can I not connect I cannot ping any workstation on the
LAN when connected

Well, When I run ipconfig /all I noticed something; Here is a section of the
output:

PPP adapter RAS Server (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.19
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

the Subnet mask is different than the private LAN. Can I change this? If so
how?; If not how do I get around this?

Thanks

Doug

--
Doug

"Carolina On-Site" <(E-Mail Removed)> wrote in
message news:BE3C937F-118D-470E-8C8E-(E-Mail Removed)...
> Still unable to connect to resources other than the VPN Server (DC, DHCP,
> DNS, RRAS). Not only can I not connect I cannot ping any workstation on
the
> LAN when connected

Double check how you configured RRAS with this:

HOW TO: Turn On and Configure Inbound VPN Access in Small Business Server
2000
http://support.microsoft.com/default...b;en-us;320697

> IP Address. . . . . . . . . . . . : 192.168.1.19
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> the Subnet mask is different than the private LAN. Can I change this? If
so
> how?; If not how do I get around this?

That's normal,...leave it be.

--

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

Will the configuration for W2K be the same as Windows Server 2003?

"Phillip Windell" wrote:

>
> "Carolina On-Site" <(E-Mail Removed)> wrote in
> message news:BE3C937F-118D-470E-8C8E-(E-Mail Removed)...
> > Still unable to connect to resources other than the VPN Server (DC, DHCP,
> > DNS, RRAS). Not only can I not connect I cannot ping any workstation on
> the
> > LAN when connected
>
> Double check how you configured RRAS with this:
>
> HOW TO: Turn On and Configure Inbound VPN Access in Small Business Server
> 2000
> http://support.microsoft.com/default...b;en-us;320697
>
> > IP Address. . . . . . . . . . . . : 192.168.1.19
> > Subnet Mask . . . . . . . . . . . : 255.255.255.255
> > the Subnet mask is different than the private LAN. Can I change this? If
> so
> > how?; If not how do I get around this?
>
> That's normal,...leave it be.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>

Your other post said you had SBS2000. SBS is a whole different thing, you
cannot treat it like the regular Server 2000 or 2003.

--

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


"Carolina On-Site" <(E-Mail Removed)> wrote in
message news:76D82FC1-28BE-4FA0-9B32-(E-Mail Removed)...
> Will the configuration for W2K be the same as Windows Server 2003?
>
> "Phillip Windell" wrote:
>
> >
> > "Carolina On-Site" <(E-Mail Removed)> wrote in
> > message news:BE3C937F-118D-470E-8C8E-(E-Mail Removed)...
> > > Still unable to connect to resources other than the VPN Server (DC,
DHCP,
> > > DNS, RRAS). Not only can I not connect I cannot ping any workstation
on
> > the
> > > LAN when connected
> >
> > Double check how you configured RRAS with this:
> >
> > HOW TO: Turn On and Configure Inbound VPN Access in Small Business
Server
> > 2000
> > http://support.microsoft.com/default...b;en-us;320697
> >
> > > IP Address. . . . . . . . . . . . : 192.168.1.19
> > > Subnet Mask . . . . . . . . . . . : 255.255.255.255
> > > the Subnet mask is different than the private LAN. Can I change this?
If
> > so
> > > how?; If not how do I get around this?
> >
> > That's normal,...leave it be.
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> >

Yeah! You are correct. My Mistake! I have Windows Server 2003 SBS.
Hopefully this helps.

Essentially I can connect to the Server using VPN however I cannot connect
to other workstations on the LAN. I wish to either; port forward a connect
to a 192.168.x.x IP address or be able to access the workstation via My
Network Places using the Client VPN. I have tried everything I know and
still unsuccessful.

I appreciate your patience and your expertise! THANKS

Doug

"Phillip Windell" wrote:

> Your other post said you had SBS2000. SBS is a whole different thing, you
> cannot treat it like the regular Server 2000 or 2003.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "Carolina On-Site" <(E-Mail Removed)> wrote in
> message news:76D82FC1-28BE-4FA0-9B32-(E-Mail Removed)...
> > Will the configuration for W2K be the same as Windows Server 2003?
> >
> > "Phillip Windell" wrote:
> >
> > >
> > > "Carolina On-Site" <(E-Mail Removed)> wrote in
> > > message news:BE3C937F-118D-470E-8C8E-(E-Mail Removed)...
> > > > Still unable to connect to resources other than the VPN Server (DC,
> DHCP,
> > > > DNS, RRAS). Not only can I not connect I cannot ping any workstation
> on
> > > the
> > > > LAN when connected
> > >
> > > Double check how you configured RRAS with this:
> > >
> > > HOW TO: Turn On and Configure Inbound VPN Access in Small Business
> Server
> > > 2000
> > > http://support.microsoft.com/default...b;en-us;320697
> > >
> > > > IP Address. . . . . . . . . . . . : 192.168.1.19
> > > > Subnet Mask . . . . . . . . . . . : 255.255.255.255
> > > > the Subnet mask is different than the private LAN. Can I change this?
> If
> > > so
> > > > how?; If not how do I get around this?
> > >
> > > That's normal,...leave it be.
> > >
> > > --
> > >
> > > Phillip Windell [MCP, MVP, CCNA]
> > > www.wandtv.com
> > >
> > >
> > >
>
>
>

"Carolina On-Site" <(E-Mail Removed)> wrote in
message news:8A1F031E-4CF5-4270-B84D-(E-Mail Removed)...
> Yeah! You are correct. My Mistake! I have Windows Server 2003 SBS.
> Hopefully this helps.
>
> Essentially I can connect to the Server using VPN however I cannot connect
> to other workstations on the LAN. I wish to either; port forward a
connect
> to a 192.168.x.x IP address or be able to access the workstation via My
> Network Places using the Client VPN. I have tried everything I know and
> still unsuccessful.

Let me digress for a moment...
"Port forward" is not even a real term although it does get tossed around
all over the place. Ports are not forwarded. People may often say IP
Forwarding but they are almost 99.99% of the time misusing the term,...IP#s
are "forwarded" but that is just normal Layer3 routing, ...see and NT4
machine's TCP/IP settings, or the routing setup in Linux and Unix based
systems to verify that.

What people are really talking about when they say "port forward" or
incorrectly use "IP forward" is really Static-NAT or also called
Reverse-NAT. There is a thing called Port Address Translation (PAT), but
is only works incombination with NAT (Network Address Translation) and is
useless by itself. So you can have reverse-NAT,...or you can Reverse-NAT
with PAT but you can never have PAT by itself. My source for that is the
Cisco CCNP training materials,...particuarly the Advanced Routing section.
In the last two years they may have rolled it into the CCNA material as
well.

Anyway,..now I'm done with that,.....

No you don't "port forward" anything, you don't "forward any IP#s", you
don't NAT, Reverse-NAT, or Static-NAT anything. You might have to "Route"
something, but I doubt it.

The only thing I can tell is use the article I gave and hope that doing it
iwth SBS2003 is the same as SBS2000. Otherwise you will have to ask in one
of the SBS Groups and get answer from people who specialize in SBS. I am not
an "SBS guy" and I stay as far away from SBS as I can get.

--

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