Hello all, I am brand spankin' new here. Hello all, I need your help. I have done CCNA and MCSE classes.

DSL prices getting insane we have decided to use clearwire (stockton, CA). I have found the best location for it and ran ethernet cabling accordingly to where my DSL and router have already been. All is well, for the PCs!!! My mac hates some websites with this isp!!

I still have my dsl until my number is transfered for VOIP. I have connected it directly and ever site works with my mac & PC. I conected it through my router system all sites work, PC and mac. Anything DSL = everything work with a high price.

Now clearwire makes macs look sad. I conect it direct some sites don't work (ex. Digg.com perfect, ups.com no go *gets the title only*, here at macoshints it might get some of the headers of the forum, rarely if ever the body). I have to type this on a PC and it makes me sad.

I tried DHCP all routing (clearwire is DHCP WAN), I tried static LAN and 3 different DNS'es from Clearwire (65.53.96.5 , 4.2.2.1, and 4.2.2.2). The DNS works for some site on the mac and all sites for PC

I have a 20" imac g5 1gb ram. I tried 10.4.6 10.4 and 10.3 in both safari and firefox... AHH

Here is the kicker... lmao no joke we have AOL and we connect to it TCP/IP over clearwire, their brower works on the OS X over all sites... I now have a lame brower doing all sites and safari and firefox doing only some...

Im tired (excuse all the crazy sentences) I never even got close to this kind of crazy "stuff" and I do class b ip/subnet splitting..

Please help and thank you in advance.

Brad W.

To continue...
 

I changed ethernet from 10 100 full duplex half duplex. Changed packet size per send, I turned off IPv6... My posts are full of errors and im sorry. Im tired and it late. I beg for help....


Thank you in advance, im gonna be up all night on this drivin me coo coo.

Brad

If you know how to split a class B network, you've certainly also heard about MTU, it might be related to your problems.

Try some really low value like 1300 and work your way up until things break if you can't figure out the correct value directly.

well harley little to no differnce with the MTU, UPS.com (got a package comin from them today) still timesout after 60 seconds. Yahoo wont come up, ebay rarely, amazon sorta. Digg.com perfect, google.com perfect...

If changing the MTU makes a difference at all, you're probably on the right track.
Detailed, factual report of problems here is likely to produce better results than the massive amount of random changes you made to your setup.

I'm just having a hard time understanding the set up here. Your explanation is all over the place so i'll try to project my assumptions here:
You have a clearwire modem connected to a router which is in turn, connected to some number of nodes. The macs are experiencing errors in loading several sites, however; the PCs are not. If this is the case, then let me make a few additional inquiries.

First, is the router a wireless router or wired? Depending on which, how is each node connected to the router? Does the modem provide DHCP? Do you have DHCP enabled on the router? Do you have any firewalls enabled? If so, exlain. Any other networking information pertinent to this problem is helpful. We always ask that posters provide every possible bit of information that they can think of so as to make our problem-solving process a bit less laborious/mysterious! Cheers.

Wired router. Everything wired. I tried DHCP LAN and Static LAN (Cleawire is DHCP WAN) Both still give me the problem with my mac. Turned all firewalls off and even directly connected the clearwire with no router to the mac, still problems. I tried every different config, and its having to do with how clearwire sends packets my mac doesn't like. The PCs have no problem.

Did you try turing off DHCP in the modem (if available)? Should that not be an option, then you should acquire the relevent logs for the timeout events and post them here. You can get these in the Console which resides in the Utilities folder. You have to do a bit of searching, but any such event is recorded there. Also, have you tried pings, traceroutes, etc. via the Macs? That information could prove useful as well.

Does the fact that if I use AOL for mac os x with our AOL account and going to the sites on aol's browers work fine (ups.com). Does that bring any ideas? Im using their TCP/IP connection over clearwire's and all sites are fine.

We got 2 PCs and one mac, and my mac being the one not working drives me nuts. Also iChat, Yahoo!, etc. work well on the mac. Just HTTP and HTTPS. Also how Digg.com acts like im on a cable modem in speed and ebay.com acts like im on dialup is the craziest thing. With that i tried firefox and safari on 10.4.6 10.4. and 10.3 all act the same. All sites on the PC work equally well. Were getting 858kbps down and 193 up.

