IE & Router problem

[Guest]

I am running Windows XP SP2, IE6, and have been accessing my Internet ISP by
a simple (ISP supplied) ADSL modem. I have switched to a D-Link router and
now find that i cannot send email (but recieve ok) due to 'host unexepectedly
terminated the connection' error. I am also finding it very slow accessing
specific web sites. I have checked configs and applied latest router updates;
no difference.
I have borrowed a NetGear router from a friend; it gives me the same
problem. I have connected a laptop running Win2k to both routers; the laptop
works fine with both routers.
If i switch the XP PC the back to the modem, all works fine again.
My conclusion is that i some sort of conflict in the PC that is interfering
with the router operation, but what? Any ideas?
NB: I have used TCPOptimiser to check MTUs - via router or moden it gives me
the same information - max size setting of 1458.

 

[NormanM]

I am running Windows XP SP2, IE6, and have been accessing my Internet ISP by
a simple (ISP supplied) ADSL modem. I have switched to a D-Link router and
now find that i cannot send email (but recieve ok) due to 'host unexepectedly
terminated the connection' error. I am also finding it very slow accessing
specific web sites. I have checked configs and applied latest router updates;
no difference.
I have borrowed a NetGear router from a friend; it gives me the same
problem. I have connected a laptop running Win2k to both routers; the laptop
works fine with both routers.
If i switch the XP PC the back to the modem, all works fine again.
My conclusion is that i some sort of conflict in the PC that is interfering
with the router operation, but what? Any ideas?
NB: I have used TCPOptimiser to check MTUs - via router or moden it gives me
the same information - max size setting of 1458.

It might help to know your connection type: Cable, or DSL? There should be
no conflict between MSIE and a router; thousands have hooked things up this
way over the years. There *could* be an issue with certain specific
configurations, such as "cascaded NAT", which happens with some DSL modems,
which are actually combination modem/router units.

 

[Guest]

My connection is via an ADSL, and both routers are combined ADSL modem/routers.

I agree its an odd problem. Talking to router suppliers and my ISP has not
given any clues, but something is clearly wrong. My analysis suggests the
problem lies within IE on my PC, but happy to proved wrong. Is there any
basic difference between the way IE communicates to an ISP directly via modem
or via a router/modem path?

Also looked at NAT options in both my router - only one option:
enable/disable NAT. If i disable, all connectivity to the internet is lost.

 

[NormanM]

"NormanM" wrote:

My connection is via an ADSL, and both routers are combined ADSL modem/routers.

I agree its an odd problem. Talking to router suppliers and my ISP has not
given any clues, but something is clearly wrong. My analysis suggests the
problem lies within IE on my PC, but happy to proved wrong. Is there any
basic difference between the way IE communicates to an ISP directly via modem
or via a router/modem path?

There is no difference in the behavior of MSIE between a router, and a
direct modem connection. Browser issues HTTP commands to an IP address,
server at that IP address responds. The router *should* transparent to MSIE.

Also looked at NAT options in both my router - only one option:
enable/disable NAT. If i disable, all connectivity to the internet is lost.

Of course. NAT translates both IP address and port number between the WAN
and the LAN. MSIE issues an HTTP GET command to www.example.com. MSIE does a
DNS lookup on www.example.com, finds it at 11.22.33.44, sends the GET
command to 11.22.33.44 from local port 1234. Router puts LAN IP address and
port 1234 into it NAT table, and sends th GET packet on its way to
11.22.33.44 from it port 1536. Server sends a response to your public IP
address at port 1536, your router looks up the destination in its NAT table,
and forwards the response to your LAN IP address at port 1234. As I said,
that process should be transparent to MSIE.

I can't think of anything in MSIE that would choke with a router, but work
without one.

Are you running the D-Link router *and* a DSL modem? Does your ISP require
PPPoE?

 

[Guest]

Norman,

The D-link router is an integral router and DSL modem. ISP requires PPPOA
which is what i have the router configured to.

Thanks for your thoughts on the topic. I will keep digging; there must be a
logical solution somewhere.

 

[NormanM]

The D-link router is an integral router and DSL modem. ISP requires PPPOA
which is what i have the router configured to.

USA? Qwest is the only major U.S. DSL provider using PPPoA. You might check
out this forum:

http://www.dslreports.com/forum/ilec,uswest

If you are posting from overseas I think I have gone about as far as I can
with this.

 

