Re: 2003 server config for routing and remote access
From: Realsaulnier (realsaulnier_at_hotmail.com)
Date: 05/15/04
- Previous message: KARRAMLI: "RAS 2000"
- In reply to: Bill Grant: "Re: 2003 server config for routing and remote access"
- Next in thread: Bill Grant: "Re: 2003 server config for routing and remote access"
- Reply: Bill Grant: "Re: 2003 server config for routing and remote access"
- Messages sorted by: [ date ] [ thread ]
Date: 15 May 2004 04:06:20 -0700
The router works fine. As I said the server sees the internet. The IP
on the router is 192.168.1.1 and yes the the router could do the NAT
for me but the idea of setting this up is the server would be the
proxy/firewall for the network. All the PC's are set to DHCP and run
IP's in the 192.168.0.X range. they all see the network fine. They run
through the first NIC (192.168.0.41)on the server. This is also setup
as the default gateway for the network. the other NIC on the server is
(192.168.1.41) and uses the router as the gateway out to the internet.
This also is working fine. The problem is the "Internal network
interface" This is not an actual card, this is something that
microsoft installs in the routing and remote access service to allow
the two networks see each other. everything other than that interface
is working. the fact that the setting on that interface say
Non-operational and administrative status unknown makes me think this
is where the problem is. Are there any settings in windows, DNS
settings, security policies, active directory, that could affect this
interface?
"Bill Grant" <not.available@online> wrote in message news:<#x65nBiOEHA.556@tk2msftngp13.phx.gbl>...
> It is always a good idea to explain the whole setup in the first place!
>
> Can't the Cisco do NAT for your LAN? What address is on the inside
> interface of the Cisco? A simple diagram of your network (with IP addresses
> and default gateway settings) would help.
>
> "Realsaulnier" <realsaulnier@hotmail.com> wrote in message
> news:3f121d82.0405140449.61cdb7b6@posting.google.com...
> > OK, I changed the LAN nic card to 192.168.1.42. Same problem. My PC's
> > see the server but can't get past it.from my PC I can ping the NIC on
> > the network side (192.168.1.42) but I can't ping the nic on the other
> > side (192.168.0.41)
> > The NIC going to the internet goes to a cisco router then ADSL modem
> > and out. This is working fine.
> >
> >
> >
> > "Bill Grant" <not.available@online> wrote in message
> news:<OtiaNtVOEHA.3028@TK2MSFTNGP11.phx.gbl>...
> > > You cannot have the NIC cards in the same subnet. If you use two NICs,
> > > one must be in the same subnet as your LAN machines, and the other must
> have
> > > a registered public IP address for NAT to work on this server. How does
> your
> > > server access the Internet?
> > >
> > > The interface called internal in RRAS is only used for remote access
> > > (RAS or VPN) to this server. It will only become active if a remote user
> > > connects to it.
> > >
> > > "Realsaulnier" <realsaulnier@hotmail.com> wrote in message
> > > news:3f121d82.0405130701.45058975@posting.google.com...
> > > > Hello Bill,
> > > >
> > > > Yes I have a card for the LAN side (server LAN) and a card for the WAN
> > > > side ( network Conection) both card have a static IP and are working.
> > > > Both cards under IP routing/General have
> > > > Type=Deticated
> > > > IP address=192.168.0.42 for one and 192.168.0.41 for the second
> > > > Administrative status=Up
> > > > Operational Status=Operational
> > > >
> > > > The Internal card on the other hand is adiffrent story.
> > > > Type=Internal
> > > > IP address=Not available
> > > > Administrative atatus=Unknown
> > > > Operational status=Non-operational
> > > >
> > > > Does this help?
> > > >
> > > > "Bill Grant" <not.available@online> wrote in message
> news:<ukKemmLOEHA.1312@TK2MSFTNGP12.phx.gbl>...
> > > > > How does your server connect to the Internet? Is there a NIC on the
> > > > > "public" side to act as the public interface for NAT?
> > > > >
> > > > > If not, you will need to set up a demand-dial interface and give
> it
> a
> > > > > default route to the Internet. You can then configure it as the
> public
> > > > > interface for NAT.
> > > > >
> > > > > "Realsaulnier" <realsaulnier@hotmail.com> wrote in message
> > > > > news:3f121d82.0405121005.451c2f0f@posting.google.com...
> > > > > > Hello all,
> > > > > >
> > > > > > I have a windows 2003 server setup. My PC's all see the network
> and
> > > > > > each other. My server sees the internet. Now the problem is the
> PC's
> > > > > > can see past the server.
> > > > > > Under routing and remote access, NAT/Basic Firewall settings my
> > > > > > internal network interface will not allow me to to select NAT.
> > > > > > everything is grayed out. All I can select is private network.
> > > > > > I also noticed that under IP Routing, General, the internal
> interface
> > > > > > says "IP Address" Not available. "Administrative status" Unknown
> and
> > > > > > "Operational Status" Non-operational.
> > > > > > I could use some help, than you.
- Previous message: KARRAMLI: "RAS 2000"
- In reply to: Bill Grant: "Re: 2003 server config for routing and remote access"
- Next in thread: Bill Grant: "Re: 2003 server config for routing and remote access"
- Reply: Bill Grant: "Re: 2003 server config for routing and remote access"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
