• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Can't connect to internet through my Clark COnnect BOX!

T

tm37

Lifer
I set up a computer as a little server using ClarkConnect,

I get the IP from the ISP and I can access the server via the web based config (from another comp)

However when I try to access any sites I cet the cannot open page error. When I try to ping I get destination not found!

What did I do wrong?
 
Can you access the 'net from the ClarkConnect box -- either by hostname or by direct IP address? Try pinging www.yahoo.com first, and if that doesn't work then try 64.58.76.225. This should allow us to determine whether the problem is with your ClarkConnect <--> Internet interaction, or if it's something else -- such as a NAT configuration error or a problem with your caching nameserver, etc.
 
I can ping the server and I can Ping Yahoo FROM THE SERVER..

I assigned IP's to the Cleints and I still cann't connect tto the internet through the server. I bypass it to post here!🙁
 
There are several possible causes:
[*] Incorrect DNS configuration on the boxes behind your router
[*] Incorrect or missing NAT configuration on the router
[*] No iptables rule to allow outbound HTTP access, or rule is present that explicitly blocks outbound HTTP access
[*] Missing route in the router's routing table

It's not obvious to me whether you tried to ping 64.58.76.225 from a box behind the router. If so and it worked, the option #1 is the most likely. If so and it doesn't work, then ignore option #1.

The second option -- incorrect NAT configuration -- is probably the most likely. Unfortunately I've never used ClarkConnect, so I don't know the process to set up and configure NAT. But you can at least check to see if the iptable_nat module is loaded by running lsmod. You could also check for a line similar to the following in any of the boot scripts:

iptables -t nat -A POSTROUTING -s $all -o $EXTERNAL -j MASQUERADE

That's the line that is used by my firewall script to enabled outbound NAT. $all would be your internal LANs network address and subnet mask (i.e. 192.168.0.0/255.255.255.0), $EXTERNAL would be the name of your external ethernet interface (i.e. eth1).

The others I can't comment about too much, since the various distributions have their own different ways of configuring those things.

If none of this helps, then your best bet would probably be to go to the ClarkConnect web site and solicit help in their forums...
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top