[Robert Aldwinckle]

There is no difference in the behavior of MSIE between a router, and a
direct modem connection. Browser issues HTTP commands to an IP address,

Norman,

Conceptually the browser issues HTTP commands to a server *name*.
In order for that to work though the name has to be converted to an IP address
and a connection established with a server there. If that's not getting done
it explains the symptom too. My questions are how much of that is done
by the application and how much is done (or assumed done) in lower level
layers by the OS? Also how much caching of those lookups is done
and how effective is it? Then, concerning the point being made, are there
different timeouts associated with using local versus global addresses?

Making the first connection to a particular server by an instance of the browser
(e.g. task running iexplore.exe) looks to me to be an iffy procedure.
If there are differences as well regarding local versus global addresses
that could just compound the uncertainty about how successful
that first connection might be.

Once a site has been accessed by an instance of a browser there may be
less of a problem using it. E.g. apparently there is an in storage cache
(different from dnscache) which would save users that source of delay
(at the risk of incorrect lookup? ref. KB263558.) Fortunately it seems
to go away when iexplore.exe is recycled.

So I think there could be a significant hurdle doing the first (or subsequently
required) DNS lookup for a name, especially depending on how long IE
needs to wait/does wait for it. And I suspect that the *first* lookup also
has to dodge whatever timeout is used by the AutoSearch/AutoScan machinery
when the user neglects to add a protocol prefix to the "request".


