My dad lives out in the country where Comcast refuses to run a wire (they want $30,000 to run a line) and DSL is too far away from the CO for service. SO we connect to a local ISP via a wireless setup and then they connect us to the internent.
The local setup is a number of PC and Mac machines that connect through an Apple Airport. The Main Airport is connected to a big directional antenna to get a signal into the house. There is an office in the garage with a Mac and an XP box. The Airport uses two Airport express repeaters to get a signal from the edge of the house and then throughout the house. Nothing has WEP.
The problem is that we get verry slow conncections to a database online. The data base is at: https://sso.construction.com/SingleSign...Manager.aspx?ReturnUrl=%2fDefault.aspx
We are trying to decide why the slow service to that site. In general I realize due to the wireless connection we can't expect gaming pings but we should get decent connections for web use. However, the entire wireless network is quite unstable and shared bandwidth between us and a number of other homes. The worst performance is during work hours and the best performance is around 4:00 am.
Here are some tracerouts and pings:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Evan Adams>tracert www.network.construction.com this is my dads database
Tracing route to www.network.construction.com [12.163.148.170]
over a maximum of 30 hops:
1 2 ms 4 ms 3 ms 192.168.1.1
2 350 ms 18 ms 52 ms nb-ii.vom.com [207.212.58.1]
3 466 ms 292 ms 246 ms 69.108.221.109
4 449 ms 163 ms 14 ms bb1-p6-0.pltnca.sbcglobal.net [151.164.191.242]
5 142 ms 29 ms 14 ms bb1-p3-0.crsfca.sbcglobal.net [151.164.190.85]
6 653 ms 26 ms 31 ms ex1-p3-0.eqsjca.sbcglobal.net [151.164.41.101]
7 288 ms * 473 ms gar7-p390.sffca.ip.att.net [12.122.79.101]
8 163 ms 295 ms 354 ms tbr1010201.sffca.ip.att.net [12.122.85.130]
9 560 ms 353 ms 503 ms tbr1-cl1.cgcil.ip.att.net [12.122.10.5]
10 330 ms 363 ms 263 ms tbr1-cl14.n54ny.ip.att.net [12.122.10.1]
11 267 ms 182 ms 676 ms gar1-p310.nw2nj.ip.att.net [12.123.219.130]
12 * 394 ms 84 ms 12.119.12.82
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\Documents and Settings\Evan Adams>ping www.network.construction.com
Pinging www.network.construction.com [12.163.148.170] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 12.163.148.170:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Documents and Settings\Evan Adams>tracert 209.191.93.52 This is Yahoo
Tracing route to f1.www.vip.mud.yahoo.com [209.191.93.52]
over a maximum of 30 hops:
1 4 ms 4 ms 4 ms 192.168.1.1
2 176 ms 171 ms 594 ms nb-ii.vom.com [207.212.58.1]
3 340 ms 280 ms 325 ms 69.108.221.109
4 217 ms 608 ms 672 ms bb1-p6-0.pltnca.sbcglobal.net [151.164.191.242]
5 360 ms 185 ms 226 ms bb1-p3-0.crsfca.sbcglobal.net [151.164.190.85]
6 298 ms 287 ms 116 ms ex1-p14-0.eqsjca.sbcglobal.net [151.164.41.10]
7 34 ms 115 ms 13 ms asn10310-yahoo-10g.eqsjca.sbcglobal.net [151.164
.248.58]
8 187 ms 195 ms 150 ms so-0-0-0.pat2.da3.yahoo.com [216.115.101.139]
9 132 ms 100 ms 249 ms ge-1-1-0-p121.msr1.mud.yahoo.com [216.115.104.91
]
10 270 ms 373 ms 203 ms te-9-1.bas-c1.mud.yahoo.com [68.142.193.9]
11 142 ms 205 ms 211 ms f1.www.vip.mud.yahoo.com [209.191.93.52]
Trace complete.
C:\Documents and Settings\Evan Adams>ping 209.191.93.52
Pinging 209.191.93.52 with 32 bytes of data:
Reply from 209.191.93.52: bytes=32 time=73ms TTL=48
Reply from 209.191.93.52: bytes=32 time=370ms TTL=47
Reply from 209.191.93.52: bytes=32 time=321ms TTL=47
Reply from 209.191.93.52: bytes=32 time=166ms TTL=47
Ping statistics for 209.191.93.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 370ms, Average = 232ms
Can anyone help? Was considering getting rid of the airport but I am not confident that the airport is my problem.
The local setup is a number of PC and Mac machines that connect through an Apple Airport. The Main Airport is connected to a big directional antenna to get a signal into the house. There is an office in the garage with a Mac and an XP box. The Airport uses two Airport express repeaters to get a signal from the edge of the house and then throughout the house. Nothing has WEP.
The problem is that we get verry slow conncections to a database online. The data base is at: https://sso.construction.com/SingleSign...Manager.aspx?ReturnUrl=%2fDefault.aspx
We are trying to decide why the slow service to that site. In general I realize due to the wireless connection we can't expect gaming pings but we should get decent connections for web use. However, the entire wireless network is quite unstable and shared bandwidth between us and a number of other homes. The worst performance is during work hours and the best performance is around 4:00 am.
Here are some tracerouts and pings:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Evan Adams>tracert www.network.construction.com this is my dads database
Tracing route to www.network.construction.com [12.163.148.170]
over a maximum of 30 hops:
1 2 ms 4 ms 3 ms 192.168.1.1
2 350 ms 18 ms 52 ms nb-ii.vom.com [207.212.58.1]
3 466 ms 292 ms 246 ms 69.108.221.109
4 449 ms 163 ms 14 ms bb1-p6-0.pltnca.sbcglobal.net [151.164.191.242]
5 142 ms 29 ms 14 ms bb1-p3-0.crsfca.sbcglobal.net [151.164.190.85]
6 653 ms 26 ms 31 ms ex1-p3-0.eqsjca.sbcglobal.net [151.164.41.101]
7 288 ms * 473 ms gar7-p390.sffca.ip.att.net [12.122.79.101]
8 163 ms 295 ms 354 ms tbr1010201.sffca.ip.att.net [12.122.85.130]
9 560 ms 353 ms 503 ms tbr1-cl1.cgcil.ip.att.net [12.122.10.5]
10 330 ms 363 ms 263 ms tbr1-cl14.n54ny.ip.att.net [12.122.10.1]
11 267 ms 182 ms 676 ms gar1-p310.nw2nj.ip.att.net [12.123.219.130]
12 * 394 ms 84 ms 12.119.12.82
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\Documents and Settings\Evan Adams>ping www.network.construction.com
Pinging www.network.construction.com [12.163.148.170] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 12.163.148.170:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Documents and Settings\Evan Adams>tracert 209.191.93.52 This is Yahoo
Tracing route to f1.www.vip.mud.yahoo.com [209.191.93.52]
over a maximum of 30 hops:
1 4 ms 4 ms 4 ms 192.168.1.1
2 176 ms 171 ms 594 ms nb-ii.vom.com [207.212.58.1]
3 340 ms 280 ms 325 ms 69.108.221.109
4 217 ms 608 ms 672 ms bb1-p6-0.pltnca.sbcglobal.net [151.164.191.242]
5 360 ms 185 ms 226 ms bb1-p3-0.crsfca.sbcglobal.net [151.164.190.85]
6 298 ms 287 ms 116 ms ex1-p14-0.eqsjca.sbcglobal.net [151.164.41.10]
7 34 ms 115 ms 13 ms asn10310-yahoo-10g.eqsjca.sbcglobal.net [151.164
.248.58]
8 187 ms 195 ms 150 ms so-0-0-0.pat2.da3.yahoo.com [216.115.101.139]
9 132 ms 100 ms 249 ms ge-1-1-0-p121.msr1.mud.yahoo.com [216.115.104.91
]
10 270 ms 373 ms 203 ms te-9-1.bas-c1.mud.yahoo.com [68.142.193.9]
11 142 ms 205 ms 211 ms f1.www.vip.mud.yahoo.com [209.191.93.52]
Trace complete.
C:\Documents and Settings\Evan Adams>ping 209.191.93.52
Pinging 209.191.93.52 with 32 bytes of data:
Reply from 209.191.93.52: bytes=32 time=73ms TTL=48
Reply from 209.191.93.52: bytes=32 time=370ms TTL=47
Reply from 209.191.93.52: bytes=32 time=321ms TTL=47
Reply from 209.191.93.52: bytes=32 time=166ms TTL=47
Ping statistics for 209.191.93.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 370ms, Average = 232ms
Can anyone help? Was considering getting rid of the airport but I am not confident that the airport is my problem.