I'll get reports for u and do traceroutes, thank u

When you use AOL's service, thats exactly what you are doing. You are connecting to their server, and they going through them onto the Internet. You should still consider posting the relevant logs.

I looked all over in console for anything with the IP address and the domains of the servers im having problems with even when I do it. I looked all over HTTPD and Directory Access. I even looked in every log in the drawer in console app. Just to show I got connections to these sites I did a netstat on my PC

C:\WINMCE|► netstat

Active Connections

Proto Local Address Foreign Address State
TCP LivingRoom:1031 localhost:1032 ESTABLISHED
TCP LivingRoom:1032 localhost:1031 ESTABLISHED
TCP LivingRoom:netbios-ssn 192.168.1.8:49471 ESTABLISHED
TCP LivingRoom:1030 69.90.232.34:27038 ESTABLISHED
TCP LivingRoom:1088 dns.sfo1.speakeasy.net:http ESTABLISHED
TCP LivingRoom:2064 66-42-73-9.stkn.mdsg-pacwest.com:http ESTABLISH
ED
TCP LivingRoom:2065 66-42-73-9.stkn.mdsg-pacwest.com:http ESTABLISH
ED
TCP LivingRoom:2066 66-42-73-9.stkn.mdsg-pacwest.com:http ESTABLISH
ED
TCP LivingRoom:2067 srv.ebayrtm.com:http ESTABLISHED
TCP LivingRoom:2074 66-42-73-9.stkn.mdsg-pacwest.com:http ESTABLISH
ED
TCP LivingRoom:2075 banners.ebay.com:http ESTABLISHED
TCP LivingRoom:2076 banners.ebay.com:http ESTABLISHED
TCP LivingRoom:2077 banners.ebay.com:http ESTABLISHED
TCP LivingRoom:2084 66.102.7.147:http ESTABLISHED
TCP LivingRoom:2085 66.102.7.104:http ESTABLISHED
TCP LivingRoom:2086 www.ups.com:http ESTABLISHED
TCP LivingRoom:2088 www.ups.com:http ESTABLISHED

I will now put the results from my mac in the next post

Here is my results in ping traceroute and port scan to: digg.com ups.com and howardstern.com

Ping has started ...

PING digg.com (64.191.203.30): 56 data bytes
64 bytes from 64.191.203.30: icmp_seq=0 ttl=242 time=57.47 ms
64 bytes from 64.191.203.30: icmp_seq=1 ttl=242 time=54.726 ms
64 bytes from 64.191.203.30: icmp_seq=2 ttl=242 time=48.514 ms
64 bytes from 64.191.203.30: icmp_seq=3 ttl=242 time=69.724 ms
64 bytes from 64.191.203.30: icmp_seq=4 ttl=242 time=48.289 ms

--- digg.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 43.737/54.763/69.724 ms

Ping has started ...

PING www.ups.com.akadns.net (153.2.224.50): 56 data bytes

--- www.ups.com.akadns.net ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss

________________________________________________________________________

Traceroute has started ...