In order to make sure that this is not a factor I have been suggesting users
could use ping -n 1 to load the dnscache for IE (and check with /displaydns
how long they had to use it.) In addition, in the case that the lookup is for an
alias, it appears that it is also necessary to ping -n 1 the canonical name
and get it loaded into the dnscache too. Of course adding an entry to HOSTS
would completely eliminate both factors (provided there weren't any redirects

server at that IP address responds. The router *should* transparent to MSIE.

I think we had a case in the other IE NG recently which showed that a router
was trying to act as the DNS. So that could be adding to the delays for lookups.

http://www.microsoft.com/communitie...693974-fec7-4f61-b50d-4a0e52580780&sloc=en-us

E.g. if the OS sees a local address as a DNS address perhaps it would
expect to see responses to such requests more quickly and more reliably
than it would if it knew that the DNS was remote over a (relatively slow)
transport?


Robert
---

 

[NormanM]

Norman,

Conceptually the browser issues HTTP commands to a server *name*.
In order for that to work though the name has to be converted to an IP address
and a connection established with a server there.

Yes. Which I did explain in my post. I see you quoted that part of my post,
uncommented, a the end of your reply.

If that's not getting done it explains the symptom too. My questions are how much
of that is done by the application and how much is done (or assumed done) in lower
level layers by the OS? Also how much caching of those lookups is done
and how effective is it? Then, concerning the point being made, are there
different timeouts associated with using local versus global addresses?

I believe that should all be transparent to the user.

Making the first connection to a particular server by an instance of the browser
(e.g. task running iexplore.exe) looks to me to be an iffy procedure.
If there are differences as well regarding local versus global addresses
that could just compound the uncertainty about how successful
that first connection might be.

And that is affected by the difference between connecting through a router,
or directly through a modem....how?

I think we had a case in the other IE NG recently which showed that a router
was trying to act as the DNS. So that could be adding to the delays for lookups.

The router would be acting as a DNS proxy. That is fairly common:

| Windows IP Configuration
|
| Host Name . . . . . . . . . . . . : KOZUE
| Primary Dns Suffix . . . . . . . :
| Node Type . . . . . . . . . . . . : Hybrid
| IP Routing Enabled. . . . . . . . : No
| WINS Proxy Enabled. . . . . . . . : No
| DNS Suffix Search List. . . . . . : aosake.net
| Ethernet adapter Local Area Connection:
|
| Connection-specific DNS Suffix . : aosake.net
| Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
| Physical Address. . . . . . . . . : 00-17-31-C6-CC-63
| Dhcp Enabled. . . . . . . . . . . : Yes
| Autoconfiguration Enabled . . . . : Yes
| IP Address. . . . . . . . . . . . : 192.168.102.34
| Subnet Mask . . . . . . . . . . . : 255.255.255.0
| Default Gateway . . . . . . . . . : 192.168.102.1
| DHCP Server . . . . . . . . . . . : 192.168.102.1
|>>> DNS Servers . . . . . . . . . . . : 192.168.0.1 <<<|
| Lease Obtained. . . . . . . . . . : Tuesday, June 26, 2007 09:08:52
| Lease Expires . . . . . . . . . . : Friday, June 29, 2007 09:08:52

http://www.microsoft.com/communitie...693974-fec7-4f61-b50d-4a0e52580780&sloc=en-us

E.g. if the OS sees a local address as a DNS address perhaps it would
expect to see responses to such requests more quickly and more reliably
than it would if it knew that the DNS was remote over a (relatively slow)
transport?

I wouldn't know at that level. Nslookup will give me this:

| nslookup www.hotmail.com
| DNS request timed out.
| timeout was 2 seconds.
| *** Can't find server name for address 192.168.0.1: Timed out
| *** Default servers are not available
| Server: UnKnown
| Address: 192.168.0.1
|
| Non-authoritative answer:
| Name: www.hotmail.aate.nsatc.net
| Address: 206.24.192.250
| Aliases: www.hotmail.com, www.hotmail.com.nsatc.net

But the Sam Spade tool for Win32 systems gives me this result:

| 06/26/07 10:39:50 dns www.hotmail.com
| Canonical name: www.hotmail.aate.nsatc.net
| Aliases:
| www.hotmail.com
| www.hotmail.com.nsatc.net
| Addresses:
| 216.74.180.189

Still I suppose there could be a problem; just because I haven't encountered
one, myself.

Which pretty much covers what you have discussed earlier.


One of my pet peeves about the "brokeness" of MS Outlook Express, as a news
client, is its inability to trim signatures from quoted text. MSFT is never
going to fix this in MSOE; but they *should* have addressed this in the
Windows Live Mail beta; it is *still* broken in WLM!

Oh, and I see that you have not given the OP an alternative to fix a
possible DNS lookup delay; manually adding the DNS servers to the network
properties.

 

[NormanM]

The D-link router is an integral router and DSL modem. ISP requires PPPOA
which is what i have the router configured to.

Thanks for your thoughts on the topic. I will keep digging; there must be a
logical solution somewhere.

Robert Aldwinckle has taken me to task for overlooking something. The
possibility that your system is seeing your DNS servers as local. You can
see this by using the 'nslookup' command in a command window. For Windows XP
type 'cmd' in the Run box. Windows 98 and Windows Me have a shortcut in the
Start menus.

I get the following result:

| C:\Documents and Settings\Norman>nslookup www.yahoo.com
| DNS request timed out.
| timeout was 2 seconds.
| *** Can't find server name for address 192.168.0.1: Timed out
| *** Default servers are not available
| Server: UnKnown
| Address: 192.168.0.1
|
| Non-authoritative answer:
| Name: www.yahoo-ht3.akadns.net
| Address: 209.131.36.158
| Aliases: www.yahoo.com

There is a perceptible delay between pressing the 'Enter' key and seeing a
result. What is happening is that my DNS request is passed through my
Netgear router to my DSL modem. When I run 'ipconfig -all' at the command
prompt, I get the following:

| C:\Documents and Settings\Norman>ipconfig -all
|
| Windows IP Configuration
|
| Host Name . . . . . . . . . . . . : KOZUE
| Primary Dns Suffix . . . . . . . :
| Node Type . . . . . . . . . . . . : Hybrid
| IP Routing Enabled. . . . . . . . : No
| WINS Proxy Enabled. . . . . . . . : No
| DNS Suffix Search List. . . . . . : aosake.net
|
| Ethernet adapter Local Area Connection:
|
| Connection-specific DNS Suffix . : aosake.net
| Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
| Physical Address. . . . . . . . . : 00-17-31-C6-CC-63
| Dhcp Enabled. . . . . . . . . . . : Yes
| Autoconfiguration Enabled . . . . : Yes
| IP Address. . . . . . . . . . . . : 192.168.102.34
| Subnet Mask . . . . . . . . . . . : 255.255.255.0
| Default Gateway . . . . . . . . . : 192.168.102.1
| DHCP Server . . . . . . . . . . . : 192.168.102.1
| >>>> DNS Servers . . . . . . . . . . . : 192.168.0.1 <<<<|
| Lease Obtained. . . . . . . . . . : Tuesday, June 26, 2007 09:08:52
| Lease Expires . . . . . . . . . . : Friday, June 29, 2007 09:08:52

As you can see, Windows thinks that there is a DNS server at 192.168.0.1,
which is the IP address of my DSL modem. I can override the DNS server
setting in the router by manually adding the DNS servers listed in the
modem. When I do, 'ipconfig -all' gives me this result:

| C:\Documents and Settings\Norman>ipconfig -all
|
| Windows IP Configuration
|
| Host Name . . . . . . . . . . . . : KOZUE
| Primary Dns Suffix . . . . . . . :
| Node Type . . . . . . . . . . . . : Hybrid
| IP Routing Enabled. . . . . . . . : No
| WINS Proxy Enabled. . . . . . . . : No
| DNS Suffix Search List. . . . . . : aosake.net
|
| Ethernet adapter Local Area Connection:
|
| Connection-specific DNS Suffix . : aosake.net
| Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
| Physical Address. . . . . . . . . : 00-17-31-C6-CC-63
| Dhcp Enabled. . . . . . . . . . . : Yes
| Autoconfiguration Enabled . . . . : Yes
| IP Address. . . . . . . . . . . . : 192.168.102.34
| Subnet Mask . . . . . . . . . . . : 255.255.255.0
| Default Gateway . . . . . . . . . : 192.168.102.1
| DHCP Server . . . . . . . . . . . : 192.168.102.1
| >>>> DNS Servers . . . . . . . . . . . : 68.94.156.1 <<<<|
| >>>> 68.94.157.1 <<<<|
| Lease Obtained. . . . . . . . . . : Tuesday, June 26, 2007 10:58:06
| Lease Expires . . . . . . . . . . : Friday, June 29, 2007 10:58:06

The DNS servers are now the ones listed in the modem Connection Information
page at http://192.168.0.1. Now 'nslookup' is a bit faster, almost
instantaneous:

| C:\Documents and Settings\Norman>nslookup www.yahoo.com
| Server: dnsr1.sbcglobal.net
| Address: 68.94.156.1
|
| Non-authoritative answer:
| Name: www.yahoo-ht3.akadns.net
| Address: 209.131.36.158
| Aliases: www.yahoo.com

Since this all works for me, anyway, I never give it much thought. Although
I don't know how a combination unit handles the matter. Maybe I do; the
relevant result from a computer which I know for certain to be connecting
through a combination DSL modem/router:

| Ethernet adapter Local Area Connection:
|
| Connection-specific DNS Suffix . :
| Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC
| Physical Address. . . . . . . . . : 00-40-2B-62-51-E9
| Dhcp Enabled. . . . . . . . . . . : No
| IP Address. . . . . . . . . . . . : 192.168.1.254
| Subnet Mask . . . . . . . . . . . : 255.255.254.0
| Default Gateway . . . . . . . . . : 192.168.0.1
|>>>> DNS Servers . . . . . . . . . . . : 192.168.0.1 <<<<|
| 206.13.28.12

So, if your 'ipconfig -all' result shows a local IP address
(192.168.xxx.xxx) for your DNS server, you might try to identify your DNS
server IP addresses (should be available through the router status pages),
and adding them manually to your Ethernet adapter through Network
Properties.

 

[Robert Aldwinckle]

.


Yes. Which I did explain in my post. I see you quoted that part of my post,
uncommented, a the end of your reply.

Well, sorry. I wasn't trying to criticize or lecture. I just thought that this was
the best way to emphasize my (admittedly speculative) points. I just wish
we had some decent diagnostics and program logic descriptions to go with
them. I never realized how much I was being spoiled by IBM when working
on mainframes. ; }

