A good friend of mine is having a rather peculiar problem. He can browse the net, except for a few sites, one of them being a very reliable site, the danish railway's main site, which works perfectly for everybody else on other computers. So we do know that the problem is that his computer, regardless of internet connection cannot connect to these sites. The pages respond with timeout in the browser. He can ping them without any problems. The PC has the problem even when connected to a different ISP.
First I did a router check when I was there. Everything was fine. I did a general DNS-check (checking the hosts-file for changes, manually putting the ip of the railway site in the browser which did not work etc). I had him then do a HijackThis! report which was fine as well. He then did a virus scan with various programs which turned out fine as well. He installed firefox to see if it was an IE problem. It was not. We then did some other tests which I am too tired to remember :blush:
It is only a few sites. They time out from the browser. Any ideas?
PS. There are some browsing problems in general now, some pages need to be refreshed more than once to work, but I am sure that is with his brand-new line and a rather unknown ISP. The last place he used the PC, in the same config, there was only the problem with these few sites.
EDIT: Oh yeah, we tried to do a fresh Java-installation, checking for flashplayer problems and so on.
Try flushing your dns cache, IPCONFIG /FLUSHDNS. Check you've got a valid DNS server configured on the PC or router.
Quote from: BigFatCat;177341Try flushing your dns cache, IPCONFIG /FLUSHDNS. Check you've got a valid DNS server configured on the PC or router.
I had him do that, but to no avail. However, by entering the ip of the site directly in the browser he should bypass the DNS-server and since that does not work either I do believe the problem is caused by something else. But I am kinda lost here...
Also - we have solved the refresh problem, so only this problem with a few sites.
Can it be browser-related somehow, or something that is underlying to browsers in general?
Look for any funny routing by typing:
route print
in a CMD window. A route print for me gives:
QuoteC:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 16 e6 5b 86 de ...... Marvell Yukon 88E8053 PCI-E Gigabit Ethernet
troller - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.5 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.5 192.168.1.5 10
192.168.1.5 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.1.255 255.255.255.255 192.168.1.5 192.168.1.5 10
224.0.0.0 240.0.0.0 192.168.1.5 192.168.1.5 10
255.255.255.255 255.255.255.255 192.168.1.5 192.168.1.5 1
Default Gateway: 192.168.1.1
===========================================================================
Persistent Routes:
None
C:\>
just copy the output here if you're not up to speed on inspecting the results and we'll check it out for you.
no chance it's a timeout setting that's been set too low? Otherwise BB's posts looks suitably technical to do something useful - would trying to perform a tracert to these sites (particularly the intermittent ones) help?
Does the problem occur at his house - could it be an underlying network issue in the area where he lives - has the pc been tested while on the same network as one that works - perhaps take a laptop round with a flushed DNS etc and see if it can connect through his router/modem?
Quote from: BlueBall;177352Look for any funny routing by typing:
route print
in a CMD window. A route print for me gives:
just copy the output here if you're not up to speed on inspecting the results and we'll check it out for you.
The result is identical to yours BB :sad:
Quote from: suicidal_monkey;177371Does the problem occur at his house - could it be an underlying network issue in the area where he lives - has the pc been tested while on the same network as one that works - perhaps take a laptop round with a flushed DNS etc and see if it can connect through his router/modem?
No other PC has been tested on the network, although we are working on it. However, the PC did the same at his old place (completely different area and another ISP)
quote=delanvital;177447]The result is identical to yours BB :sad:[/quote]
Thats good. it means your routing hasnt been hijacked. Now, can you check the contents of some files:
Go to C:\WINDOWS\system32\drivers\etc\
and open hosts in notepad.
Here is my hosts file:
127.0.0.1 localhost
The file will prob contain lots of other lines all starting with # which basically means those lines are remarked out and don't do anything.
Can you check to see what is in the hosts file?
Quote from: BlueBall;177454Can you check to see what is in the hosts file?
See top post - I've already been there :)
Quote from: delanvital;177456See top post - I've already been there :)
That was quick :blush:
My next step if it was mine would be to try a different network card.
He did a couple of tracerts and now this is getting weird, or interesting, depending on how you see it. He did two trace routes. First this one:
----
Microsoft Windows XP [version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator.NUITARI> tracert www.elitedaters.com (http://www.elitedaters.com)
Sporer rute til www.elitedaters.com (http://www.elitedaters.com) [81.19.228.34]
over et maksimum af 30 hop:
1 <1 ms <1 ms <1 ms 192.168.1.254
2 26 ms 26 ms 26 ms 1.16.185.213.dk-bot.res.dyn.perspektivbredband.n
et [213.185.16.1]
3 26 ms 27 ms 26 ms kbhn-cdix-pr0-gi0-1-509.perspektivbredband.net [
213.185.31.194]
4 27 ms 26 ms 27 ms jay.net.dix.dk [192.38.7.66]
5 28 ms 29 ms 27 ms 81.7.154.9
6 29 ms 30 ms 29 ms web1.elitedaters.com [81.19.228.34]
Sporing fuldført.
C:\Documents and Settings\Administrator.NUITARI>
Note, that this site does still not work in the browser! The interesting find on that listing is jay.net.dix.dk - it is part of the network at the technical university where he used to live and route his data through. Could there be some remnants from that setup somewhere? I do not know if that site worked from the university network.
---
The other site - the railway one - times out. And please note, that this PC times out on this site from more than one ISP and location (!) The attempt at trace route is here:
Microsoft Windows XP [version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator.NUITARI>tracert www.dsb.dk (http://www.dsb.dk)
Sporer rute til www.dsb.dk (http://www.dsb.dk) [193.28.147.158]
over et maksimum af 30 hop:
1 <1 ms <1 ms <1 ms 192.168.1.254
2 26 ms 26 ms 26 ms 1.16.185.213.dk-bot.res.dyn.perspektivbredband.n
et [213.185.16.1]
3 26 ms 27 ms 26 ms kbhn-cdix-pr0-gi0-0-509.perspektivbredband.net [
213.185.31.54]
4 27 ms 27 ms 27 ms 192.38.7.43
5 28 ms 28 ms 27 ms 192.38.7.80
6 28 ms 28 ms 28 ms g0-1-50-ar5.CPH.router.colt.net [80.80.0.170]
7 33 ms 30 ms 31 ms 80.80.2.22
8 * * * Anmodning fik timeout.
9 * * * Anmodning fik timeout.
10 * * * Anmodning fik timeout.
11 * * * Anmodning fik timeout.
12 * * * Anmodning fik timeout.
13 * * * Anmodning fik timeout.
14 * * * Anmodning fik timeout.
15 * * * Anmodning fik timeout.
16 * * * Anmodning fik timeout.
17 * * * Anmodning fik timeout.
18 * * * Anmodning fik timeout.
19 * * * Anmodning fik timeout.
20 * * * Anmodning fik timeout.
21 * * * Anmodning fik timeout.
22 * * * Anmodning fik timeout.
23 * * * Anmodning fik timeout.
etc.
This could also be due to some bad routing, i.e. the same problem as the frist tracert. Any clever thoughts? :blink:
Has he got any proxies running in the browsers?
Check Tools // Internet Options // Connections in MSIE and see if there are any old connections in there.
Additionally, click on LAN settings and see if a proxy has been specified.
Quote from: GhostMjr;177460Has he got any proxies running in the browsers?
When he was at the uni he did use some proxies. But he says everything is gone now. It seems to be correct I guess, since "just about" every single page on the internet works...
Quote from: BlueBall;177462Check Tools // Internet Options // Connections in MSIE and see if there are any old connections in there.
Additionally, click on LAN settings and see if a proxy has been specified.
There are no dial-up or vpn settings. The "never dial" etc is greyed out.
Lan settings: checked in automatic registration of settings but that is it. No other settings or specifications. Seems like standard.
Can I reset his network routing somehow? Say, if I had him reinstall his network-adapter? And if that adapter is built-in I cannot move it to another slot, and force a fresh reinstall wrt drivers. Just speculating here...
Quote from: delanvital;177463When he was at the uni he did use some proxies. But he says everything is gone now. It seems to be correct I guess, since "just about" every single page on the internet works...
There are no dial-up or vpn settings. The "never dial" etc is greyed out.
Lan settings: checked in automatic registration of settings but that is it. No other settings or specifications. Seems like standard.
Can I reset his network routing somehow? Say, if I had him reinstall his network-adapter? And if that adapter is built-in I cannot move it to another slot, and force a fresh reinstall wrt drivers. Just speculating here...
You could try uninstalling the NIC from device manager then rebooting but it may not cure the problem. What "may" be more effective is to go into network properties and check in the "advanced" properties of the TCP/IP protocol to see if anything has been added to DNS/WINS/NetBIOS etc. basically they should all be empty with DHCP providing all necessary info (check that DHCP server has not been hard coded just in case:)
You could also try removing TCP/IP from the protocols bound to the card then reboot and add TCP/IP back in
Here are his settings for the WINS/NetBIOS etc.
http://www.thorlaksson.dk/capture1.jpg
If you don't mind a doc I have this link as well:
http://www.thorlaksson.dk/iptcp-instil.doc
Will now look into the other stuff regarding the NIC. Good ideas. Will revert on that.
Quote from: BlueBall;177464You could also try removing TCP/IP from the protocols bound to the card then reboot and add TCP/IP back in
I had him try this first. It seems that the Uninstall-option greys out as he clicks on tcp-ip in the listbox. It is not because the card is enabled, I had him try and disable that first to no avail. So I guess I will go for the uninstall NIC procedure. Hand me the scalpel :wink:
Quote from: delanvital;177467I had him try this first. It seems that the Uninstall-option greys out as he clicks on tcp-ip in the listbox. It is not because the card is enabled, I had him try and disable that first to no avail. So I guess I will go for the uninstall NIC procedure. Hand me the scalpel :wink:
Good luck and may the force be with you :)
Can he ping the sites?
If so, telnet to them from a command prompt on port 80 and rule out the browser.
Then complain to colt through his ISP because they don't have the return routes for whatever tier 3 ISP he is signed up to....
We reinstalled the NIC with other drivers to be sure if was not them.
Quote from: Benny;177471Can he ping the sites?
If so, telnet to them from a command prompt on port 80 and rule out the browser.
Then complain to colt through his ISP because they don't have the return routes for whatever tier 3 ISP he is signed up to....
The worst first: elitedaters.com has an alias in the form of elitedating.dk.
Ping - He can ping the .com option not the .dk. I can both.
Telnet - He can only telnet the .dk option, I can both.
The other site, the colt.net-issue:
I think it is two different causes. DSB.dk - you are right. I have the same here. Colt.net is not routing correctly as you said. He is writing a mail for them now. Thanks a lot for the help, that is sorted :thumb:
But that other one... :blink:
This is the traceroute to the .dk option from him:
Microsoft Windows XP [version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator.NUITARI>tracert www.elitedating.dk (http://www.elitedating.dk)
Sporer rute til www.elitedating.dk (http://www.elitedating.dk) [195.47.247.81]
over et maksimum af 30 hop:
1 <1 ms <1 ms <1 ms 192.168.1.254
2 26 ms 26 ms 26 ms 1.16.185.213.dk-bot.res.dyn.perspektivbredband.n
et [213.185.16.1]
3 26 ms 26 ms 26 ms kbhn-cdix-pr0-gi0-0-509.perspektivbredband.net [
213.185.31.54]
4 27 ms 27 ms 27 ms ge2-6.cr1.gl.cph.ngdc.net [192.38.7.93]
5 42 ms 28 ms 28 ms ge1-26.ar0.ly.cph.ngdc.net [217.116.255.33]
6 28 ms 28 ms 28 ms ge1-26.ar0.ba.cph.ngdc.net [217.116.255.29]
7 * * * Anmodning fik timeout.
8 * * * Anmodning fik timeout.
9 * * * Anmodning fik timeout.
10 * * * Anmodning fik timeout.
11 ^C
C:\Documents and Settings\Administrator.NUITARI>
So that times out. Here is my attempt:
C:\Documents and Settings\Administrator>tracert www.elitedating.dk (http://www.elitedating.dk)
Tracing route to www.elitedating.dk (http://www.elitedating.dk) [195.47.247.81]
over a maximum of 30 hops:
1 6 ms 6 ms 38 ms 192.168.100.1
2 12 ms 13 ms 13 ms lo1.sgnxx3.ip.tele.dk [80.166.138.221]
3 13 ms 17 ms 12 ms ge-0-3-0-40.1000M.sgnxj1.ip.tele.dk [83.88.2.129
]
4 16 ms 15 ms 19 ms pos1-2.622M.naenxg2.ip.tele.dk [83.88.27.154]
5 19 ms 13 ms 13 ms pos5-3.622M.naenxg1.ip.tele.dk [83.88.13.217]
6 39 ms 51 ms 50 ms so-3-1-0.2488M.albnxu1.ip.tele.dk [83.88.23.218]
7 15 ms 14 ms 16 ms pos0-0.2488M.albnxg7.ip.tele.dk [83.88.12.78]
8 35 ms 34 ms 37 ms so-0-3-0-622M.ar1.CPH1.gblx.net [64.208.110.21]
9 33 ms 36 ms 33 ms ge1-1-10G.ar3.CPH1.gblx.net [67.17.105.242]
10 34 ms 35 ms 33 ms Netgroup.ge-1-2-0.100.ar2.CPH1.gblx.net [64.212.
108.226]
11 35 ms 32 ms 34 ms ge1-5.cr0.taa.cph.ngdc.net [217.116.255.63]
12 37 ms 33 ms 37 ms ge1-25.ar0.ba.cph.ngdc.net [217.116.255.25]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * ^C
C:\Documents and Settings\Administrator>
Which also times out. So, there is some routing problems for that site t ngdc.net. But if I enter the .dk option into my browser I get to the site (refers to the .com) if he does that, it just times out, as well with the .com option. So for him, the issue is not this routing problem with the .dk-referrer I think.
Knowing that he can traceroute to the actual server via .com or the ip, that he can ping the .com option as well, but not telnet it - we are down to a browser issue?
Quote from: delanvital;177476Knowing that he can traceroute to the actual server via .com or the ip, that he can ping the .com option as well, but not telnet it - we are down to a browser issue?
If it isn't the browser then it could be a TCP stack issue.
Is he using MSIE? If so DL Firefox or Opera and try them to see if they work?
Quote from: BlueBall;177482Is he using MSIE? If so DL Firefox or Opera and try them to see if they work?
We installed FF to test, it also times out. Worth trying Opera as well?
TCP-stack. How do I deal with that? Should we try an other router? Tomorrow we will try a laptop on the network to see.
Are there any strange entries in his routing table?
From a cmd prompt type "route print" to list his active route table. Check for any persistant routes.
Quote from: lionheart;177484Are there any strange entries in his routing table?
From a cmd prompt type "route print" to list his active route table. Check for any persistant routes.
Already tried that one (see previous ppage)
Quote from: delanvital;177483We installed FF to test, it also times out. Worth trying Opera as well?
Nah, if FF made no diff then it is not a browser problem. The issue is being caused somewhere in the networking layers either locally or through ISP.
The big test would be to try another PC on the network and see how it performs. If it works OK then prob is local, if it has probs then time to start shouting at ISP.
JUst noticed BB suggested this ages ago.. I'll get my coat.......
Quote from: lionheart;177487JUst noticed BB suggested this ages ago.. I'll get my coat.......
Nah I've already got your coat coz I hadn't noticed he had already checked the hosts file so I guess we're daft together :)
Er, does he have PeerGuardian2 installed or any other P2P "protection" software?
I just thought I would try the address on my second PC, which runs PeerGuardian2 and the web address you specified is in the blocklist and so all traffic is blocked!
All that would happens is your browser will timeout as the traffic is intercepted by the program, you can turn the HTTP blocker off on PG2.
Check for it on the taskbar or see what software he has installed.
and after that get him take another pc/laptop home to test on his network.
Quote from: delanvital;177448No other PC has been tested on the network, although we are working on it.
Quote from: suicidal_monkey;177502and after that get him take another pc/laptop home to test on his network.
I am bringing my laptop by today to do a comparison.
Quote from: Liberator;177493Er, does he have PeerGuardian2 installed or any other P2P "protection" software?
I will check later today.
Also, hijackThis report was clean but I am planning to kill all non-essential services and processes in a session and see if that helps anyway.
Quote from: BlueBall;177488Nah I've already got your coat coz I hadn't noticed he had already checked the hosts file so I guess we're daft together :)
That's good cos I was about to suggest checkign the host file! :blink:
TL.
I hooked up a laptop which worked fine. When attempting to connect to elitedating.dk it said dns-error, but was redirected to the .com option automatically.
I am now at his PC and I tried to clear out all the processes I could and test some things. Still no luck.
He uses the Gbit NIC built-in in the nForce3 chipset (ASUS K8N-E Deluxe if i remember correctly). I will try various drivers for that NIC.
I have solved the problem. Not sure what it was though.
I looked into the drivers for the nForce3 Gbit built-in netcard. Some functions was not working. So, I went for the reference driver from nvidia. That install gave me about 5-6 different error messages and would not start. As a wild guess I ran the installation in Win2K compatibility mode and it almost completed - but gave me a BSoD. After rebooting the software had installed enough for the NIC to work. The problem was gone. How I LOVE windows.
So, seems like either a software og hardware error with the NIC. For now it works, so better leave it like that.
Thanks for all your help. Also, a big thanks fro my friend to you all. dMw rocks :woot2:
Glad your fixed m8
rofl @ TL :lmfao: