Anyone with Network/Router experience...

[Sir Kenyth]

Remember, you have two interfaces on your router to check. The ethernet gateway on the inside of the subnet, and the other interface leading to the cable modem (ethernet I assume). I'm assuming the cable modem is a dumb device serving as a means of interfacing the telco medium to your ethernet side. If the cable modem has routing built in, you will have a config on the cable modem port(s) also. To connect to your web server using an IP, you will use your internal address since you are on the internal side of the network. There may be some safety stuff concerning routing loops set that will prevent your packets from being routed outside your network and then back in. That would happen if you tried to use 24.129.134.18 as your destination address and you use NAT. This would only be because your web server and PC are on the same subnet. Since DNS is coming from an outside source, you will need to have a local name resolution to your internal address. I'm not an expert, but I am familiar with CISCO routers. I hope it helps. NAT complicates things a little. I havn't had the pleasure of working with it yet.

[Night Stalker]

I would turn the DMZ back on and put list the IW IP in it - you can map the public IP to the private (192.168.x.x) one in the setup of the DMZ. Then for your local trafic, you need name resolution for IW - since you don't have a large network, running your own DNS would be silly, so just use a hosts file on each machine as andrewas mentioned.

For NWN, you not only have to have the ports open, but like the IP for IW, you need to map the public IP/port to the private IP/port. I haven't used a linksys so I can't walk you through the steps. Hope this gets you started.

[Sir Kenyth]

Originally posted by Night Stalker: I would turn the DMZ back on and put list the IW IP in it - you can map the public IP to the private (192.168.x.x) one in the setup of the DMZ. Then for your local trafic, you need name resolution for IW - since you don't have a large network, running your own DNS would be silly, so just use a hosts file on each machine as andrewas mentioned. For NWN, you not only have to have the ports open, but like the IP for IW, you need to map the public IP/port to the private IP/port. I haven't used a linksys so I can't walk you through the steps. Hope this gets you started.

Night Stalker, are you a CCNA? I'm working on it myself. I don't have any experience with NAT yet. I really need to get a hold of a Cisco 1600 to play with. With Xmas, I can't afford to drop the 400-500 bucks, probably for a while. I have a software IOS simulator, but I hear they don't work as well as the real thing.

[Sir Krustin]

I think Kenyth's got it.

Reading through this, I suspected it might be because he's trying to use an internet IP to address a local IP. (Remember, using NAT the entire subnet looks like one machine to the rest of the internet)

[Ziroc]

Originally posted by Sir Krustin: I think Kenyth's got it. Reading through this, I suspected it might be because he's trying to use an internet IP to address a local IP. (Remember, using NAT the entire subnet looks like one machine to the rest of the internet)

I'll mess with it today and see what I can do!! Thanks all!

PS: For Neverwinter to be hostable, you gotta open port 5121, BUT, if you want the hosted game to show up in GAMESPY's list, you gotta open 4 MORE ports!!!
yuk!

[Sir Kenyth]

Originally posted by Ziroc: quote: Originally posted by Sir Krustin: I think Kenyth's got it. Reading through this, I suspected it might be because he's trying to use an internet IP to address a local IP. (Remember, using NAT the entire subnet looks like one machine to the rest of the internet)

I'll mess with it today and see what I can do!! Thanks all!

PS: For Neverwinter to be hostable, you gotta open port 5121, BUT, if you want the hosted game to show up in GAMESPY's list, you gotta open 4 MORE ports!!!
yuk![/QUOTE]Firewalls are just as fun as NAT huh? More security = less accessibility!

[ 12-31-2002, 12:47 PM: Message edited by: Sir Kenyth ]

[Sir Krustin]

Originally posted by Sir Kenyth: Firewalls are just as fun as NAT huh? More security = less accessibility!

That's the idea, isn't it?

After reading up on network security, particularly the lack therof on winblows systems, I wouldn't run a network without one. I'm positively shocked how wide-open winblows is.

Z: Let us know how you make out...

[Thoran]

I use a Win2002 Advanced Server box for Routing and NAT so I'm going to have to guess a bit regarding how your Router works but maybe some of this will be useful.

