Anyone with Network/Router experience...

[Ziroc]

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.

I would NEVER have any of my machines set to a DMZ. That opens you up bigtime... [img]smile.gif[/img]

Anyway, I figured out what it was! It WAS the subnet! The router was still 255.255.255.252 and it SHOULD have been .0! I overlooked it.. I was like-WHAT THE HELL IS GOING ON!?!? Then I just looked harder and BAM! It hit me. DUUUHHHH! [img]smile.gif[/img]

Thanks to all of you!!! It's running fine now! woohoo! [img]smile.gif[/img]

[img]graemlins/choc.gif[/img] --FINALLY DAN!

[realbinky]

There were some questions about what would happen if you had a hosts entry then connected from elsewhere. The answer is it would still work. It checks the hosts file, then the lmhosts, and then the ISP DNS servers. If one does not work, it goes to the next, I think.

Edit: oops, meant to say NICE WORK! Reason why this place is what it is.

[ 01-03-2003, 02:29 PM: Message edited by: realbinky ]

[Sir Kenyth]

Originally posted by Ziroc: I would NEVER have any of my machines set to a DMZ. That opens you up bigtime... [img]smile.gif[/img] Anyway, I figured out what it was! It WAS the subnet! The router was still 255.255.255.252 and it SHOULD have been .0! I overlooked it.. I was like-WHAT THE HELL IS GOING ON!?!? Then I just looked harder and BAM! It hit me. DUUUHHHH! [img]smile.gif[/img] Thanks to all of you!!! It's running fine now! woohoo! [img]smile.gif[/img] [img]graemlins/choc.gif[/img] --FINALLY DAN![/QB]

Seeeeeeeeeeee! I told you! [img]tongue.gif[/img]

Good work!

[Ziroc]

Originally posted by Sir Kenyth: quote: Originally posted by Ziroc: I would NEVER have any of my machines set to a DMZ. That opens you up bigtime... [img]smile.gif[/img] Anyway, I figured out what it was! It WAS the subnet! The router was still 255.255.255.252 and it SHOULD have been .0! I overlooked it.. I was like-WHAT THE HELL IS GOING ON!?!? Then I just looked harder and BAM! It hit me. DUUUHHHH! [img]smile.gif[/img] Thanks to all of you!!! It's running fine now! woohoo! [img]smile.gif[/img] [img]graemlins/choc.gif[/img] --FINALLY DAN!

Seeeeeeeeeeee! I told you! [img]tongue.gif[/img]

Good work![/QB][/QUOTE]na na naaaa na na!

BTW, this also corrected the Neverwinter Nights server problem! So tonight, it'll be up!!!!

[Night Stalker]

Good find Dan!

I would still implement the hosts file on each machine on your LAN. Otherwise your packets to IW when using the domain name will go outside on the 'Net before returning to your server. This just adds another hole to your firewall. To proove or disproove, do a tracert www.ironworksforum.com. If it returns anything besides 192.168.1.2 on a single line - your packects are leaking onto the 'Net.

And a properly implemented DMZ offers no greater risk than a single firewall with open ports. To do so securely you would need more public IPs. A DMZ is just an area behind a single firewall that has open ports, while the rest of the private network is behind a fully closed firewall.

[ 01-04-2003, 01:55 AM: Message edited by: Night Stalker ]