I have recently received my new IP for my FDC server,
It has IP conflict or routing issues!

there is 40-100% packet loss!
I cannot connect to server using TerminalServices Client,
After 2 hours with too many disconnections, closed connections, .. from VNC
I could add another IP to the adaptor, but it has the same packet loss issue,

here is my current TCP/IP config:
IPs:
66.227.104.129
66.227.111.141

Netmask:
255.255.248.0

Gateway:
66.227.104.1

DNS IPs:
209.120.214.166
209.120.214.162


NetDude's opinion:

hmm... i am seeing 40-60% packet loss... not good... what could be the cause? hmm... i'd put my first bet on a half-duplex/full-duplex issue... ur server being set to one, switch being set to the other... or a port speed issue... server set to 100Mbps and switch set to 10Mbps... or vice versa (yeah right)...

after that... i'd start blaming the router... (which is most likely a linux box with a bit of bridging software and a packet shaping system like ipfw in freebsd or ipchains in redhat)...

Current Server TCP/IP Config:

Local Area Connection Status:

Connection:

Status: Connected
Duration: 4:49:16
Speed: 100.0 Mpps

Mattf's opinion:
oversubscribed bandwidth?
jst a speculation.


Is there anybody who has the same problem? what do u think about it?

If you can login with SSH or telnet type 'ifconfig' and 'dmesg' and paste the results. Might be helpful.

it is a W2K server + MS SQL server

>tracert 66.227.104.129

Tracing route to 66.227.104.129 over a maximum of 30 hops

7 182 ms 159 ms 148 ms Level3.atdn.net [66.185.143.90]
8 163 ms 149 ms 158 ms so-4-0-0.mp2.London1.Level3.net [212.187.131.125
]
9 182 ms 160 ms 168 ms so-3-0-0.mp1.London2.Level3.net [212.187.128.46]

10 232 ms 219 ms 238 ms so-1-0-0.mp1.Washington1.Level3.net [212.187.128
.138]
11 251 ms 260 ms 248 ms so-3-0-0.mp1.Chicago1.Level3.net [64.159.1.33]
12 275 ms 272 ms 273 ms pos8-0.core1.Chicago1.Level3.net [209.247.10.162
]
13 271 ms 250 ms 239 ms gigabitethernet6-2.ipcolo2.Chicago1.Level3.net [
209.244.8.30]
14 273 ms 258 ms 240 ms unknown.Level3.net [63.210.100.206]
15 463 ms 430 ms 458 ms ge-1-3-0.chi002jp02.yipes.com [66.54.192.126]
16 272 ms 269 ms 270 ms rif1.chi002bd02.yipes.com [66.54.192.170]
17 314 ms 277 ms 239 ms 209.120.214.89
18 302 ms 270 ms 289 ms o4-8ap1.chi011ap01.yipes.com [66.54.192.89]
19 302 ms 260 ms 249 ms 209.120.155.11
20 582 ms * 472 ms 66.227.104.129

Trace complete.


Seems abit of congestion between Level3 + Yipes and also your box seems to be getting screwballed
and


>ping 66.227.104.129

Pinging 66.227.104.129 with 32 bytes of data:

Request timed out.
Reply from 66.227.104.129: bytes=32 time=554ms TTL=109
Reply from 66.227.104.129: bytes=32 time=583ms TTL=109
Request timed out.

Ping statistics for 66.227.104.129:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 554ms, Maximum = 583ms, Average = 568ms

No, there's no congestion between Yipes and Level3:

