people unable to connect on wan side

[spie]

I have read through all the posts and FAQ's here as well as at smoothwall reguarding my problem. I have tried them all as well.

My friends are all setup with dsl connections. They are Natted at their end.

My end of things. My ISP unfortunately requires me to be use PPPOA so I am unable to bridge my connection.

So with that being said I am required to have my POS actiontec modem/router 1524su hold my wan IP. I then dmz 192.168.0.2 to my smoothwall box. Which should open up all ports to smoothwall. However, things are natted at this point. So at my smoothwall box I then have it setup with my red, orange, green network. Red being hooked into my dsl modem/router. Green is my private zone and orange is my dmz zone.

At this point I open up udp port 8767 to my dmz zone 192.168.5.2 which is the ip of the computer hosting TS server. The server is running mandrake 10 at the moment. On the server I then open up udp port 8767 again which should forward traffic to there.

So I am hoping that all of this does make sense.

Now of note I have even tried running the server on my winxp box hooked directly into the dsl modem/router with the ip address of my winxp box set to dmz just to see if it would work. I don't have the firewall running on winxp so that should not have been a problem. My winxp box should have been totally visible and open to whatever at this point.

So what is going on? I have tried the boundtoip or whatever and then I am unable to start the server (linux) or start the server (winxp) but then not able to use administration. users are still unable to connect at this point as well. All of the posts here I have tried so far with no luck. I even thought well it is my one friend that is screwing up so I had my brother try it as well with me directing him as what to do.

BTW I am always able to connect on the lan side of things. Even when I am on the green network and trying to connect to the orange network. The mandrake firewall rules would not permit me to connect if I did not have the port opened up.

What other information is needed here? If clarification is needed please let me know. Thank you in advance for your help.

[spie]

I wanted to add as well that the server can be seen online on the public webserver list. Still users are unable to connect. Does this help anyone?

With messing around today with it as well I decided to unhook my pc and set it up in front of my smoothwall firewall. I had opened up 8767 udp port. Unable to connect to it. Is everyone sure that there does not need to be any other ports opened up for it? The tcpquery port maybe? From my understanding the answer is no.

However I did forget to try the debug mode of my client today. But now I am at work so I can't test anything out till morning.

Does anyone have an idea?

[spie]

Ok an update since no one has been able to suggest anything for me. And since this isn't a router/network forum in the first place either.

I messed around with my setup and finally figured out where I was going wrong and why people were unable to access it from the outside.

So I setup a pc of mine in front of my smoothwall box. smoothwall being my firewall. I was unable to connect to the server at this point. I was still on my network in a sense but not really. I was actually outside of my firewalled part of the network.

I messed around with my dsl modem/router settings including dmz and port forwarding. Then I started looking at my routing tables. I noticed that while I had routes for parts of my lan I did not have a route defined for the segment of my lan that I have the TS server running on. So I setup a static route for this part of the lan and then connected to it from outside of my firewall. I was able to connect at this point.

so maybe people need to setup static routes for TS to work? I don't know but it worked for me

[CIDR]

What you had to do makes sense with the info you
provided above.

Your dsl modem/router had private address of
192.168.0.2 which I am going to guess had a
subnet mask of 255.255.255.0. The TS address
192.168.5.2 is on a different subnet than you
dsl router and therefor would need a route to
tell it how to get there. Most likely what was
happening is the dsl router has a default route
pointing back out to the internet so if it didn't know
where to find a host it would forward it back out
to the internet and that would go no where since
192.168 is a private IP address range.

[spie]

But what is strange is the fact that I had put my actiontec router/modem into dmz to forward all traffic to 192.168.0.2 so it should have forwarded everything there and let my smoothwall handle the rest.

Because I also happen to have my "green" network as smoothwall refers to running. and at one time I didn't have any static routes specified there and it still worked fine.

hmmm might be a stupid bug with this router/modem who knows but its working >

[pim]

Originally posted by spie
But what is strange is the fact that I had put my actiontec router/modem into dmz to forward all traffic to 192.168.0.2 so it should have forwarded everything there and let my smoothwall handle the rest.

you dont put a router in a DMZ, the router gives you the possibility to put a host, ie like a client and/or a server , in a DMZ. This effectively means a router is not looking after that host anymore but connects it directly to the Internet, All firewalling, portforwarding and NAT rules set on the router will not apply to that host anymore

[spie]

sorry for not using the correct terminology there. I must have been tired. I have one connection to my lan from the router. That ip address is set to dmz in the router. this is letting my smoothwall do all of my firewalling for me since that is the only thing connected to the crappy actiontec dsl modem/router. does that make more sense now? I did say it pretty crappy. . but the port fowarding don't work worth a crap on the actiontec.

[pim]

I am still not sure if I really understand you, but ,,,,,


The LAN port on the router obviously has a LAN IP-address, that's sure, however I have not heard yet of anyone putting this address in the DMZ, this will effectively render your router useless. If the router really swallows this at all

If I were you I would put the ip address of the box containing the TS server in the DMZ and see what happens

[spie]

ok. my network is as follows. I have my router which also is my dsl modem. it carries 2 ip address one for the wan and one for the lan. 192.168.0.xx subnet. so on this subnet I have only one computer which is my true firewall setup. I setup the ip address that correlates to my firewall to be in dmz mode on the router.

this effectively forwards all incoming traffic requests to this box whether it be port 30 or port 3332 doesn't matter. saves me the trouble of opening up ports in a bunch of different places.

So i am not setting the routers ip address into dmz mode I am setting a specific port on the router into dmz mode. it just happens to be that I only use one port of the router.

I am not going to set the TS server box into dmz mode. that will do nothing. no traffic would be able to come into the router if i was to do that.

so back to the original. if anyone has multile subnets on their lan and all and they are still having the problem i originally was having they need to take a look at their routing tables.

[CIDR]

Trying to make some sense out of this

What device did you setup that static route on?

What is the subnet mask of the LAN side of your
DSL router and the firewall NIC that it connects to?