Did you upgrade the firmware recently? I noticed that some of the new firmware lets you assign the port for remote administration - this shouldn't apply from inside the lan, but who knows. Try
It ended up being a prob with my Winsock in the registry. After 6 days of struggling to get connected with SBC and after about dozen calls to customer support, I found this by myself.
I deleted couple of winsock entries in my registry, unbound tcp/ip from my NIC and rebooted. rebound tcp/ip, reboot, and voila.
Apparently, the install CD from SBC corrupted my winsock.
Hmmm...that's an interesting bit of information, I wouldn't have expected that. Thanks for posting the solution - it may help someone else in the future.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ - and delete the winsock and winsock2 keys and also goto - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Vxd and delete the winsock keys their too.
Uninstall tcp/ip from networking (that would be ALL instances) reboot and reinstall tcp/ip - reboot again and you'll be up and running.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.