Hi, Has anybody had success configuring a WEB server on a Netware 5.1 box and have people access the WEB Server through a cable / DSL router. If so what type of router was it? Any special configuration? Thanks Andre

I hope this helps, don't know if this is the same Andre who posted earlier... I a BEFSR41 v2 and NetWare 5.1 and have the Netscape Webserver accessible to the public network and private network. The whole idea is to make your TCP/IP environment and the Netscape Web Server think that the NetWare host has the publicly known hostname that your ISP has provided you with. Public hostname issued by my ISP: cr741357-a.wlfdle1.on.wave.home.com Public IP address: DHCP assigned. Linksys router - Private address: 192.168.1.1 NetWare Host - Local IP address (Private): 192.168.1.51 NetWare Host - Gateway address: 192.168.1.1 NetWare Host - Subnetwork mask: 255.255.255.0 Linksys ports open 80 and 443 mapped to 192.168.1.51 (Both TCP and UDP) The NetWare BIND command is: BIND IP 3C90X_1_EII MASK=255.255.255.0 GATE=192.168.1.1 ADDRESS=192.168.1.51 In Netscape's MAGNUS.CONF file I made certain that the parameter value of ServerName was the hostname (including domain) provided by my ISP. In the NetWare HOSTS file I added my ISP hostname to the list of aliases for 192.168.1.51 In the NetWare RESOLV.CFG file I added the domain of ISP provider. I probably used INETCFG to do this, I don't remember now. In the NetWare RESOLV.CFG file I added the nameservers provided by my ISP. I probably used INETCFG to do this, I don't remember now. Within NetWare's INETCFG.NLM utility I selected Protocols->TCP/IP and then changed the value of 'IP Packet Forwarding' to: 'Disabled("End Node")' NOTE: Within the same screen of the INETCFG utility you can set the domain and nameserver ip addresses that will end up in the RESOLV.CFG file by selecting the screen: 'DNS Resolver Configuration' Keep in mind that as far as your ISP is concerned the Linksys router is the host associated to the public hostname they have provided you. WARNING: If the public user is going through a firewall on their side, their firewall may be causing problems and not your setup. WARNING: The BEFSR41 does not like it when a client on the private network uses your ISP's nameserver to resolve a public hostname back to a host that is on your private network. In my case, public users would loose connectivity to any of my machines within the private network when I did this. The BEFSR41 would have to be rebooted so that public users could again connect to the server. This is a limitation of the router. To work around this problem, I included an entry for the public hostname of the NetWare server in the local HOSTS file of each client machine that is part of the private network and associated the NetWare server's private IP address (192.168.1.51) to the public hostname (cr741357-a.wlfdle1.on.wave.home.com). As long as you have a static hostname provided by your ISP, then the setup I have described should work for you as well. If both the hostname and IP address provided by your ISP are dynamic, then they have made it virtually impossible for their customers to host any services. One problem that I have encountered which is maybe not a problem with the Web Server is with the NetWare Management Portal screens. They use redirects and these redirects provide the private IP address and not the public IP address of the host to go to. So far I haven't found a solution to effectively using this the NetWare Management Portal from the public network. Mind you, if I was mode HTML savvy I probably would setup my own static SSL protected webpages to use Server Side Includes to do simple tasks like startup and shutdown the server remotely.