Private class 10. IP addresses ..

D

Ditch

Well-Known Member
Joined
Feb 23, 2004
Messages
208
Reaction score
0
Location
.
Yesterday and today the ST DHCP server has been giving me private class 10. IPs .. then of course nothing works. Anyone else had this? The only thing I see on ST's notice board are extremely vague and totally meaningless allusions to a "network fault" on the 22nd, but I guess thats something else as this problem has continued today.
 
Hiya. That IP range shows up when you do a fresh install with the MyWi CD. The process kicks IE (and it *HAS* to be IE on Win_whatever (well- I've yet to see it work with Firefox or Opera!)) and the MyWi dialer logs that PC on with an account name of "new_user". Short of the regedit hack to stop this codependent behaviour this is a necessary step -and this is the time that you see that 10.x range that goes nowhere.

As to WHY you're getting that range on what I presume to be a usually working modem I can't comment.
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by bdt</i>
<br />Hiya. That IP range shows up when you do a fresh install with the MyWi CD.
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">
I know, I remember. But it wasn't a fresh install, it's been installed for months and I specifically checked that it wasn't doing the new_user thing. It just did it for a few hours, then stopped doing it. Then the next day it did it again for a few hours, then stopped again. I changed nothing - I know it almost certainly must have been a problem with their DHCP server, was just wondering if anyone else noticed it, yet I guess most would not have happened to reconnect at those times. (It didn't open IE, and happened using either the MySignal or Windows or IPWireless diallers, and happened on USB as well as PPPoE, etc. Believe me, I wasn't just having a "beginner problem"!)
 
By the looks of things, it is the classic "cookie" scenario. Very little know that the Sentech software when entering the registration page successfully, creates a hidden/read only cookie that it stores in the software directory that updates the registry. It has happened that for some reason, the updated "cookie" does not always get picked up by the UEstatus.exe so it thinks that you are not registered, therefore, the software registry entry thows you on connecting to the 10 range.

Its common in windows. Get the ethernet cable, runn pppoe098.exe and go from there. Simple to install, no hassels. The only thing when calling in for support is if something goes wrong is providing the rscp/iscp levels and frequency. Better hook the usb up before you call...
 
Uh, let me try be even clearer, since those replying don't even seem to be reading what I'm writing (exactly like tech support funnily enough - not even reading the message AT ALL but instead just quickly scanning for the first 'keywords' you recognize - hmm .. ST tech support guys posting on the forum?) .. As I <i>already</i> mentioned, it happened with BOTH the ethernet cable (PPPoE) AND the USB cable (I already had both up and running long ago). And in fact it ALSO happened on two different computers that I tried it on during the same few hours - remarkable coincidence eh? And as stated it happened with various different diallers, not just the IPWireless software. And it's never happened before .. I highly doubt this is "common in Windows", I've been following these forums for a long time and have never even heard anyone mention this happening. Sorry, I'm still convinced it was the DHCP. And btw a "cookie" has stuffall to do with registries, a "cookie" is a web browser thing. But thanks anyway for the two trying-to-be-helpful but useless/wrong answers .. I just wanted to hear from anyone else if they had seen the same thing on those days, I'm not trying to "solve a problem I'm having" because it already went away.
 
I had this problem a few months ago, you get stuck on the Auth. Server in the tower, and it doesnt route you onto the main network. There is no easy way around this. Its a tower problem. It took them allmoast a week to try and sort it out. There is more info if I can remember under the Durban section sumwhere a few pages back.

________________________________________________________________________________________


Durban Mal Park(36) 36% SNL-12 128k | D-Link Tri-Mode Dual Band Wireless router | 802.11G PCI card |irc.shadowfire.org #mywireless
 
Oh, and they gave me IP's to ping on their local "tower only" network, and I caould ping all those, but not outside the ST network at all.
It was eventually confirmed by them that it was a Tower issue.

________________________________________________________________________________________


Durban Mal Park(36) 36% SNL-12 128k | D-Link Tri-Mode Dual Band Wireless router | 802.11G PCI card |irc.shadowfire.org #mywireless
 
Interesting. So it may just have been an intermittent problem with my tower specifically. I was under the impression that the authorisation (and e.g. IP assignment) was centralised, and that TCP/IP was just layered over some IPWireless-specific comms stuff between the towers. Hmm .. that might help explain a comment I read regarding the bug they had in their authentication system .. someone said that (back then) you could use any username/password provided nobody else <i>on that same tower</i> was using it.
 
I see you also on openportal...

I blacklisted your email on bitfarm.. so who ever invite you will also get ban...
 
Last edited:
Perhaps if he had some great news like "5 years later and look:" but rez a 5 year dead thread for a bitfarm invite? I suppose that is one way to get yourself banned...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X