Topic: SERVER MODE

[Pete]

My windows system is the gateway. My e-smith server is the client. Is there away I can make people(outside world) access ssh/apache server? becuase right now, I can only access it localy, which it sucks. I want the outside world to be able to access it.  The program im using in the windows system is called WINROUTE... it also has port mapping....  What ports should I map so people can access ssh/httpd ?

[Terry Brummell]

Forward ports 22 for SSH and 80 for web services (443 is you're using https) to the SME box.

Pete wrote:
>
> My windows system is the gateway. My e-smith server is the
> client. Is there away I can make people(outside world) access
> ssh/apache server? becuase right now, I can only access it
> localy, which it sucks. I want the outside world to be able
> to access it.  The program im using in the windows system is
> called WINROUTE... it also has port mapping....  What ports
> should I map so people can access ssh/httpd ?

[Pete]

Ok, tcp/udp for both? or just tcp?

[Terry Brummell]

TCP is fine, UDP is not a forwardable protocol (as far as I'm told).

Pete wrote:
>
> Ok, tcp/udp for both? or just tcp?

[Pete]

Hey terry, thanks alot man. Hopefully it works. One more thing, I am running a cs server on the esmith box. Based on the howto in the contrib link. Ok, well the problem is that esmith is not the gateway. I'm not sure what to add to the port mapping part in winroute. When I connect to a cs server, its port 20715, so in tcp/udp I should forward ports to 20715/192.168.1.4 (my esmith server..) ?

[Terry Brummell]

I don't know what a "cs" server is.  But, it sure won't hurt to forward both TCP and UDP ports, I have been told that...but what you are doing sounds right....


Pete wrote:
>
> Hey terry, thanks alot man. Hopefully it works. One more
> thing, I am running a cs server on the esmith box. Based on
> the howto in the contrib link. Ok, well the problem is that
> esmith is not the gateway. I'm not sure what to add to the
> port mapping part in winroute. When I connect to a cs server,
> its port 20715, so in tcp/udp I should forward ports to
> 20715/192.168.1.4 (my esmith server..) ?

[Pete]

I'm still having problems. I forward 22/80, but it still doesnt work. The esmith server is on server-only mode. Maybe thats the problem? Maybe in that mode only locally can be access? I'm not sure than.. Any ideas? Do you need more info on my system?

[Terry Brummell]

Ok, 1st, make sure you have SSH open to the public.  2nd, make sure all of your ibays are open to "Enire Internet", I have found that to be a problem when access from a different subnet is needed although the box is running server only.  If that doesn't do it then I don't know what it would be.
Why wouldn't you use the SME box as your gateway/firewall instead of the Winows box with Winroute anyway?  It's possible that Winroute will only forward http requests and not the complete tcp/ip stack as needed.  If you still can't access port 22 and 80, I have no idea where the problem is without duplicating the setup...

Pete wrote:
>
> I'm still having problems. I forward 22/80, but it still
> doesnt work. The esmith server is on server-only mode. Maybe
> thats the problem? Maybe in that mode only locally can be
> access? I'm not sure than.. Any ideas? Do you need more info
> on my system?

[Pete]

I try setting up my cable modem in the esmith box. But it didnt work.. To tell you the truth I don't know how....
 In my windows box, the only thing I do is setup the nic, and plug in the rj-45 cable and it works. I'm not sure what I have to do with the esmith server. My ip is dyn.

[ryan]

I have set up e-smith/SME to Cable several times.  Login as Admin and go through the configure process again.  Use the default for the internal network IP address and remember to say yes to DHCP.

For the external network card, look at the documentation from the cable company.  If they assigned an IP address, enter it and subnet for the external nic.  If DHCP, you have the option to send your cable account username.  Mine starts with cxXXXXXXX-a.  This will allow your SME to accept an IP address like your Windows box does (you said just plug it in, so your Windows must be a DHCP client).  Once the SME server reboots, use the "test" internet connection.  If it passes, your windows machine should be able to access the web through SME.  You installed as server and gateway right?

Good Luck