Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Computing > Cisco > Internal Web Server with cisco 1841 problem

Reply
Thread Tools

Internal Web Server with cisco 1841 problem

 
 
robertm@performancematerials.com
Guest
Posts: n/a
 
      08-26-2006
Hello,

I am new to Cisco and am having mild difficulties. I have a internal ip
(192.168.1.x) and an external network (172.16.32.x).

I have a web server in the 192.168.1.x network that is up and running.
I setup nat so that the computers in 172.16.32.x can access the web
server. That works fine. The problem I am having is that no one on the
internal network (192.168.1.x) can access the webserver from the
external IP address (172.16.32.10).

ASCII Diagram

[HTTP SERV 192.168.1.100] ------| [FE1 192.168.1.1] [FE0 172.16.32.10]
| ------ [172.16.32.x]

So if a computer say 192.168.1.15 points a web browser to 172.16.32.10
they get nothing. They can ping it, but that is all.

Any help would be wonderful!

Thanks
Robert

 
Reply With Quote
 
 
 
 
BernieM
Guest
Posts: n/a
 
      08-26-2006

<> wrote in message
news: ups.com...
> Hello,
>
> I am new to Cisco and am having mild difficulties. I have a internal ip
> (192.168.1.x) and an external network (172.16.32.x).
>
> I have a web server in the 192.168.1.x network that is up and running.
> I setup nat so that the computers in 172.16.32.x can access the web
> server. That works fine. The problem I am having is that no one on the
> internal network (192.168.1.x) can access the webserver from the
> external IP address (172.16.32.10).
>
> ASCII Diagram
>
> [HTTP SERV 192.168.1.100] ------| [FE1 192.168.1.1] [FE0 172.16.32.10]
> | ------ [172.16.32.x]
>
> So if a computer say 192.168.1.15 points a web browser to 172.16.32.10
> they get nothing. They can ping it, but that is all.
>
> Any help would be wonderful!
>
> Thanks
> Robert
>


If you're having hosts in the same subnet as the web server (192.168.1.x)
access the web server on its external address (172.16.32.10) you need to be
natting the source address of the clients so the web server replies to that
address and doesn't reply directly back to the clients. Clients expect
traffic to come from "172.16.32.10".

BernieM


 
Reply With Quote
 
 
 
 
robertm@performancematerials.com
Guest
Posts: n/a
 
      08-28-2006
Here is what I have in my NAT:

Vlan1
inside = 192.168.1.1

FE0
outside = 172.16.32.10

ip nat inside source list 1 interface FastEthernet0 Overload
ip nat inside source static tcp 192.168.1.100 80 interface
fastethernet0 80

What else would I need ?

Thanks again.

BernieM wrote:
> <> wrote in message
> news: ups.com...
> > Hello,
> >
> > I am new to Cisco and am having mild difficulties. I have a internal ip
> > (192.168.1.x) and an external network (172.16.32.x).
> >
> > I have a web server in the 192.168.1.x network that is up and running.
> > I setup nat so that the computers in 172.16.32.x can access the web
> > server. That works fine. The problem I am having is that no one on the
> > internal network (192.168.1.x) can access the webserver from the
> > external IP address (172.16.32.10).
> >
> > ASCII Diagram
> >
> > [HTTP SERV 192.168.1.100] ------| [FE1 192.168.1.1] [FE0 172.16.32.10]
> > | ------ [172.16.32.x]
> >
> > So if a computer say 192.168.1.15 points a web browser to 172.16.32.10
> > they get nothing. They can ping it, but that is all.
> >
> > Any help would be wonderful!
> >
> > Thanks
> > Robert
> >

>
> If you're having hosts in the same subnet as the web server (192.168.1.x)
> access the web server on its external address (172.16.32.10) you need to be
> natting the source address of the clients so the web server replies to that
> address and doesn't reply directly back to the clients. Clients expect
> traffic to come from "172.16.32.10".
>
> BernieM


 
Reply With Quote
 
BernieM
Guest
Posts: n/a
 
      08-28-2006

>> <> wrote in message
>> news: ups.com...
>> > Hello,
>> >
>> > I am new to Cisco and am having mild difficulties. I have a internal ip
>> > (192.168.1.x) and an external network (172.16.32.x).
>> >
>> > I have a web server in the 192.168.1.x network that is up and running.
>> > I setup nat so that the computers in 172.16.32.x can access the web
>> > server. That works fine. The problem I am having is that no one on the
>> > internal network (192.168.1.x) can access the webserver from the
>> > external IP address (172.16.32.10).
>> >
>> > ASCII Diagram
>> >
>> > [HTTP SERV 192.168.1.100] ------| [FE1 192.168.1.1] [FE0 172.16.32.10]
>> > | ------ [172.16.32.x]
>> >
>> > So if a computer say 192.168.1.15 points a web browser to 172.16.32.10
>> > they get nothing. They can ping it, but that is all.
>> >
>> > Any help would be wonderful!
>> >
>> > Thanks
>> > Robert
>> >

