Hi,
I don't know if you'll see such an option (I've never seen one, but then
again there are plenty of DSL routers that I've never looked at). Generally,
with the cheaper SOHO type routers they either do support it, or they don't
(there's no option to enable it).
Cheers
Ken
"Tom" <Tom.RemoveThis@discussions.microsoft.com> wrote in message
news:1FD4F3A7-7FE2-48A0-9ED9-9CA240DC8DD7@microsoft.com...
> Ken
>
> I did exactly what you said and that worked. as far as the router, you are
> also probably right, although i will look at the manual some more. So i
> have
> to look for an option called loopback?
>
> It is actaully a combo dsl modem and router in one. That is what verizon
> supplied me with. I would have liked to use a linksys router, but there
> is
> no option to shut off the router and just use the modem. Its is a Westell
> 327. Thanks
>
> "Ken Schaefer" wrote:
>
>> It could be a limitation of your router. Some cheaper routers do not
>> process
>> requests that require a "loopback" (ie a request from on the internal
>> interface destined for the external interface that needs to be forwarded
>> back to a machine on the internel interface). Since everything else seems
>> to
>> be working, I would suspect that this is the problem.
>>
>> You could "manually" overcome this by adding an entry in your client
>> machine's hosts file that points <a style='text-decoration: underline;' href="http://www.yourNewDomain.com" target="_blank">www.yourNewDomain.com</a> -> 192.168.x.x
>> (where
>> this is the internal IP address rather than the public one)
>>
>> Cheers
>> Ken
>>
>> "Tom" <Tom.RemoveThis@discussions.microsoft.com> wrote in message
>> news:C084E7D0-F873-4004-BBB4-007C499D436B@microsoft.com...
>> >I have an DSL Modem and Router. The router obtains a public IP from my
>> >ISP.
>> > The router also acts as a dhcp server and hands out 192.168.0.X
>> > numbers.
>> > I
>> > have port fowarding setup to foward port calls to my computer acting as
>> > a
>> > webserver. It is a win XP pro machine running IIS. I can access the
>> > webserver from any internal PC using the internal IP of the webserver
>> > but
>> > not
>> > the external IP. I can also access the webserver from any external PC
>> > by
>> > using the public IP. My problem is that i can not access my webserver
>> > internally by using the public IP. I want to eventually register a
>> > domain
>> > name and use a dynamic IP updater, but i want to fix this problem
>> > first.
>> > I
>> > hope someone can help me. This is pretty frustrating.
>>
>>
>><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: cant access external ip from internal lan