Slow connection to router

womble12345

macman wrote: »

If the friend's machine using the same router gives nearly 14MBps, then clearly it's not a line or router issue-the problem is your PC, or it's network connection.
Can you ping the router from your PC?
Have you tried resetting the IP address?
From the command prompt type in- "ipconfig /release", then "ipconfig /renew"

I can ping the router fine, I can also ping my friends pc.

I tried renewing ip address but it didnt help at all.

womble12345

Trinitrotoluene wrote: »

It sounds like you may be using old entries from your previous network.

See here http://www.wikihow.com/Set-up-DHCP-Network-Settings-on-Windows-XP and follow these steps.

I tried this and also no joy.

womble12345

Date/TimeFacilitySeverityMessageJan 1 00:00:24usercritkernel: eth0 Link UP. Jan 1 00:00:24usercritkernel: ADSL G.994 training Jan 1 00:00:24usercritkernel: ADSL G.992 started Jan 1 00:00:24usercritkernel: ADSL G.992 channel analysis Jan 1 00:00:27usercritkernel: ADSL G.992 message exchange Jan 1 00:00:28usercritkernel: ADSL link down Jan 1 00:00:33usercritkernel: ADSL G.994 training Jan 1 00:00:40usercritkernel: ADSL G.992 started Jan 1 00:00:44usercritkernel: ADSL G.992 channel analysis Jan 1 00:00:51usercritkernel: ADSL link up, interleaved, us=1020, ds=17459 Jan 1 00:01:17daemoncritpppd[531]: PPP LCP UP. Jan 1 00:01:17daemoncritpppd[531]: Received valid IP address from server. Connection UP. Jan 1 00:01:45useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=201.43.248.70 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=114 ID=39412 DF PROTO=TCP SPT=1829 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 00:01:48useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=201.43.248.70 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=114 ID=39651 DF PROTO=TCP SPT=1829 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 00:02:14useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=201.43.175.121 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=114 ID=21159 DF PROTO=TCP SPT=4175 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 00:02:16useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=201.43.175.121 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=114 ID=21424 DF PROTO=TCP SPT=4175 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 00:10:07useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=120.50.111.49 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=42 ID=47565 DF PROTO=TCP SPT=53704 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 00:13:36useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=122.95.16.122 DST=79.71.118.61 LEN=64 TOS=0x00 PREC=0x00 TTL=45 ID=30401 DF PROTO=TCP SPT=2168 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 00:24:42useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=83.139.165.176 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=1927 DF PROTO=TCP SPT=1117 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 00:33:07useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=190.6.202.90 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=115 ID=54496 DF PROTO=TCP SPT=4212 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0 Jan 1 00:47:15useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=70.161.82.37 DST=79.71.118.61 LEN=52 TOS=0x00 PREC=0x00 TTL=113 ID=9681 DF PROTO=TCP SPT=61934 DPT=20909 WINDOW=8192 RES=0x00 SYN URGP=0 Jan 1 00:54:07useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=151.68.159.24 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=51275 DF PROTO=TCP SPT=4504 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 01:14:21useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=46.73.42.48 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=120 ID=1887 DF PROTO=TCP SPT=3574 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 01:14:24useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=46.73.42.48 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=120 ID=2200 DF PROTO=TCP SPT=3574 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 01:23:17useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=126.14.225.137 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=111 ID=38804 DF PROTO=TCP SPT=3099 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 01:32:36useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=41.189.17.210 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=2189 DF PROTO=TCP SPT=3390 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 01:42:59useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=79.45.209.221 DST=79.71.118.61 LEN=64 TOS=0x00 PREC=0x00 TTL=35 ID=859 DF PROTO=TCP SPT=9827 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 01:52:07useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=189.110.218.245 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=114 ID=56774 DF PROTO=TCP SPT=2838 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 02:03:22useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=116.249.180.104 DST=79.71.118.61 LEN=60 TOS=0x00 PREC=0x00 TTL=47 ID=55287 DF PROTO=TCP SPT=32929 DPT=22 WINDOW=5808 RES=0x00 SYN URGP=0 Jan 1 02:17:23useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=82.233.253.25 DST=79.71.118.61 LEN=64 TOS=0x00 PREC=0x00 TTL=117 ID=29273 DF PROTO=TCP SPT=8367 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 02:23:03useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=80.210.8.168 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=16566 DF PROTO=TCP SPT=4283 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 02:42:13useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=187.14.126.72 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=108 ID=63438 DF PROTO=TCP SPT=4618 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 02:42:16useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=187.14.126.72 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=108 ID=63758 DF PROTO=TCP SPT=4618 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 03:00:40useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=62.118.157.85 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=117 ID=56108 DF PROTO=TCP SPT=2846 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 03:04:31useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=189.51.240.245 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=117 ID=22246 DF PROTO=TCP SPT=2050 DPT=445 WINDOW=64380 RES=0x00 SYN URGP=0 Jan 1 03:12:30useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=98.80.141.249 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=54163 DF PROTO=TCP SPT=3958 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0 Jan 1 03:27:01useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=79.71.127.66 DST=79.71.118.61 LEN=64 TOS=0x00 PREC=0x00 TTL=47 ID=52839 DF PROTO=TCP SPT=3227 DPT=135 WINDOW=65535 RES=0x00 SYN URGP=0 Jan 1 03:32:44useralertkernel: Intrusion -> IN=ppp_0_38_1 OUT= MAC= SRC=217.203.208.182 DST=79.71.118.61 LEN=48 TOS=0x00 PREC=0x00 TTL=112 ID=5810 DF PROTO=TCP SPT=3028 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0

