Topic: no access to contribs using static ip

[fixit]

I am having trouble accessing contribs.org using my static ip, once i remove my static ip address, i can view contribs and email contribs.

so i assume maybe my ip address has been black listed or does anyone else have any ideas as to why i cannot view contribs using static ip

i have checked everything on my end. i.e, virus scanner, firewall, spam filter, router and found nothing that could be blocking contribs, because if it were blocking contribs completely, i would not be able to write this message no matter what ip address i was using.

So my assumption is that my static ip address has been black listed, unless someone else could come up with a better reason as to why my static ip cannot access contribs.

  confused

[raem]

fixit

> once i remove my static ip address, i can view contribs and email contribs.

Exactly where are you removing this IP address from ?

Please tell us the details in server manager Review configuration panel.

[fixit]

I remove the static ip from the adsl router

[Smitro]

can you access anything through the router once you change this?

[raem]

fixit

Please tell us the details in the Server Manager/Review configuration panel

[fixit]

Review configuration
Networking Parameters
Server Mode servergateway
Local IP address / subnet mask 10.0.1.1/255.255.255.0
External IP address / subnet mask 10.0.0.1/255.0.0.0
Gateway 10.0.0.138
Additional local networks 10.0.1.0/255.255.255.0
DHCP server enabled
Beginning of DHCP address range 10.0.1.65
End of DHCP address range 10.0.1.250

This all was working great a couple of weeks ago

can do traceroute and ping with static ip, but not view web pages from contribs or email contribs.

looked at firewall, no mention of contribs being blocked.

hope this info might shed some light

[fixit]

Traceroute with static ip, I assume that the * down the bottom mean something

traceroute to contribs.org (207.182.33.10), 30 hops max, 40 byte packets
 1  FastEthernet6-0.civ-service1.Canberra.telstra.net (203.50.1.65)  0.282 ms  0.174 ms  0.269 ms
 2  GigabitEthernet3-0.civ-core2.Canberra.telstra.net (203.50.10.129)  0.749 ms  0.532 ms  0.762 ms
 3  GigabitEthernet2-2.dkn-core1.Canberra.telstra.net (203.50.6.126)  0.546 ms  0.859 ms  0.432 ms
 4  Pos4-1.ken-core4.Sydney.telstra.net (203.50.6.69)  4.808 ms  5.125 ms  5.019 ms
 5  10GigabitEthernet3-0.pad-core4.Sydney.telstra.net (203.50.6.86)  5.298 ms  4.987 ms  5.277 ms
 6  GigabitEthernet2-2.syd-core01.Sydney.net.reach.com (203.50.13.38)  5.296 ms  5.393 ms  5.348 ms
 7  i-12-3.wil-core02.net.reach.com (202.84.249.205)  153.596 ms  153.717 ms  153.607 ms
 8  i-6-2.wil04.net.reach.com (202.84.251.186)  153.554 ms  153.552 ms  153.606 ms
 9  reach.ar1.LAX2.gblx.net (208.50.13.237)  154.047 ms  154.971 ms  154.261 ms
10  so1-0-0-2488M.ar4.PHX1.gblx.net (67.17.68.26)  163.713 ms  164.185 ms  164.625 ms
11  Limelight-Content-Phoenix.ge-3-2-0.ar4.PHX1.gblx.net (208.51.41.230)  163.834 ms  164.335 ms  163.974 ms
12  login-gx-oc3.so2-2-2.jr1.phx1.llnw.net (69.28.139.246)  187.411 ms  185.632 ms  185.728 ms
13  t2-0.Tucson-enss1.t3.LOGIN.COM (204.17.35.106)  185.826 ms  186.289 ms  187.519 ms
14  Core-GW.Opus1.COM (207.182.35.58)  188.284 ms  186.667 ms  187.396 ms
15  DSL-GW3.Opus1.COM (204.27.149.14)  191.029 ms  189.659 ms  190.425 ms
16  coleman-Rstrat-T1.Opus1.NET (207.182.63.246)  265.775 ms  348.69 ms  331.362 ms
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

[raem]

fixit

> Review configuration

What is the setting for DNS Server ?


> This all was working great a couple of weeks ago

So what have you changed since then ?


Why are you using Public IP's 10.x.x,xx on your local network rather than Private IP's 192.xxx,xx,xx ?

[fixit]

Review configuration
Networking Parameters
Server Mode servergateway
Local IP address / subnet mask 10.0.1.1/255.255.255.0
External IP address / subnet mask 10.0.0.1/255.0.0.0
Gateway 10.0.0.138
Additional local networks 10.0.1.0/255.255.255.0
DHCP server enabled
Beginning of DHCP address range 10.0.1.65
End of DHCP address range 10.0.1.250
Server names
DNS server 10.0.1.1
Web server www.fixitcomputers.com.au
Proxy server proxy.fixitcomputers.com.au:3128
FTP server ftp.fixitcomputers.com.au
SMTP, POP, and IMAP mail servers mail.fixitcomputers.com.au

[raem]

ping 61.9.129.4  gets a reply OK, what IP is that ?

ping www.fixitcomputers.com.au time outs

ping 61.9.212.66 times out

[fixit]

my ping will time out because I can not access contribs with it, the other ip's you mentioned are telstras ip's

at this stage I still think that my ip has been black listed for some reason.

I have spent about 3 weeks trying to figure out why, called my isp and asked around then finally post questions on contribs and emailed garret @ ruffdogs & still no closer to finding a answer.

changed settings on adsl router, removed sme server & reinstalled sme serveral times & it's always the same.

The only thing left to do is change my static ip, it's pretty OBVIOUS THAT IS HAS BEEN BLACK LISTED

[jackl]

fixit
Are you using an Alcatel Speedtouch adsl router?

Regards
Jack

[fixit]

yes it is, why????

[jackl]

fixit,

I recognised it from your ip configuration
change the router to bridgeing mode might solve your problem.
The gateway address of 10.0.0.138 was the giveaway if you set the speedtouch to bridge mode then your external ip address provided by your ISP should appear as the gateway address and this should solve your problems.
I am assuming here that you are using PPPOE and have made no other changes to the Speedtouch router. Believe it or not despite being a static address it is usually assigned to your line dynamically by your ISP it just makes sure you get the specified address everytime you connect. So remove any static address settings you have set in the router, and set it to dhcp on WAN side and bridging mode. Set your SME to PPPoe with password, do not set the SME to dhcp or static ip, and your static address from your isp should appear on eth1, and not on your router.
The way you have it configured at the moment makes it difficult for DNS to function correctly.

Regards
Jack

ps   Warning do not use this method with M$ Servers

[fixit]

thanks jack, i will give this a try & see how i go

Thanks for your respone and to Ray as well

Russell