traceroute to 66.227.104.129 (66.227.104.129), 30 hops max, 38 byte packets
1 f13.ba01.b003070-1.sfo01.atlas.cogentco.com (66.250.4.165) 4.592 ms 0.434 ms 0.386 ms
2 g0-2.core02.sfo01.atlas.cogentco.com (66.28.5.181) 1.301 ms 0.647 ms 1.116 ms
3 p6-0.br01.sfo01.atlas.psi.net (154.54.1.42) 0.440 ms 0.398 ms 0.411 ms
4 p6-0.br01.sfo03.atlas.psi.net (154.54.2.94) 0.510 ms 0.441 ms 0.440 ms
5 p5-0.br01.sfo02.atlas.psi.net (154.54.2.98) 1.162 ms 1.110 ms 1.101 ms
6 pos1-6.core2.SanJose1.Level3.net (209.0.227.25) 3.370 ms 2.322 ms 2.305 ms
7 ae0-56.mp2.SanJose1.Level3.net (64.159.2.161) 2.674 ms 2.582 ms 2.673 ms
8 so-3-0-0.mp1.Chicago1.Level3.net (64.159.1.33) 81.900 ms 81.561 ms 81.859 ms
9 pos8-0.core1.Chicago1.Level3.net (209.247.10.162) 81.964 ms 81.573 ms 81.629 ms
10 gigabitethernet6-2.ipcolo2.Chicago1.Level3.net (209.244.8.30) 81.525 ms 81.789 ms 81.641 ms
11 unknown.Level3.net (63.210.100.206) 81.859 ms 82.531 ms 81.947 ms
12 ge-1-3-0.chi002jp02.yipes.com (66.54.192.126) 82.370 ms 81.567 ms 82.548 ms
13 rif1.chi002bd02.yipes.com (66.54.192.170) 82.388 ms 82.381 ms 82.284 ms
14 209.120.214.89 (209.120.214.89) 83.250 ms 82.684 ms 82.956 ms
15 o4-8ap1.chi011ap01.yipes.com (66.54.192.89) 82.240 ms 82.907 ms 82.421 ms
16 209.120.155.11 (209.120.155.11) 82.181 ms 83.073 ms 82.692 ms
17 66.227.104.129 (66.227.104.129) 82.196 ms * *

There's clearly a problem between FDC's router/switch and this server. Maybe a bad network cable?

I think level3 has a problem.. our yipes
( must be a the route betwen the two things :)

the trace route ( From Brasil - Sao Paulo - Telefonica DSL )

Did i help ? :)

PS :> I'm making several downloads and my ping it's a little high normal ping to USA is ( 150-190 ms )


Tracing route to 66.227.104.129 over a maximum of 30 hops


1 100 ms 30 ms 50 ms 200-171-254-225.customer.telesp.net.br [200.171.
254.225]
2 141 ms 20 ms 20 ms atm-2-0-4-br-spo-pa-rc1.bbone.telesp.net.br [200
.171.254.141]
3 110 ms 20 ms 10 ms pos-14-4-br-spo-co-rt1.bbone.telesp.net.br [200.
205.254.117]
4 20 ms 20 ms 40 ms 200.207.252.218
5 80 ms 120 ms 30 ms So5-0-1-0-grtsaoco1.ri.telefonica-data.net [213.
140.50.89]
6 130 ms 131 ms 130 ms So6-1-0-0-grtmiabr1.ri.telefonica-data.net [213.
140.36.58]
7 170 ms 240 ms 191 ms So6-2-0-0-grtmiatc3.ri.telefonica-data.net [213.
140.37.206]
8 381 ms 280 ms 130 ms P4-1-grtmiasd1.ri.telefonica-data.net [213.140.3
7.166]
9 301 ms 210 ms 190 ms gige5-1-513.hsipaccess1.Miami1.Level3.net [63.21
2.176.229]
10 350 ms 511 ms 341 ms ge-6-0-0.mp2.Miami1.Level3.net [64.159.0.17]
11 270 ms 170 ms 190 ms so-1-0-0.mp1.Chicago1.Level3.net [209.247.9.105]

12 160 ms 171 ms 180 ms pos8-0.core1.Chicago1.Level3.net [209.247.10.162
]
13 311 ms 240 ms 170 ms gigabitethernet6-2.ipcolo2.Chicago1.Level3.net [
209.244.8.30]
14 461 ms 160 ms 160 ms unknown.Level3.net [63.210.100.206]
15 331 ms 170 ms 190 ms rif6.chi002bd01.yipes.com [66.54.192.166]
16 211 ms 330 ms 230 ms 209.120.214.82
17 160 ms 161 ms 160 ms 209.120.214.89
18 170 ms 260 ms 221 ms o4-8ap1.chi011ap01.yipes.com [66.54.192.89]
19 181 ms 240 ms 180 ms 209.120.155.11
20 271 ms 220 ms * 66.227.104.129
21 170 ms 400 ms * 66.227.104.129
22 161 ms * 241 ms 66.227.104.129

ace complete.



Ping statistic for 66.227.104.129 it 1000 Bytes of data :
packets sent : 21, Received : 5, Lost : 26 (76% loss)
Min : 241 ms Max :340 ms

Would u please tell me what can I do myself??