asbokid

cast your pings further afield...

try pinging 209.85.147.106 .. that's one of the IP addresses that resolves from https://www.google.com

if pinging by IP address works, then try pinging https://www.google.com ..

if pinging https://www.google.com doesn't work, then it points to a nameserver problem on your PC.

GunJack

...or the DNS isn't set on your pc to the address of the router. Check the wifi adapter's properties - the primary DNS server address should be the IP address of the router, e.g. 192.168.x.x

asbokid

Maybe I just buy crap routers but I've not had one that runs its own DNS service..

Usually the router obtains nameserver details from the peer, i.e. from the ISP's pppd server during the establishment of the PPP link layer.

However the broadband router does run a DHCP server for clients on the local network.

It is through the responses to queries to that DHCP server that the local clients obtain the IP addresses for the ISP's nameservers.

As an aside...

Three (the 3G operator) has had a buggy PPP implementation since launch. Every so often the Three pppd server 'forgets' to report the IP addresses of its nameservers when you connect from a 3G dongle. You've got full connectivity but no name resolution. I gave up in the end and statically entered the nameserver IP addresses. In Linux if you run pppd in debug and verbose mode the fault is clearly shown as being with Three. Since pppd is the standard Linux/Unix daemon, there are probably quite a few other ISPs running buggy versions which are causing the same problem.

womble12345

I have now looked into this further. It seems on my PC some websites are fine and yet some time-out, yet on my friends PC that is wired to the same router all websites are fine.
As an example forums.moneysavingexpert.com is fine yet www.metoffice.gov.uk times out. Pings to both are fine though.

I have looked into DNS servers but my settings are the same as the other PC (both use automatic DNS servers).
Anyone got any ideas?

Hammyman

Open up a command prompt in Windows. Type in the following:

ipconfig /flushdns

This will wipe all cached DNS requests on your PC.

Toxteth_OGrady

Java problem on OP's machine maybe?

womble12345

Hammyman wrote: »

Open up a command prompt in Windows. Type in the following:

ipconfig /flushdns

This will wipe all cached DNS requests on your PC.

Thanks for the suggestion but I tried this but it didnt help.
Thanks