hey I am still having this problem.

I use to be able to FTP and surf to the linux webserver on my network from my windows clients, but my ISP changed my static IP and suddenly i cant ping or ftp or websurf the server, from inside my network. I know the server is working properly ( I think ) because the outside world has no problem pinging or FTP or web surfing to the Linux Server... I just cant do it internally (except for on the linux server, if I am on the linux box i can ftp itself using any of the web domains or ips its assosicated with)

so I am hoping as a last ditch effort before i reformat the linux box some guru here can help.. here is some info if it helps:

Windows XP box:

Ethernet adapter Hard Wired 100mps:

Connection-specific DNS Suffix . : bc.hsia.telus.net
IP Address. . . . . . . . . . . . : 64.180.111.82
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . : 64.180.104.254


Linux Box (mandrake 9.0):

inet: 142.179.67.159
bcast: 142.179.67.255
mask: 255.255.254.0


I took the hardware router off the network to elimante that possibility, both mahcines are directly connected to the Modem via a standard switch, and both are reciving the Static IP'S given from my ISP.

I am not sure what changed when the IPS changed, but something happend (I did not hardcode or change any settings on either machine, I just released/renewd my windows machine and rebooted the linux server and they both attatched to the given IPS automatically.

THe Ip change happened three days ago, so I dont really thing its any sort of DNS issue (the DNS server is third party DNS service outside the network)

HELP!
:bawling:

The ips are not in the same range and subnets are different.

yes, I know but they are both connected to the internet... I would hope that it wouldnt matter, since I need my customers to access the webserver, and I imagine they wont all be in the same range either?

oh also, i forgot to mention that outside people can ping the IP, i just cant, like go ahead and ping 142.179.67.159 ... it times out for me :bawling:

can your linux server ping your windows box ?

:homer:

nope :(

if i talked to my ISP and asked them to reasing me to IPS in the same range do you think that would help?

OK.

do a traceroute to both the systems from each other.

can you ping cnn.com from both systems ?
can you traceroute to the gateway from both systems ?

do a ping/traceroute combination to either systems from both the systems and determine where the fault lie.

maybe your packets are reaching to the other gateway, or your ISP's firewalls.


I did a traceroute and the common IP that i got at the last was:

209.53.1.170

and after that the packets split up to go to 64.180.111.82 and 142.179.67.159


Try doing a traceroute combination to cnn or your ISP or each other and find the point of fault.


:homer:

k, when i traceroute 142.179.67.159 from 64.180.111.82 or vice versa it doesnt even make it to the first hop.. times out.

cnn.com goes like this:


1 18 ms 18 ms 18 ms 209.53.1.233
2 19 ms 18 ms 18 ms nwmrbc01dr12.bb.telus.com [209.53.1.222]
3 113 ms 236 ms 30 ms nwmrbc01dr01.bb.telus.com [154.11.10.73]
4 19 ms 18 ms 19 ms vancbc01gr01.bb.telus.com [204.174.217.4]
5 70 ms 70 ms 70 ms vancbc01br01.bb.telus.com [154.11.10.49]
6 70 ms 69 ms 70 ms clgrab21br01.bb.telus.com [154.11.10.22]
7 69 ms 69 ms 69 ms wnpgmb38br00.bb.telus.com [154.11.10.158]
8 69 ms 69 ms 69 ms 154.11.11.177
9 68 ms 69 ms 69 ms chcgildtgr00.bb.telus.com [154.11.11.14]
10 78 ms 78 ms 78 ms pop2-chi-P4-3.atdn.net [66.185.148.73]
11 79 ms 79 ms 78 ms bb2-chi-P1-0.atdn.net [66.185.148.66]
12 98 ms 98 ms 98 ms bb2-vie-P10-0.atdn.net [66.185.152.215]
13 99 ms 98 ms 99 ms bb1-vie-P11-0.atdn.net [66.185.152.206]
14 105 ms 104 ms 105 ms bb1-cha-P7-0.atdn.net [66.185.152.28]
15 104 ms 104 ms 105 ms bb1-atm-P6-0.atdn.net [66.185.152.182]
16 105 ms 105 ms 105 ms pop1-atl-P4-0.atdn.net [66.185.136.18]
17 * * * Request timed out.
18


stops at 17...? but I can goto cnn.com no problem with a webbrowser.

here is to my ISP:


Tracing route to telus.net [198.161.157.214]
over a maximum of 30 hops:

1 18 ms 18 ms 18 ms 209.53.1.233
2 18 ms 19 ms 18 ms vancbc01dr11.bb.telus.com [209.53.1.190]
3 148 ms 19 ms 347 ms vancbc01dr01.bb.telus.com [154.11.10.69]
4 19 ms 18 ms 18 ms vancbc01gr01.bb.telus.com [154.11.4.97]
5 40 ms 40 ms 40 ms vancbc01br01.bb.telus.com [154.11.10.49]
6 40 ms 40 ms 41 ms clgrab21br01.bb.telus.com [154.11.10.22]
7 40 ms 40 ms 40 ms clgrab31br01.bb.telus.com [154.11.10.165]
8 40 ms 40 ms 40 ms edtnabxmbr01.bb.telus.com [154.11.10.149]
9 39 ms 39 ms 40 ms edtnabxmgr01.bb.telus.com [154.11.10.141]
10 40 ms 40 ms 40 ms edtnabkddr00.bb.telus.com [205.233.111.101]
11 41 ms 39 ms 39 ms 161.184.255.147
12 39 ms 39 ms 40 ms cityweb.telus.net [198.161.157.214]

Trace complete.

Just for fun i tracert Yahoo:


Tracing route to yahoo.com [64.58.79.230]
over a maximum of 30 hops:

1 18 ms 17 ms 18 ms 209.53.1.233
2 18 ms 19 ms 18 ms nwmrbc01dr12.bb.telus.com [209.53.1.222]
3 20 ms 19 ms 19 ms nwmrbc01dr01.bb.telus.com [154.11.10.77]
4 19 ms 19 ms 18 ms nwmrbc01gr01.bb.telus.com [204.174.217.5]
5 24 ms 23 ms 23 ms nwmrbc01br01.bb.telus.com [154.11.10.53]
6 22 ms 22 ms 23 ms sttlwa01gr02.bb.telus.com [209.53.75.178]
7 23 ms 23 ms 23 ms acr2-so-2-1-0.Seattle.cw.net [208.172.81.129]
8 84 ms 85 ms 85 ms agr4-loopback.Washington.cw.net [206.24.226.104]

9 85 ms 84 ms 85 ms dcr2-so-6-3-0.Washington.cw.net [206.24.238.189]

10 86 ms 86 ms 86 ms bhr1-pos-10-0.Sterling1dc2.cw.net [206.24.238.16
6]
11 87 ms 87 ms 86 ms csr04-ve242.stng01.exodus.net [216.33.98.218]
12 193 ms 223 ms 223 ms 216.35.210.126
13 88 ms 88 ms 88 ms w1.rc.vip.dcx.yahoo.com [64.58.79.230]

Trace complete.