There are 3 emails sent to FDC regarding this issue by now!
After one week down time, Should I wait another week to solve packet loss?
there is another weekend again! :(
This way,I cannot even copy my server contents to another server!

Ping 66.227.104.129 ...
1 Addr:66.227.104.129, RTT: 1318ms, TTL: 103
2 Addr:66.227.104.129, RTT: 2170ms, TTL: 103
3 failed
4 failed
5 failed
6 failed
7 Addr:66.227.104.129, RTT: 1235ms, TTL: 103
8 failed
9 Addr:66.227.104.129, RTT: 1057ms, TTL: 103
10 failed

Did you ask if there is a routing problem betwen
( level3 and yipes ) ?


I guess if they know they have this problem, has to be fix like in 24 h. our less ... ( right guys ? )


Wait till night time :) if they don't fix wait till 3-4 AM that has a low trafic and try to pull stuff out..

As it seems this is just my server's problem!! other IPs have no packet loss!

try 66.227.104.128 ,

do your other servers take extactly the same route out? its quite possibly a combination of matt and netdudes suggestions, **** network coupled with **** servers and its been setup wrong.

No it is the same route from Level3 to Yipes and then FDC router at 209.120.155.11 ,

FDC block of IPs:
66.227.96.1 to 66.227.111.255

i ran a trace a few times and i dont see the level3 problem peering that others have, but i do get packet loss on the final hop, would suggest a dodgy nic or incorrect setup as mentioned before. ask them to swapout the nic and double check the switch settings (they do use managed switches right?) and the nic settings in 2k. hope it gets sorted for you soon

try 66.227.104.128

Don't mind the ping beacuse i'm making downloads..
: ping 66.227.104.128 with 1000 bytes of data :

Reply from 66.227.104.128: bytes=1000 time=260ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=311ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=741ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=751ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=961ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=1031ms TTL=10
Reply from 66.227.104.128: bytes=1000 time=922ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=240ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=441ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=851ms TTL=107
Request timed out.
Reply from 66.227.104.128: bytes=1000 time=380ms TTL=107
Request timed out.
Reply from 66.227.104.128: bytes=1000 time=520ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=791ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=901ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=1022ms TTL=10
Reply from 66.227.104.128: bytes=1000 time=260ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=280ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=251ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=280ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=251ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=290ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=251ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=580ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=370ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=341ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=250ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=250ms TTL=107
Reply from 66.227.104.128: bytes=1000 time=501ms TTL=107


(6% Loss)

its your box theres packet loss even from a box at fdc but not to any other ip .128 is fine .130 is fine do you have some kinda firewall randomly blocking icmp or are you getting real packetloss

it looks more and more likely webdude was right about the mismatched speeds or bad nic, unfortunately this is in their hands not yours. they have to fix it. with all their current downtime i would hope they dont charge your for this month, esp if theyve messed this up as well.

Originally posted by ReZa

...
Netmask:
255.255.248.0
...


OMG... they put all their customers in one giant subnet?!?! No wonder they've had so many problems... just the thought makes me sick to my stomach. :(

I have to say two things:

1-I'm not a direct customer of FDC, I got my dedicated server from Dreamz Solu tions,
When I was in trouble and wanted my IPs after some correspondence, when FDC (petr & Kule) noticed that I'm the authorised ownner, helped me and gave me the new IPs (near 18 hours before) , but it was useless, becuase there is a big packet loss and I cannot use server!

2-Everything shows that the problem is something related to my box connection to server, as netdude & richy said, something related to speed mismatch or similar.

I have sent my 4th email to FDC and another one to Dreamz,(dreamz has also sent emails regarding my issue to FDC)
I don't know why I have not got any answer yet after so many hours!

Is there anybody out there who has any connection with FDC and can help me? or take their attentin to my issue?

Do they have any other email? I contact them by supportfdc@megapathdsl.net
have u got any email from them recently? if you are their friends ,can u tell them my issue?

I would be so thankful because I'm losing all my reputation and business!
Also my advertisement and special report from one of sites hosted at server will be published soon in a computer magazine :(
and I'm really under pressure after one week of sleeplessness and waiting and still not connected!

Thank you for your help,
I just got this reply and everything seems to be ok alothough I have not yet connected to server and just pinged!
---------------------------------------

we switched you to a different port, the problem seems to be gone. If
you
have any more issues please let us know. sorry about slow responce but
we
expcet to be heavily backlogged till sunday

regards

FDCservers