I believe that should all be transparent to the user.

Provided the timing isn't different or doesn't matter.

And that is affected by the difference between connecting through a router,
or directly through a modem....how?

We're not sure? ; )


....

I wouldn't know at that level. Nslookup will give me this:

| nslookup www.hotmail.com
| DNS request timed out.
| timeout was 2 seconds.
| *** Can't find server name for address 192.168.0.1: Timed out
| *** Default servers are not available
| Server: UnKnown
| Address: 192.168.0.1

I wonder if that timeout is really significant? E.g. if it only represents
the failure of the reverse lookup for the local address for the DNS
perhaps you could eliminate that delay by giving it a name somewhere?

|
| Non-authoritative answer:
| Name: www.hotmail.aate.nsatc.net
| Address: 206.24.192.250
| Aliases: www.hotmail.com, www.hotmail.com.nsatc.net

But the Sam Spade tool for Win32 systems gives me this result:

| 06/26/07 10:39:50 dns www.hotmail.com
| Canonical name: www.hotmail.aate.nsatc.net
| Aliases:
| www.hotmail.com
| www.hotmail.com.nsatc.net
| Addresses:
| 216.74.180.189

Heh. Want another one? ; }

<nslookup>
Non-authoritative answer:
Name: www.hotmail.aate.nsatc.net
Address: 64.70.45.46
Aliases: www.hotmail.com, www.hotmail.com.nsatc.net
</nslookup>