traceroute to digg.com (64.191.203.30), 30 hops max, 40 byte packets
1 66-53-96-2.stk.clearwire-dns.net (66.53.96.2) 98.944 ms 100.381 ms 80.305 ms
2 66-53-96-2.stk.clearwire-dns.net (66.53.96.2) 38.014 ms 128.892 ms 62.815 ms
3 csc6501r-vlan37.stkn.mdsg-pacwest.com (66.52.71.29) 33.716 ms 54.461 ms 67.47 ms
4 csc12001-gig3-1.stkn.mdsg-pacwest.com (64.66.193.193) 31.621 ms 55.683 ms 56.201 ms
5 pos3-2.gw2.sac1.alter.net (208.222.9.53) 56.494 ms 48.252 ms 68.923 ms
6 152.at-5-0-0.xr2.sac1.alter.net (152.63.51.102) 91.724 ms 43.376 ms 44.305 ms
7 0.so-0-0-0.xl2.sac1.alter.net (152.63.54.1) 53.137 ms 124.18 ms 65.658 ms
8 0.so-3-0-0.xl2.scl2.alter.net (152.63.48.94) 67.535 ms 56.851 ms 65.756 ms
9 0.so-7-0-0.br1.scl2.alter.net (152.63.57.101) 73.469 ms 61.978 ms 56.972 ms
10 204.255.173.42 (204.255.173.42) 67.756 ms 82.347 ms 108.697 ms
11 so-1-2-0.bbr1.sanjose1.level3.net (209.244.3.137) 51.066 ms so-1-2-0.bbr2.sanjose1.level3.net (209.244.3.141) 73.121 ms so-1-2-0.bbr1.sanjose1.level3.net (209.244.3.137) 89.474 ms
12 * ge-11-2.ipcolo1.sanjose1.level3.net (4.68.123.169) 57.068 ms ge-7-1.ipcolo1.sanjose1.level3.net (4.68.123.73) 43.697 ms
13 * * *

Traceroute has started ...

traceroute to www.ups.com.akadns.net (153.2.228.50), 30 hops max, 40 byte packets
1 66-53-96-2.stk.clearwire-dns.net (66.53.96.2) 151.859 ms 97.075 ms 34.301 ms
2 66-53-96-2.stk.clearwire-dns.net (66.53.96.2) 55.987 ms 218.315 ms 73.493 ms
3 csc6501r-vlan37.stkn.mdsg-pacwest.com (66.52.71.29) 92.439 ms 104.494 ms 130.275 ms
4 csc12001-gig3-0.stkn.mdsg-pacwest.com (64.66.193.1) 85.465 ms 96.316 ms 70.569 ms
5 pos3-2.gw2.sac1.alter.net (208.222.9.53) 68.27 ms 88.378 ms 79.784 ms
6 152.at-6-0-0.xr1.sac1.alter.net (152.63.51.94) 70.799 ms 96.933 ms 113.638 ms
7 0.so-0-0-0.xl1.sac1.alter.net (152.63.53.237) 117.034 ms 140.939 ms 129.067 ms
8 0.so-3-0-0.xl1.scl2.alter.net (152.63.48.90) 73.813 ms 57.907 ms 103.999 ms
9 0.so-6-0-0.br1.scl2.alter.net (152.63.57.49) 107.501 ms 70.46 ms 96.644 ms
10 eli-gw.abnva.ip.att.net (192.205.32.73) 92.606 ms 88.576 ms 119.341 ms
11 tbr2-p011901.sffca.ip.att.net (12.123.12.21) 202.408 ms 230.591 ms 193.827 ms
12 tbr1-cl2.sl9mo.ip.att.net (12.122.10.41) 183.521 ms 232.453 ms 235.198 ms
13 tbr2-cl24.sl9mo.ip.att.net (12.122.9.142) 245.425 ms 221.493 ms 238.599 ms
14 tbr2-cl29.attga.ip.att.net (12.122.10.137) 278.511 ms 256.083 ms 291.639 ms
15 gbr1-p20.attga.ip.att.net (12.122.12.34) 215.291 ms 213.135 ms 264.668 ms
16 12.123.197.185 (12.123.197.185) 233.921 ms 170.858 ms 204.587 ms
17 12.118.184.50 (12.118.184.50) 219.812 ms 195.826 ms 204.948 ms
18 * * *

Traceroute has started ...

