Hi all,
i've b2 connect to a router. in lan it works fine, a part some access problem in some clients..., but in wan access happen a strage thing:
if i type Public IP adress from a mobile phone (Windows mobile based) i connect perfectly. If i try to connect from a laptop with an adsl or from a laptop with a umts connection (the same connection of mobile phone...) i'm not able to connect! Wait connection for ever! If i PING from laptop with adsl or gprs the ping works fine.
So i think that is a problem of firewall or browser configuration, as browser i've try with explorer 7, firefox 3 and google chrome but the problem is the same.
Any ideas?
thanks
Please note the new address for this forum : forum.excito.org. The old address redirects here but I don't know for how long. Thanks !
New user's registration have been closed due to high spamming and low trafic on this forum. Please contact forum admins directly if you need an account. Thanks !
STRANGE B2 WAN ACCESS!
For give an update about situation.
With a Linux (ubuntu) based pc with firefox or a mac (leopard) is possible to access to web interface from wan with the same adsl or the same umts key that won't works in my Windows xp laptop. So at that point is a windows problem because i've try with 3 different windows browser but the thing remain the same. So any suggestions?
Many thanks
With a Linux (ubuntu) based pc with firefox or a mac (leopard) is possible to access to web interface from wan with the same adsl or the same umts key that won't works in my Windows xp laptop. So at that point is a windows problem because i've try with 3 different windows browser but the thing remain the same. So any suggestions?
Many thanks
Hi,
The reason for asking you to try the above mentioned workaround, is that this "bug" is dependent on how things are aligned in the actual tcp packet.
It is possible that different OS:es align data in the tcp packets differently (a bit too far into the tcp/IP stack for me...)
Did you try the workaround?
/PA
The reason for asking you to try the above mentioned workaround, is that this "bug" is dependent on how things are aligned in the actual tcp packet.
It is possible that different OS:es align data in the tcp packets differently (a bit too far into the tcp/IP stack for me...)
Did you try the workaround?
/PA