Somebody once suggested I try DIG intead of nslookup.
(Domain I(something) Groper.) I can't remember if it avoids
this issue of doing a reverse lookup for the DNS server address
or not.

Still I suppose there could be a problem; just because I haven't encountered
one, myself.

Since there are no diagnostics and no logic manuals the only thing
that I can think of doing to try to find out is taking a packet trace
of both cases (e.g. netcap + Ethereal) and comparing the two timing-wise.
Probably one set of observations wouldn't tell us much so we'd have to do it
many times and see if there was a difference statistically. Ugh...

Which pretty much covers what you have discussed earlier.

Except for my emphasis on making the initial connection
appearing to be the weakest point in the process, yes. ; }

One of my pet peeves about the "brokeness" of MS Outlook Express, as a news
client, is its inability to trim signatures from quoted text. MSFT is never
going to fix this in MSOE; but they *should* have addressed this in the
Windows Live Mail beta; it is *still* broken in WLM!

I thought that this had been fixed--part of OE6sp1 mondo perhaps?

Oh, and I see that you have not given the OP an alternative to fix a
possible DNS lookup delay; manually adding the DNS servers to the network
properties.

Good idea. I hope it works.


Robert
---

 

[NormanM]

I wonder if that timeout is really significant? E.g. if it only represents
the failure of the reverse lookup for the local address for the DNS
perhaps you could eliminate that delay by giving it a name somewhere?

I already have a host file entry for the modem:

| 192.168.0.1 suzuka.aosake.net Suzuka # Siemens SpeedStream 4100

I tried playing with custom configuration of Treewalk, once; but I have a
lot more to learn about how DNS works before I can confidently set it up as
more than just a local, caching DNS server.

Heh. Want another one? ; }

Not really. The point was the different results in the final IP address
found, but in the fact that Sam Spade didn't choke on the local DNS proxy;
though, admittedly, it took a second, or three, to get the result.

Since there are no diagnostics and no logic manuals the only thing
that I can think of doing to try to find out is taking a packet trace
of both cases (e.g. netcap + Ethereal) and comparing the two timing-wise.
Probably one set of observations wouldn't tell us much so we'd have to do it
many times and see if there was a difference statistically. Ugh...

One of my pet peeves about the "brokeness" of MS Outlook Express, as a news
client, is its inability to trim signatures from quoted text. MSFT is never
going to fix this in MSOE; but they *should* have addressed this in the
Windows Live Mail beta; it is *still* broken in WLM!

I thought that this had been fixed--part of OE6sp1 mondo perhaps?
but it may depend on the poster actually using a signature too... <eg>

What MSOE fixed is the cursor placement. At least, I can get MSOE to place
the cursor at the end of the quoted text using a registry hack. I have never
seen MSOE trim quoted signatures.

Good idea. I hope it works.

Maybe the OP will post back the results, if he tries it.

 

[Guest]

Norman,

Thanks for the input. I went throught the process steps you suggested and
got the same results as per your note for nslookup and ipconfig commands. I
tried setting router up with manaual DNS entries, but made no difference to
the original problem. (I used ipconfig to verify DNS addresses had changed).

So looks like another blank.

I tried to follow the thread of the discussions between yourself and Robert.
The ping command gave me the following. It translates to an ip address, but
then cannot find the host. Odd?:

"C:\Documents and Settings\Paul>ping tiscali.co.uk -n 1
Pinging tiscali.co.uk [212.74.99.30] with 32 bytes of data:
Request timed out.
Ping statistics for 212.74.99.30:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:\Documents and Settings\Paul>"

 

[NormanM]

On Wed, 27 Jun 2007 13:14:03 -0700, Paul W wrote:

The only other thing that I can think of is that your ISP is using some kind
of transparent, caching proxy which is inducing delay in DNS response; a
delay which isn't breaking things when connected directly to the modem, but
breaking things when the router is added.

Trying the FQDN in your ping test with Sam Spade WinTool:

| 06/27/07 16:14:06 ping tiscali.co.uk
| Ping tiscali.co.uk (212.74.99.30) ...
| 1 failed
| 2 failed
| 3 failed
| 4 failed
| 5 failed
| 6 failed
| 7 failed
| 8 failed
| 9 failed
| 10 failed

And also:

| 06/27/07 16:15:01 Slow traceroute tiscali.co.uk
| Trace tiscali.co.uk (212.74.99.30) ...
| 192.168.102.1 RTT: 1ms TTL:170 (chihiro.aosake.net ok)
| 192.168.0.1 RTT: 2ms TTL:170 (suzuka.aosake.net ok)
| 69.105.177.254 RTT: 350ms TTL:170 (adsl-69-105-177-254.dsl.pltn13.pacbell.net ok)
| 64.164.97.130 RTT: 371ms TTL:170 (dist1-vlan60.pltn13.pbi.net probable bogus rDNS: No DNS)
| 151.164.93.231 RTT: 355ms TTL:170 (bb1-g15-0.pltnca.sbcglobal.net ok)
| 151.164.242.230 RTT: 284ms TTL:170 (ex2-p14-0.eqsjca.sbcglobal.net ok)
| 213.200.66.245 RTT: 273ms TTL:170 (so-0-1-2.sjc11.ip.tiscali.net probable bogus rDNS: No DNS)
| 213.200.81.254 RTT: 443ms TTL:170 (so-0-0-0.lon22.ip.tiscali.net probable bogus rDNS: No DNS)
| 213.200.78.234 RTT: 317ms TTL:170 (tiscali-uk-tch2.ip.tiscali.net probable bogus rDNS: No DNS)
| 212.74.106.210 RTT: 254ms TTL:170 (ge3-2.switch0-mk.as9105.net probable bogus rDNS: No DNS)
| * * * failed
| * * * failed
| * * * failed
| * * * failed

That is an odd result (latency is higher than expected due to a concurrent
BitTorrent download).

Probably not responding to ICMP.

Thanks for the input. I went throught the process steps you suggested and
got the same results as per your note for nslookup and ipconfig commands. I
tried setting router up with manaual DNS entries, but made no difference to
the original problem. (I used ipconfig to verify DNS addresses had changed).

So looks like another blank.

I tried to follow the thread of the discussions between yourself and Robert.
The ping command gave me the following. It translates to an ip address, but
then cannot find the host. Odd?:

"C:\Documents and Settings\Paul>ping tiscali.co.uk -n 1
Pinging tiscali.co.uk [212.74.99.30] with 32 bytes of data:
Request timed out.
Ping statistics for 212.74.99.30:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:\Documents and Settings\Paul>"

 

[Robert Aldwinckle]

Norman,

Thanks for the input. I went throught the process steps you suggested and
got the same results as per your note for nslookup and ipconfig commands. I
tried setting router up with manaual DNS entries, but made no difference to
the original problem. (I used ipconfig to verify DNS addresses had changed).

So looks like another blank.

I tried to follow the thread of the discussions between yourself and Robert.
The ping command gave me the following. It translates to an ip address, but
then cannot find the host. Odd?:

"C:\Documents and Settings\Paul>ping tiscali.co.uk -n 1
Pinging tiscali.co.uk [212.74.99.30] with 32 bytes of data:
Request timed out.
Ping statistics for 212.74.99.30:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:\Documents and Settings\Paul>"

If that name is what you are entering in IE's Address bar
you're going to have unnecessary delay due to redirection anyway.

E.g. using telnet 80 here is what I get from a GET / to it
and with Host: tiscali.co.uk

<telnet>
HTTP/1.1 301 Moved Permanently
Date: Thu, 28 Jun 2007 02:25:52 GMT
Server: Apache/1.3.34 (Unix) PHP/4.4.2 mod_ssl/2.8.25 OpenSSL/0.9.7e
Location: http://www.tiscali.co.uk/
</telnet>

IOW you might as well start with that URL in the Location: header

Apparently it is found at the same IP address:

<nslookup>
Non-authoritative answer:
Name: www.tiscali.co.uk
Address: 212.74.99.30
</nslookup>


FYI

Robert
---