Originally posted by Ziroc: Ok, here are my Router settings: 1. DMZ is OFF 2. Port 80 and 25 and SMTP is open only. 3. DHCP is off All else is default I believe. Anyway, on my HOME PC, I cannot connect to my website in the browser, and I can't get to the IP even (24.129.134.18). Also cannot get to these on my laptop. BUT, both can get on the Internet fine. (I went to altavista's translate site and entered the ironworksforum.com URL, and THEIR server pulls my website fine. It's just my setup.

If you can connect to your website using http://192.168.1.2 then everything is working properly locally. You have a dedicated route set up in your Linksys box to forward incoming HTTP traffic to your web site box... it would appear that the Linksys box doesn't know how to recognize when outgoing traffic is destined for your internal server and correctly route it (I'm not sure that ANY router would do that). The router would need to handle these packets totally internally, if it sends em out onto the internet they'll just get lost (because the router isn't listening for it's own outgoing messages I'd imagine [img]smile.gif[/img] )

As said earlier, HOSTS entries that map www.ironworksforum.com to 192.168.1.2 for your local machines will fix this... but then if you connect your laptop to the internet from elsewhere it won't work right. I know that Windows has some capabilities for setting up multiple network environments (Home, Work, Travel, etc...) and perhaps with some experimenting you can resolve this problem too.

Originally posted by Ziroc: Also, I can't host my Neverwinter Nights game. (I DID open the correct ports for the game too! 5121 and a range as well). If you know HOW I can fix this, please reply or email me. Now, I CAN copy files to my shared folder, and go to another PC and it'll be there.. so I can transmit files between PC's just fine. Any help would be VERY helpful! [img]smile.gif[/img] Thanks!!!

Maybe a dumb question, but do you have the Dedicated Route set up in the Linksys router to direct the port 5121 traffic to your game server? I know that there's new dynamic route configuration capabilities that are going around (it allows a machine on a local network to request that a Router redirect an external port to it's internal IP... it's a new capability in Windows 2002 Server, not sure if the dedicated boxes can do it), are you relying on this sort of capibility to setup your server routings? If so than I'd guess that it's not working for NWN and you'll need to manually set up a dedicated route at the linksys end.

Originally posted by Sir Krustin: quote: Originally posted by Sir Kenyth: Firewalls are just as fun as NAT huh? More security = less accessibility!

That's the idea, isn't it?

After reading up on network security, particularly the lack therof on winblows systems, I wouldn't run a network without one. I'm positively shocked how wide-open winblows is.

Z: Let us know how you make out...[/QUOTE]I would never use a broadband connection without my Linksys...I get hit all day long, but nary a query makes it thru to my machine (I ran Norton Inet Security on the machine for 3 months just to see what came through.)

[andrewas]

Originally posted by Thoran: If you can connect to your website using http://192.168.1.2 then everything is working properly locally. You have a dedicated route set up in your Linksys box to forward incoming HTTP traffic to your web site box... it would appear that the Linksys box doesn't know how to recognize when outgoing traffic is destined for your internal server and correctly route it (I'm not sure that ANY router would do that). The router would need to handle these packets totally internally, if it sends em out onto the internet they'll just get lost (because the router isn't listening for it's own outgoing messages I'd imagine [img]smile.gif[/img] )

A cisco 1710 will, or can be made to at least. Whether it puts it through the internet gateway and picks it up on the return trip, or just hands it straight to the netside interface I dont know, but I can definately ping both interfaces from inside. Whether or not it would route HTTP traffic correctly I dont know, but since I can ping the interface it should work.

As said earlier, HOSTS entries that map www.ironworksforum.com to 192.168.1.2 for your local machines will fix this... but then if you connect your laptop to the internet from elsewhere it won't work right. I know that Windows has some capabilities for setting up multiple network environments (Home, Work, Travel, etc...) and perhaps with some experimenting you can resolve this problem too.

A simpler solution would be to have batch files on the desktop to copy the host files in and out. I cant think offhand of a simple way to make a hosts fix apply only when connected to a specfic network. *Possibly* using the lmhosts file instead, it would only apply to ethernet traffic, but I woudnt bet on it.