• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1039
  • Last Modified:

Linksys wireless router

I had a Linksys wired router and went to the combo wired/wireless.

I have a linksys router that points web requests to my web server.  I currently host 4 or 5 sites.  

Upon swapping the routers, everything works fine except that I cannot get to my sites whilst on my network (web server and development machine behind the linksys).  When I attempt to get to my sites I get the Linksys logon prompt.

www.functionware.com is an example.

Any thoughts?
0
classnet
Asked:
classnet
1 Solution
 
classnetAuthor Commented:
FYI... I can't access my websites from either machine behind the router.
0
 
ZoidlingCommented:
Sounds like your router is doing NAT (network address translation) for a single public IP to a private IP network.  Confirm/correct this and provide more detail on your network setup such as IP/mask info and whether your web server is in a DMZ or just part of your private LAN.
0
 
classnetAuthor Commented:
FYI... this had been working prior to swapping out routers.

No DMZ.  Server is on a my LAN.  Just forwarding "80" requests to my "server".  The server is sending request to the correct virtual directory based on header information.  If I remove all forwarding items in the router I get the same issue.

It appears that my public IP address is being pointed to my private router address.  Host/LMHost files are clean.

Linksys is a fairly simple setup.  No  DHCP.

I can get to any other site NOT on my server.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
mikebernhardtCommented:
I'm trying to understand your problem: It soiunds like when you are on a machine inside your private network and you try to go to the public IP of your network, you get the Linksys instead of your own server? What happens if you try to get to your sites from outside the router? When I try I get the 403 page. Is that coming from your Linksys or your server?

For sure you should turn off remote login to your Linksys! This may not address the cause but you've got a big security issue. It should only respond on the inside address.
0
 
classnetAuthor Commented:
Remote login is already disabled (thanks)...

Try going to www.sheldonlivingston.com... functionware isn't setup yet (403 is coming from server).

So, if I try to go to sheldonlivingston.com from the LAN I get the Linksys logon prompt... from outside the LAN all is OK.
0
 
mikebernhardtCommented:
Are you sure that everything that could be set up the same, is? This kind of problem happens a lot with NAT. Normally the solution is to have a DNS server set up on the inside that points to the inside address for your own domains.

It sounds like the router is assuming that since the source address is on the inside, that you want to get to the router itself when you point to the public IP. I wonder if you used netmon or ethereal or something, if you'd see packets from the router login coming from the inside address or the outside address? It could be a router firmware issue, or there could be something you need to turn on or off on the router.

I don't know your exact model or we could look up the manual on-line. If you can't fix it, the workaround would be to set up an inside DNS server with entries for your inside hosts and forwarding to your ISP DNS servers.
0
 
classnetAuthor Commented:
I think it is a simple setup:

Static IP is set up to public, Local IP to private.

DHCP, DDNS, Remote Admin, SNMP and UPnP are off/disabled.

It's a WRT54GP2A-AT linksys.

Were you able to get to sheldonlivingston.com?
0
 
mikebernhardtCommented:
Yes, I got to that site fine.
0
 
mikebernhardtCommented:
The latest firmware is 3.03.6. Is that what you have?
0
 
classnetAuthor Commented:
Linksys site shows no firmware upgrades yet...  I'm on 1.00.14.
0
 
mikebernhardtCommented:
It's quite possible that it's designed to work that way. Any cisco router would behave the same way. there's lots of question posted here about not being able to get the the public address of a web server from inside a private network... maybe the old router was the strange one.
0
 
classnetAuthor Commented:
It's just that when I code I want to "confirm" what the world will actually see... thus I hit the web from the outside.

Now I have to remote to another machine to test.
0
 
classnetAuthor Commented:
I think we need to kill this post... appears no one can help.

Thanks
0
 
DarthModCommented:
Closed, 125 points refunded.

DarthMod
Community Support Moderator
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now