>>

> BernieM wrote:
>> If you're having hosts in the same subnet as the web server (192.168.1.x)
>> access the web server on its external address (172.16.32.10) you need to
>> be
>> natting the source address of the clients so the web server replies to
>> that
>> address and doesn't reply directly back to the clients. Clients expect
>> traffic to come from "172.16.32.10".
>>
>> BernieM


>

<> wrote in message
news: oups.com...
> Here is what I have in my NAT:
>
> Vlan1
> inside = 192.168.1.1
>
> FE0
> outside = 172.16.32.10
>
> ip nat inside source list 1 interface FastEthernet0 Overload
> ip nat inside source static tcp 192.168.1.100 80 interface
> fastethernet0 80
>
> What else would I need ?
>
> Thanks again.
>


I don't think you can do it because you can't configure an interface as both
'nat inside' and 'nat outside' it has to be one or the other. Clients in
the same subnet at the server need to use the servers real adddress.

BernieM


 
Reply With Quote
 
BernieM
Guest
Posts: n/a
 
      08-28-2006
"BernieM" <> wrote in message
news:4bHIg.19452$...
>
>>> <> wrote in message
>>> news: ups.com...
>>> > Hello,
>>> >
>>> > I am new to Cisco and am having mild difficulties. I have a internal
>>> > ip
>>> > (192.168.1.x) and an external network (172.16.32.x).
>>> >
>>> > I have a web server in the 192.168.1.x network that is up and running.
>>> > I setup nat so that the computers in 172.16.32.x can access the web
>>> > server. That works fine. The problem I am having is that no one on the
>>> > internal network (192.168.1.x) can access the webserver from the
>>> > external IP address (172.16.32.10).
>>> >
>>> > ASCII Diagram
>>> >
>>> > [HTTP SERV 192.168.1.100] ------| [FE1 192.168.1.1] [FE0
>>> > 172.16.32.10]
>>> > | ------ [172.16.32.x]
>>> >
>>> > So if a computer say 192.168.1.15 points a web browser to 172.16.32.10
>>> > they get nothing. They can ping it, but that is all.
>>> >
>>> > Any help would be wonderful!
>>> >
>>> > Thanks
>>> > Robert
>>> >
>>>

>> BernieM wrote:
>>> If you're having hosts in the same subnet as the web server
>>> (192.168.1.x)
>>> access the web server on its external address (172.16.32.10) you need to
>>> be
>>> natting the source address of the clients so the web server replies to
>>> that
>>> address and doesn't reply directly back to the clients. Clients expect
>>> traffic to come from "172.16.32.10".
>>>
>>> BernieM

>
>>

> <> wrote in message
> news: oups.com...
>> Here is what I have in my NAT:
>>
>> Vlan1
>> inside = 192.168.1.1
>>
>> FE0
>> outside = 172.16.32.10
>>
>> ip nat inside source list 1 interface FastEthernet0 Overload
>> ip nat inside source static tcp 192.168.1.100 80 interface
>> fastethernet0 80
>>
>> What else would I need ?
>>
>> Thanks again.
>>

>
> I don't think you can do it because you can't configure an interface as
> both 'nat inside' and 'nat outside' it has to be one or the other.
> Clients in the same subnet at the server need to use the servers real
> adddress.
>
> BernieM
>


But keep thinking, as you could do it using another device doing the
natting. Like a Radware ASD ...
http://www.radware.com/content/solut...nd/default.asp


 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Cisco Nat Internal > External > Internal dcpearso Cisco 3 03-23-2008 07:01 AM
cisco ios nat from internal->external->internal Bob Cisco 0 12-11-2006 01:05 PM
VPN terminating on 1841 but cannot route to internal LAN? StevenY Cisco 1 06-15-2006 07:34 AM
837. Unable to see internal web server from internal server. eric the brave Cisco 0 03-05-2006 01:52 PM
Cisco PIX 501 - Port forwarded to an internal host via Static NAT doesn't work from internal host JoelSeph Cisco 9 01-23-2006 03:52 PM



Advertisments
 



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57