traceroute to howardstern.com (64.235.250.50), 30 hops max, 40 byte packets
1 66-53-96-2.stk.clearwire-dns.net (66.53.96.2) 181.942 ms 92.293 ms 63.764 ms
2 66-53-96-2.stk.clearwire-dns.net (66.53.96.2) 29.762 ms 30.319 ms 32.841 ms
3 csc6501r-vlan37.stkn.mdsg-pacwest.com (66.52.71.29) 30.809 ms 31.376 ms 28.555 ms
4 csc12002-gig3-1.stkn.mdsg-pacwest.com (64.66.193.197) 52.237 ms 24.136 ms 32.728 ms
5 66-162-144-89.static.twtelecom.net (66.162.144.89) 40.814 ms 27.829 ms 33.887 ms
6 core-01-ge-3-1-1-509.okld.twtelecom.net (66.192.250.69) 28.572 ms 28.702 ms 36.753 ms
7 core-02-so-1-1-0-0.lsag.twtelecom.net (66.192.251.10) 41.482 ms 55.553 ms 57.295 ms
8 peer-01-so-0-0-0-0.lsag.twtelecom.net (66.192.251.25) 56.722 ms 44.323 ms 41.349 ms
9 206.223.123.62 (206.223.123.62) 47.324 ms 46.282 ms 41.346 ms
10 xe1-0.cr01.lax02.mzima.net (64.235.224.182) 67.294 ms 41.805 ms 45.26 ms
11 pos0-4.ar02.lax02.mzima.net (64.235.224.187) 42.383 ms 51.487 ms 47.651 ms
12 fe0-dreamtank.cust.lax02.mzima.net (216.193.192.78) 41.725 ms 66.074 ms 46.128 ms
13 64.235.250.18 (64.235.250.18) 67.171 ms 148.387 ms 45.363 ms
14 64.235.250.50 (64.235.250.50) 42.391 ms 89.808 ms 81.844 ms
15 64.235.250.50 (64.235.250.50) 100.293 ms 164.94 ms 104.252 ms
16 64.235.250.50 (64.235.250.50) 54.998 ms 86.585 ms *
17 64.235.250.50 (64.235.250.50) 88.476 ms 82.419 ms 45.548 ms
18 64.235.250.50 (64.235.250.50) 84.464 ms 111.709 ms 121.103 ms
19 64.235.250.50 (64.235.250.50) 73.967 ms * 94.285 ms
20 64.235.250.50 (64.235.250.50) 117.875 ms 57.014 ms 98.703 ms
21 64.235.250.50 (64.235.250.50) 108.626 ms 63.097 ms 111.428 ms
22 * 64.235.250.50 (64.235.250.50) 108.198 ms 146.548 ms
23 64.235.250.50 (64.235.250.50) 96.213 ms 41.697 ms 54.138 ms
24 64.235.250.50 (64.235.250.50) 54.004 ms 202.128 ms *
25 64.235.250.50 (64.235.250.50) 238.068 ms 137.068 ms 61.792 ms
26 * 64.235.250.50 (64.235.250.50) 176.729 ms 69.893 ms
27 64.235.250.50 (64.235.250.50) 133.712 ms 88.343 ms 101.037 ms
28 64.235.250.50 (64.235.250.50) 98.338 ms 69.223 ms 84.807 ms
29 64.235.250.50 (64.235.250.50) 95.893 ms * 96.922 ms
30 64.235.250.50 (64.235.250.50) 48.072 ms 84.335 ms 71.042 ms

________________________________________________________________________

Port Scan has started ... *I started digg. com*

Port Scanning host: 64.191.203.30

Open Port: 80 http
Port Scan has completed ...

Port Scan has started ... *I started ups.com*

Port Scanning host: 153.2.224.50

Open Port: 80 http
Port Scan has completed ... *I went back to ping and still get 100% packet loss*
*Safari says: Safari could not open the page "http://www.ups.com/" after trying for 60 seconds*

By logs, I meant the logs from your "Console" when you try to connect to the sites in question, however; these will give some insight. I'll get back to you once i give them a once over.

Well, it looks like those specific site may filter ICMPs. So the Pings, traceroutes, and port scans may produce useless information. The best way to find out whats going on is to post the console logs that show what happens when you try to connect to those sites.

well i got a voip adapter it does DHCP routing so i tossed my router and use the voip adapter for routing now all the sites work... I have no idea why a router (linksys) would make mac's not work but pc's ok.. thank you for your time, seriously. Thank you bored28

