Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Originally posted by terrylmt I can't ping out.. seems like the network is an issue then?
it's possible... but not being able to ping isn't necessarily proof of that... i mean, your firewall could be blocking outgoing pings, for example... your ifconfig says the interface had received 7 megabytes worth of data when you posted, BTW...
it would be nice if you could elaborate on why your IP is different from the one the domain resolves to... and post the iptables output also please...
Originally posted by win32sux it would be nice if you could elaborate on why your IP is different from the one the domain resolves to... and post the iptables output also please...
iptables posted.. as for the IP difference, I am resolving that with my network manager now..
I checked the nameserver settings with the domain name registrar and they are all pointing to the correct server..
now just hoping it's not a screwup on our own side..
well, your local server iptables isn't doing any filtering, so if you're getting filtered it's at another point... the output of this should show the IP of your gateway/firewall:
Code:
route -n
sounds like it might be a firewall issue...
the httpd error you get is normal, as httpd is aleady running...
when you say that the records are pointing to the correct server you mean 202.172.233.179, right?? what does your network manager say about the IP address issue??
Originally posted by win32sux
when you say that the records are pointing to the correct server you mean 202.172.233.179, right?? what does your network manager say about the IP address issue?? [/B]
eh.. the nameserver is pointed to my dns server which is dns.neweraint.com..
traceroute to www.primary-learning.com (203.125.225.133), 30 hops max, 38 byte packets
1 swiCS3-V10 (130.59.10.3) 0.261 ms 0.227 ms 0.199 ms
2 swiEZ2-P1 (130.59.36.222) 0.262 ms 0.292 ms 0.221 ms
3 swiIX1-10GE-1-1 (130.59.36.250) 0.298 ms 0.330 ms 0.300 ms
4 zch-b1-geth4-1.telia.net (213.248.79.189) 0.313 ms 0.243 ms 0.257 ms
5 ffm-bb1-pos0-3-1.telia.net (213.248.65.185) 5.721 ms 5.713 ms 5.784 ms
6 prs-bb1-pos7-0-0.telia.net (213.248.64.110) 15.408 ms 15.305 ms 15.324 ms
7 ldn-bb1-pos7-2-0.telia.net (213.248.64.10) 42.158 ms 22.303 ms 22.245 ms
8 nyk-bb1-pos0-2-0.telia.net (213.248.65.90) 92.629 ms 92.631 ms 92.611 ms
9 nyk-b1-pos6-0-0.telia.net (213.248.80.62) 92.785 ms 92.720 ms 92.697 ms
10 so-9-1.car1.NewYork1.Level3.net (209.244.160.161) 97.644 ms 97.630 ms 97.565 ms
11 ae-1-56.bbr2.NewYork1.Level3.net (4.68.97.161) 92.807 ms 105.833 ms 92.767 ms
12 as-0-0.bbr1.SanJose1.Level3.net (64.159.1.133) 202.149 ms 173.559 ms 173.078 ms
13 so-14-0.hsa3.SanJose1.Level3.net (4.68.114.154) 178.153 ms 175.534 ms 169.908 ms
14 65.57.244.2 (65.57.244.2) 175.487 ms 182.214 ms 175.686 ms
15 ge-0-3-0.plapx-cr3.ix.singtel.com (203.208.168.113) 179.678 ms ge-0-0-0.plapx-cr2.ix.singtel.com (203.208.168.105) 175.428 ms ge-3-3-0.plapx-cr3.ix.singtel.com (203.208.168.117) 210.351 ms
16 p1-1.sngtp-cr3.ix.singtel.com (203.208.182.113) 382.840 ms ge-1-0-0.plapx-cr3.ix.singtel.com (203.208.168.98) 176.780 ms 203.208.182.57 (203.208.182.57) 396.189 ms
17 202.160.250.54 (202.160.250.54) 382.661 ms 369.961 ms p1-1.sngtp-cr3.ix.singtel.com (203.208.182.113) 383.584 ms
18 202.160.250.54 (202.160.250.54) 366.986 ms FE-0-0-0.parkway.singnet.com.sg (165.21.12.30) 377.324 ms 202.160.250.54 (202.160.250.54) 367.450 ms
19 165.21.22.182 (165.21.22.182) 396.688 ms 370.154 ms FE-0-0-0.parkway.singnet.com.sg (165.21.12.30) 370.222 ms
20 203.125.217.210 (203.125.217.210) 392.086 ms 165.21.22.182 (165.21.22.182) 386.541 ms 203.125.217.210 (203.125.217.210) 410.222 ms
21 203.125.217.210 (203.125.217.210) 410.853 ms 417.489 ms *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
i am able to ping 203.125.217.210...
Code:
bash-3.00$ ping -c 3 203.125.217.210
PING 203.125.217.210 (203.125.217.210) 56(84) bytes of data.
64 bytes from 203.125.217.210: icmp_seq=1 ttl=244 time=377 ms
64 bytes from 203.125.217.210: icmp_seq=2 ttl=244 time=370 ms
64 bytes from 203.125.217.210: icmp_seq=3 ttl=244 time=363 ms
--- 203.125.217.210 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2020ms
rtt min/avg/max/mdev = 363.957/370.391/377.089/5.387 ms
i'm not sure why the packet trace stops at that IP before going on to 203.125.225.133... this might have something to do with the current problem you are having...
BTW, at the time of this post 203.125.225.133 still seems dead to me:
Code:
bash-3.00$ ping -c 3 203.125.225.133
PING 203.125.225.133 (203.125.225.133) 56(84) bytes of data.
--- 203.125.225.133 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms
bash-3.00$ nmap -p 80 -P0 203.125.225.133
Starting nmap 3.75 ( http://www.insecure.org/nmap/ ) at 2005-04-26 01:27 EST
Interesting ports on 203.125.225.133:
PORT STATE SERVICE
80/tcp filtered http
Nmap run completed -- 1 IP address (1 host up) scanned in 12.092 seconds
Originally posted by terrylmt 172.16.0.6 with mask 255.255.0.0
you can assign that IP with the ifconfig command... but the configuration will be gone when you reboot... this should be enough for you to conduct tests and make sure everything works fine, though... in order to tell you which files to edit to make the IP change permanent we need to know what linux distribution the server is running...
Code:
ifconfig eth0 inet 172.16.0.6 netmask 255.255.0.0
that would set the IP, but you'd still need to set the gateway... ask him the internal IP of the firewall/router, for example if he tells you it's 172.16.0.1 then you can set it (also temporarily) with:
Code:
route add default gateway 172.16.0.1 eth0
now your FQDM should point to the external IP of the firewall/router that is doing NAT for your server, and the TCP/80 packets will get forwarded to your server at 172.16.0.6...
good luck... i'll be back online tomorrow, i'm gonna go sleep now...
Originally posted by terrylmt No. Mine is having a local IP
oh, okay, then your server should probably have one too - with your network manager setting the router/firewall to do NAT, as it appears he's already doing...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.