Nedbank/Netbank

[ednetday]

Is anyone else having a problem connecting to https://netbank.nedsecure.co.za? I can connect to it faultlessly over adsl but as soon as I hook my pc up to iburst - nothing. Not even an error message in my browser. Both scanarios from behind a smoothwall box.

As you can probably guess, iburst support says its a Nedbank problem. Nedbank says its an iburst problem, "to do with certificates".

I can connect to Standard Bank over https no problem whatsoever.

Traceroute shows this:

[root@plato edward]# traceroute netbank.nedsecure.co.za
traceroute to netbank.nedsecure.co.za (168.142.240.40), 30 hops max, 38 byte packets
1 smoothwall (192.168.0.252) 1.287 ms 1.149 ms 1.157 ms
2 196.30.31.100 (196.30.31.100) 235.887 ms * 261.136 ms
3 196.30.31.193 (196.30.31.193) 190.274 ms 199.115 ms 230.236 ms
4 fe6-1.gw10.jnb6.alter.net (196.30.31.254) 235.037 ms 259.261 ms 248.499 ms
5 fe1-0.br1.jnb7.alter.net (196.31.17.162) 261.836 ms 286.402 ms 259.891 ms
6 as3741.rba.is.co.za (196.30.228.242) 295.223 ms 375.111 ms 399.488 ms
7 ch9-rba-fa0-0.rtr.isnet.net (196.26.0.16) 474.996 ms 474.282 ms *
8 168.209.89.66 (168.209.89.66) 618.928 ms !X 134.003 ms !X *

My smoothwall box shows this in the logs:

Date:12/20 12:01:56
Name: ICMP Destination Unreachable (Communication Administratively Prohibited)
Priority: 3
Type: Misc activity
IP info: 192.168.0.121:49931 -> 168.142.240.40:33457

This appears to be telling me that Netbank is refusing my connection intentionally?

I have now made a total of 11 phonecalls to tech support since Friday afternoon in an effort to get to the bottom of this. So far nada, although Portia was good enough to call back this morning - no solution though.

And oh yes, I am running Linux on the desktop.

Any ideas?

[ic]

Well, I have just tried it (after having to reconnect several times), and FireFox gets there without a problem. You probably tried when the burst was not bursting...

[DFantom]

Loads fine here. I had very similar problems a while ago with a connection sharing I was using, changed it to be a proxy and it fixed up it up. I never got to the bottom of it but it appeared to be DNS related

[asmith]

Could be a path MTU discovery problem. Often happens with firewalls envolved (at either end). Download DRTCP http://www.dslreports.com/drtcp
and try and change your MTU size down to 1200.