That is strange. I would just be curious to find out what exactly is causing the Linksys to behave in such a way. If you do happen to revisit this problem, I would be very interested to hear what your troubleshooting process uncovers.

Well the loading is sorta laggy on the mac. Safari and Firefox draw immediately on a mac even if all items aren't loaded and on windows it waits till nearly all items are loaded in my opinion. Another thing is there is about an 80 foot run of CAT 5 from the clearwire modem to my computer, yet the same stretch applies to our other computer an XP machine runs great right now. Maybe XP handles TCP stacks better?!?

I do have another router I never test because it was so lame it couldn't push the single far enough to the switch, only the linksys could.

Clearwire to linksys => 70 ft span to a passive hub (not a switch, lame I know got no $$ right now.) then 10 ft to my Mac and then the same to another PC. it clearly is fine in 10baseT standards, I got no clue. Hell maybe the voip adapter is taking clearwire's shaped packets and giving them longer time to live lol I have no clue. I know it works now!

P.S. Finally typing this on my mac!!!! Thank the lord!!!!

What model of linksys router do you own? I'm fairly certain that it has nothing to do with the way Macs handle TCP/IP stacks because if that were the case, everyone would be having problems connecting to wireless access points. It sounds like a router misconfiguration or just a router problem in general.

Similar Issue with Netgear WGR614v4 Wireless Router
 

Hi,

I just signed up for Clearwire and had a very similar issue. This Thread helped me focus on the Router that is connected to my Clearwire modem, so I thought I would post how I solved the problem in case anyone else happens upon this thread. (This maybe a different issue than the original posters problem with the LinkSys router).

The specific problem I had was with DNS lookups continuously failing. (I apologize that this is not OS specific, it would happen on Windows XP and Ubuntu Fiesty Fawn. I don't think it was OS related ) I would load a website in IE 6, IE 7, or Firefox 2.0.0.7 and the website would usually not load (sometimes it did though). After hitting F5 to reload the page a random number of times the website would load. Download times were fine after a connection was open and DNS was resolved. Doing something like "ping www.yahoo.com" would fail completely the first random number of times as well.

It turns out that upgrading the firmware on my Netgear WGR614v4 Wireless Router solved all my issues. Netgear documents the bugs that are fixed with the firmware upgrade, and I believe that it is a DynDNS fix, preventing it from failing sometimes, that solved my issue. The specific firmware version I upgraded to is "WGR614v4 Firmware Version 5.0_07".

http://kbserver.netgear.com/products/wgr614v4.asp

I found it strange that this issue didn't come up when I was using Comcast Cable. Maybe they have a different DNS setup?

Anyways, hope this helps someone.

A coworker just signed up for Clearwire at home and is completely unable to connect to our company's Mac Server (10.4.10).
She gets an operation failed message each time she tries to connect via afp. In the server admin utility, it show her connection as disabled/asleep. Disconnecting her so she can attempt to reconnect ends up the same way.
I am not sure what to look at since the modem is wireless, and she has no router.

She has no problems sending e-mail or connecting to any websites. So the internet connection is working, just not the ability to connect to our server (which is the most important piece).

Any ideas? :(

If the modem is wireless, it probably contains a router. See if she can get to a setup/configuration page.

I too have this same problem, spent 2.25 hours on cust. service with Clearwire and they started to think blocked ports that the OSX server uses in its AFP Connection setup. I looked and don't see which port is supposed to be used?! Clearwire's modem doesn't have a router (I believe) I do have a Linksys wireless router I use for my laptop. However I ruled out the router since I plug the Clearwire modem directly into the computer (laptop or tower) and neither work. However I bring my laptop over to my neighbors DSL service and can access the server no problem.

not necessarily. I use the same system in Canada provided by Rogers. The internet access is wireless, and the accesspoint provided by them does not contain or serve as a router. It has only one ethernet port, and it is not possible to connect to it from your computer wirelessly. It only connects to the service provider wirelessly.

If you want more than one computer in your home to have internet access, then you need to have a Mac share its access, or buy a router.

Likely it is a problem of blocked ports. Apple File Sharing uses port 548, hence the website www.AFP548.com