Esat BT and windows 2000

Fabre

I have downgraded my pc from winXP to 2000 pro SP4.

One of the first things I have noticed after installing the modem driver is that it is improperly detected. (It asked for my area code...)

Connection speed 8mbps
in reality the "normal" 50ko/s

Then in properties it says it connect using an ISDN channel and line type 64k (other available settings 56k digital or voice)

all that seems purely esthetical concern since the connection work "iol" fine.

But another new features is the fact that my second pc (shared connection) can't access some websites like monster.fr or home.io.ie but can access others like hotmail ot google. It was working fine with XP But this part should probably go in the OS section.

So the question is has anyone else have the same issues with windows 2000 and have they found a cure?

/Edit

The cd that came with the modem wasn't working so Bt tech told me to get it from : http://www.systemhouse.com/p630/

OfflerCrocGod

Well did that cure it, I was having the same problems with ICS before I got a router(thank God for that!), I dont see how it could have been the drivers......

Fabre

No, no cure so far, but the thing I don't get is that it was working fine with XP pro.
And why some sites work and other don't???

^pt^

I guess you mean with Internet Connection Sharing? I have exactly the same problem if so. The only answer I could find is because ICS seems to use ICMP somehow, since Esat block this it occasionally causes problems.

From what I've seen it's almost random, not always the same websites, not all the time either. You can't really complain to Esat about it, since their T&C clearly state they only support one computer.

I gave up trying to find a solution, I'm getting a router. You might try a software solution instead of ICS though, there are a couple of programs that do the same job. Wingate, Kerio WinRoute and Sygate Home Network to name a few, all available on download.com.

Hope that helps,
PT.

Fabre

Followed your advice installed winroute pro and configure it has a proxy server internet works fine on the client pc now but on the downside it still eat about 10mo ressources on the main pc.

OfflerCrocGod

For me it wasn't random at all it was always the same sites all the time. Listen ICS ate up resources when you were running it on windows - unless you though it ran on air?, I suggest you dump the s/w solution and buy a router it just makes sense and makes your network safer and more efficient. Once you get a router you will never want to go back to ICS and other s/w hacks (cause that's all they are).

Fabre

well Kerio winroute pro solved my problem and it is a firewall aswell so apart from the ressources usage I really don't have any complaints.

Atm I am scanning myself to test the firewall.
http://scan.sygatetech.com/

haven't found any open port so far

Really don't see the point in buying a router when I already have a modem and a, now, working internet connection. and also because I am expecting to move to canada soon.
So I will probaly consider buying a wireless router at a later date but not for now.

/EDIT

btw with a router is it possible to control the bandwidth allocation to different softwares on different machines.

I use netlimiter but it only allow me to control the bandwidth allocated to software installed on the machine where it is running.

OfflerCrocGod

It depends on the router you buy. Sorry for not being more helpful but it's up to the router so when getting it just check the advertised features.

Ripwave

Originally posted by Fabre
btw with a router is it possible to control the bandwidth allocation to different softwares on different machines.

Offhand, I don't know of any "residential" router that does that. It's not exactly a "mass market" feature, so I haven't come across it in any product descriptions in this market segment.

Fabre

Solved!

the answer here

I am pasting it here aswell in case the other page dissapear

From

: Klom Dark
Posted

: 11/3/2002 1:22:18 PM


Subject

: Fix for slow ICS on Windows 2000
[Reply To This Message] [Start New Thread]

When using Internet Connection Sharing to connect through a Windows 2000 machine from a Windows 2000 machine (I've only tested this problem using a Windows 2000 machine as a client, other versions of Windows used for a client may also have the same problem, I don't know.) it will probably go pretty slow with the default settings, as the Message Transfer Unit (MTU) sizes do not match for some reason. When the client MTU is larger than the Host ICS MTU, packets will get silently dropped, causing your connection to be excruciatingly slow.

To fix this requires a bit of simple experimentation to find the proper MTU size. I found the maximum working MTU size on my machine is 1344. Your mileage may vary.

On the client machine, open a command prompt. I started with 1500 and worked my way through it.

The command to use is ping, with some extra flags. Assuming your host machine is 192.168.0.1 try the following:

ping -f -l (MTU Size) (Host Address)

Such as:

ping -f -l 1500 192.168.0.1

With a value of 1500, you will either get no response or a message about "Packet needs to be fragmented but DF set." depending. When you get no response, try a lower number.

I tried 1200 to start:

ping -f -l 1200 192.168.0.1

Which gave me a normal ping response like:

---

Pinging 192.168.0.1 with 1200 bytes of data:

Reply from 192.168.0.1: bytes=1200 time=10ms TTL=128
Reply from 192.168.0.1: bytes=1200 time<10ms TTL=128
Reply from 192.168.0.1: bytes=1200 time<10ms TTL=128
Reply from 192.168.0.1: bytes=1200 time<10ms TTL=128

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% lo
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 10ms, Average = 2ms

---

This means that an MTU size of 1200 works, but the bigger the MTU, the faster data can be transmitted, so now we start increasing the size. I try 1300 next:

ping -f -l 1300 192.168.0.1

Once again I get a good response. So I try 1400 for the MTU size:

ping -f -l 1400 192.168.0.1

This time I get a bad response, this means an MTU size of 1400 is too big, so I cut the difference to 1450 and try again, still no response, still too big.

I try 1325 and get a good response. I then kept increasing the size until I could not get a response (1345 didn't work for me, but 1344 did, so I went with that as the best size.)

Now, what to do with this magic value?

Open regedit, and open HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces - Underneath Interfaces, you'll see one or more cryptic entries like {1B2709BD-B617-44B0-9386-B508EE40F17B}. This is Windows obscure way of refering to the network card settings. If there is only one, you know which is the correct entry. If there is more than one (and assuming you have only one NIC in your client machine), then click on each one individually and look at the values underneath it. Find the entry that has the IP address of the ICS host machine for the DHCPDefaultGateway and DHCPServer entries. The other entries will probably be 0.0.0.0 for same settings.

Once you have located the correct entry, right-click on that entry and select "New DWORD Value". Type "MTU" (In uppercase, no quotes) for the new name and hit Enter. Next, double-click on the new MTU entry to bring up the dialog to set the actual value. Select the radio button for a Decimal Base, and enter the MTU value you figured out with the ping command above, then click OK. Close Regedit.

The last step is to Right-Click on My Network Places, then select Properties from the menu that appears. This will bring up your Network and Dialup Connections. You should have an entry called "Local Area Connection" - right-click on it and select Disable. Once it is disabled, right-click on Local Area Connection again and select Enable. This restarts the network connection with the new correct MTU value.

Open your web browser and connect to somewhere, you should see a massive increase in speed and feel happy for the rest of your life!

In my case the MTU is 1426, no need for a router or third party connection sharing solution afterall!

^pt^

Hmm changing MTU fixed it completely for you Fabre? I found that a while ago and thought I was onto something, but when I tested it my current MTU setting already worked fine for me. Oh well! The mystery of Windows, eh? :rolleyes:

Fabre

Yeah like I said I followed the instructions and found out that 1426 was the max mtu, created the entry in the registry and now it is working fine.
I would have never thought it would have something to do with the client machine since it worked fine when the server machine was running xp.

Must say I was lucky on that one, I stumbled upon that page while looking for some third party ICS solutions.

btw the proxy of Winroute pro worked well but msn was getting disconnected after a few minutes on the client machine.

Solidshare worked well aswell but I wasn't to sure about its firewall efficiency.

Anyway this fix worked so back to kerio 2.1.5 for protection.