I need some expert advise...

delanvital · February 15, 2007, 09:11:20 PM

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.

delanvital · February 15, 2007, 09:21:47 PM

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:

Anonymous · February 15, 2007, 09:51:23 PM

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

Benny · February 15, 2007, 10:00:49 PM

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....

delanvital · February 15, 2007, 10:41:26 PM

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:

delanvital · February 15, 2007, 10:48:31 PM

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

Sporer rute til 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

Tracing route to 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?

Anonymous · February 15, 2007, 11:04:05 PM

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?

delanvital · February 15, 2007, 11:05:06 PM

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.

lionheart · February 15, 2007, 11:30:05 PM

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.

Anonymous · February 15, 2007, 11:31:09 PM

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)

Anonymous · February 15, 2007, 11:32:57 PM

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.

lionheart · February 15, 2007, 11:34:46 PM

JUst noticed BB suggested this ages ago.. I'll get my coat.......

Anonymous · February 15, 2007, 11:38:03 PM

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

Liberator · February 16, 2007, 12:29:05 AM

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.

suicidal_monkey · February 16, 2007, 08:24:53 AM

and after that get him take another pc/laptop home to test on his network.