Mweb News Server - It ain't workin' no more!

[MWEBHelp]

Sorry to go a bit off topic,

But Mweb Guy.

What is the different in using the two different username realms?

[email protected]
[email protected]

A trace route on the @dslmweb.co.za goes via your new DBN IPC. (20ms higher latency since the implementation of the DBN IPC)
A trace route on the @mweb.co.za goes via your CPT IPC. (lower latency)

I am in Richmond KZN which is about 100KM from Durban CBD. So routing via Cape Town which is 1200KM away seems better?

Just a question, otherwise still happy with MWEB!!!

Hi Hummercellc,

The username is for authentication purposes and I would advise using the dslmweb.co.za.

Please can you provide me the traceroutes as well so that I can provide it to the relevant persons to look at.

Kind regards,
MWEB Guy

 

[Will@MWEB]

Hey Will

Thanks for the call today(or yesterday)! Was awesome chatting with you.
I played around with the DNS settings a bit. Tried different DNS IP's that I could remember. And also tried it again on automatic settings. No luck unfortunately. I'm now running 2 connections to news.mweb.co.za, which resolves to 196.82.182.50 when i do a tracert on it. I presume this is the CT cluster's IP? I'm also running the other 2 connections using the same IP itself.
Will keep them running incase you need to monitor.

Here are my tracert results just incase:

Tracing route to news.mweb.co.za [196.28.182.50]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms mygateway.ar7 [192.168.1.1]
2 197 ms 132 ms 61 ms 41 [41.133.102.1]
3 21 ms 21 ms 31 ms te1 [196.28.178.178]
4 20 ms 23 ms 22 ms Vlan92.cpt [196.28.179.11]
5 23 ms 22 ms 23 ms 196 [196.28.178.34]
6 23 ms 22 ms 23 ms news.mweb.co.za [196.28.182.50]

Trace complete.

Hi Empie

I am sending you a PM regarding this. Please take a look and let me know if it helps.

 

[Empie]

Thanks for the PM Will. I think its all working proper now!
It seems, the culprit was the Window's Firewall. Odd that turning it off now, solved the problem. Since I turned it off quite a few times during the last 2 months with hope it will fix the issue.
I assume it could originally have been both the DNS thing that resolved to the JHB cluster and the firewall causing the problem. With the DNS now pointing me to CPT, turning the firewall off this time cleared things up. Or something like that.
But never the less, problem solved!

Thanks Will and Guy! I owe you a bells!

 

[Will@MWEB]

Thanks for the PM Will. I think its all working proper now!
It seems, the culprit was the Window's Firewall. Odd that turning it off now, solved the problem. Since I turned it off quite a few times during the last 2 months with hope it will fix the issue.
I assume it could originally have been both the DNS thing that resolved to the JHB cluster and the firewall causing the problem. With the DNS now pointing me to CPT, turning the firewall off this time cleared things up. Or something like that.
But never the less, problem solved!

Thanks Will and Guy! I owe you a bells!

Great stuff, glad you have it sorted, come join us for some BF3 some time - you'd be surprised how many of the old school guys are still doddering around the battlefield