Re: [OT] XServe networking PITA
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 60549
interpreted = N
texte = I am not quite sure I follow your current configuration but here is the way it is normally done. 1) DSL modem Ethernet into WAN port of the NetGear Firewall Router. 2) Set LAN IP address on router to 192.168.0.1 3) NetGear Router needs to be setup for PPOE connection IE. Use your username and password from Verizon to tell the modem to connect to the Verizon Internet via PPOE. 4) Set the server to static IP example IP 192.168.0.100 Subnet mask 255.255.255.0 Gateway 192.168.0.1 5) Set the DMZ setting on the router to expose 192.168.0.100 6) Connect all your computers to the 8 available ports on the NetGear Router That should do it. Sal D'Anna -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of WJ Starck Sent: Sunday, December 19, 2004 7:09 PM To: WebDNA Talk Subject: [OT] XServe networking PITA Sorry for the OT, but this one has me tearing my hair out. We have two XServes in house. One is a web server and the other is a combination CGPro Mailserver, Nameserver and Retrospect server for backup of the PCs on the LAN. We have a NetGear FVL328 Firewall/Router, and 13 static IPs. This office has a DSL connection from Verizon via a DSL modem, which has one ethernet port. The Netgear has 8 LAN ports and 1 WAN port and is acting as a DCHP server for the private clients on the LAN. Problem is, I can find no combination of settings that will allow the servers to be exposed to the internet and clients on the LAN, while at the same time giving the LAN clients access to the internet. I've tried setting up the firewall with NAT, and placing the servers in a DMZ to no avail. The best I can get with this setup is the servers visible to the internet, but then no clients on the LAN have internet access. We have 13 class C IPs and a gateway IP, which is 66.15.112.1. Apparently, this DSL modem is not a router, but just directs all traffic to the gateway IP. Settings: XServes' Built in Ethernet: IP is manually set to the public IP according to our DNS setup, router is set to 66.15.112.1 XServes' PCI Ethernet: Private IPs assigned by DHCP, router is 192.168.0.1 Firewall: WAN IP is one of the public IPs, gateway is set to 66.15.112.1. LAN IP is 192.168.0.1, NAT is on. DMZ is maps private IP of XServe assigned by DHCP server ---> public IP of each server according to DNS. A thousand blessings and a camel to the kind soul that can help me get this working! Regards, Will Starck -- NovaDerm Skincare Science http://www.novaderm.com wjs@novaderm.com 817-431-8437 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
I am not quite sure I follow your current configuration but here is the way it is normally done. 1) DSL modem Ethernet into WAN port of the NetGear Firewall Router. 2) Set LAN IP address on router to 192.168.0.1 3) NetGear Router needs to be setup for PPOE connection IE. Use your username and password from Verizon to tell the modem to connect to the Verizon Internet via PPOE. 4) Set the server to static IP example IP 192.168.0.100 Subnet mask 255.255.255.0 Gateway 192.168.0.1 5) Set the DMZ setting on the router to expose 192.168.0.100 6) Connect all your computers to the 8 available ports on the NetGear Router That should do it. Sal D'Anna -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of WJ Starck Sent: Sunday, December 19, 2004 7:09 PM To: WebDNA Talk Subject: [OT] XServe networking PITA Sorry for the OT, but this one has me tearing my hair out. We have two XServes in house. One is a web server and the other is a combination CGPro Mailserver, Nameserver and Retrospect server for backup of the PCs on the LAN. We have a NetGear FVL328 Firewall/Router, and 13 static IPs. This office has a DSL connection from Verizon via a DSL modem, which has one ethernet port. The Netgear has 8 LAN ports and 1 WAN port and is acting as a DCHP server for the private clients on the LAN. Problem is, I can find no combination of settings that will allow the servers to be exposed to the internet and clients on the LAN, while at the same time giving the LAN clients access to the internet. I've tried setting up the firewall with NAT, and placing the servers in a DMZ to no avail. The best I can get with this setup is the servers visible to the internet, but then no clients on the LAN have internet access. We have 13 class C IPs and a gateway IP, which is 66.15.112.1. Apparently, this DSL modem is not a router, but just directs all traffic to the gateway IP. Settings: XServes' Built in Ethernet: IP is manually set to the public IP according to our DNS setup, router is set to 66.15.112.1 XServes' PCI Ethernet: Private IPs assigned by DHCP, router is 192.168.0.1 Firewall: WAN IP is one of the public IPs, gateway is set to 66.15.112.1. LAN IP is 192.168.0.1, NAT is on. DMZ is maps private IP of XServe assigned by DHCP server ---> public IP of each server according to DNS. A thousand blessings and a camel to the kind soul that can help me get this working! Regards, Will Starck -- NovaDerm Skincare Science http://www.novaderm.com wjs@novaderm.com 817-431-8437 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
"Sal D'Anna"
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Signal Raised Error (1997)
database problems (1999)
ShowNext Command (1997)
update on include (1997)
Server Freeze (1998)
WebDNA creates DUPLICATE SHOPPING CART NUMBERS (2004)
close to search (2001)
Seattle based Webcatters? (2000)
[WebDNA] What file needs to be edited in apache to server html (2008)
Country & Ship-to address & other fields ? (1997)
Secure Server (1997)
Setting up WebCatalog with Retail Pro data (1996)
Almost a there but..bye bye NetCloak (1997)
[WebDNA] Search on a database (2012)
WebCatalog2 Feature Feedback (1996)
E-mailer error codes (1997)
The USArea® Network web site ... (1997)
Re2: frames & carts (1997)
UPPERCASE (1997)
PCS Frames (1997)