Router vs Usb

Roman4604, many of us have found opendns to be faster and I used to get webpages timing out with iburst dns settings on the 1st click, now with opendns all those problems have disapeared.

The same with Verizon. The pings are much more constant than those of iBurst and pages don't time out.
Ok whatever works for you guys. I've never had page timeouts (due to dns) and my dns resolution has always been pretty snappy.
 
Roman why don't you do a ping with the iBurst DNS and then do one with Verizon. The Verizon IP is bound to give you a better result.
 
MrH, using it directly with the ethernet cable to my pc now. It's not slow at all.
 
Jhbgirl, I take it if you connect all your PCs' to your router they can all communicate with each other, if not then you need to setup your router to assign internal IPs' to all the PCs' in that network.

I don't know the setup for the Belkin router but someone else here might be able to help with that.
 
Ok so now we know it works if you connect the modem directly to your PC with the ethernet cable, we also now know that all the PCs' can communicate with each other when connected to the router.
I take it that if you connect the modem to the other PCs' that they will also work on the internet, if this is so then there has to be some setting in the router setup thats not set correctly.

I can't remember which member here said he also had a Belkin router but hopefully he replies as to what you need to set and where those settings are.
Maybe do a search through this thread and see if you can PM him about it.
I can't do the search as it's crawling here in CT and I'm getting many timeouts while posting here.
 
Jhbgirl, this might be a dumb question but are the PCs' connected to the router with ethernet cables or are they connected to it through a wireless network?
 
Connected to the router with ethernet cables.

I tried the ethernet directly from the modem again and its not working and giving similar results to the router connection. Could the ethernet port on the modem be broken?
 
Did you use the same ethernet cable that you used the last time when it worked connected directly to the PC?
Some network cables have their connections reversed as a crossover connection, just check the cable wire colours where they enter the connecting plugs at the ends of the cable.
 
If you are sure that the cable you are trying now is the same cable that worked the last time and now it does not, then try another cable first before worrying about the modem socket been faulty.
Just make sure the same colour wires go to the same pins of the cable plugs as the cable that worked the first time.

If it is the oppersite connection you won't damage anything but it will not work.
 
Roman why don't you do a ping with the iBurst DNS and then do one with Verizon. The Verizon IP is bound to give you a better result.
No real diffs for me ...


C:\>ping -n 10 196.7.142.132

Pinging 196.7.142.132 with 32 bytes of data:

Reply from 196.7.142.132: bytes=32 time=164ms TTL=58
Reply from 196.7.142.132: bytes=32 time=108ms TTL=58
Reply from 196.7.142.132: bytes=32 time=263ms TTL=58
Reply from 196.7.142.132: bytes=32 time=103ms TTL=58
Reply from 196.7.142.132: bytes=32 time=263ms TTL=58
Reply from 196.7.142.132: bytes=32 time=87ms TTL=58
Reply from 196.7.142.132: bytes=32 time=93ms TTL=58
Reply from 196.7.142.132: bytes=32 time=266ms TTL=58
Reply from 196.7.142.132: bytes=32 time=76ms TTL=58
Reply from 196.7.142.132: bytes=32 time=231ms TTL=58

Ping statistics for 196.7.142.132:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 76ms, Maximum = 266ms, Average = 165ms

C:\>ping -n 10 196.30.31.193

Pinging 196.30.31.193 with 32 bytes of data:

Reply from 196.30.31.193: bytes=32 time=215ms TTL=251
Reply from 196.30.31.193: bytes=32 time=305ms TTL=251
Reply from 196.30.31.193: bytes=32 time=190ms TTL=251
Reply from 196.30.31.193: bytes=32 time=191ms TTL=251
Reply from 196.30.31.193: bytes=32 time=130ms TTL=251
Reply from 196.30.31.193: bytes=32 time=140ms TTL=251
Reply from 196.30.31.193: bytes=32 time=46ms TTL=251
Reply from 196.30.31.193: bytes=32 time=189ms TTL=251
Reply from 196.30.31.193: bytes=32 time=99ms TTL=251
Reply from 196.30.31.193: bytes=32 time=218ms TTL=251

Ping statistics for 196.30.31.193:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 305ms, Average = 172ms
 
JHBgirl: Try run a continual ping on www.iburst.co.za
Ie start->run-> type ping www.iburst.co.za -t -l1

Sometimes this helps increase your presense to the tower and thus your connection. On usb I found this made little/no difference but on ethernet it made a huge difference for me.
 
MrH, yes the cable/s are fine, they have been working up until sunday, so did the PPPoE. I'm going to try and get iBurst to exchange the modem. I'm convinced it's the ethernet port.
 
Top
Sign up to the MyBroadband newsletter
X