ports question about VMC on E220

E

eboo

Active Member
Joined
Jul 11, 2006
Messages
87
Reaction score
1
Hi

I have a a E220 modem (frimware 11.110.05.00.00)with VMC lite version3.2.1.156 running on my WinXP notebook. The moment VMC launches, I see noticed that a whole bunch of ports on my machine are placed in a TIME_WAIT state (I can see this by using Netstat). As soon as I disconnect VMC, all the ports are then released form this state.

XP is up to date with all patches, Anti virus as well, and I've run spyware checks as well. I then checked with a few work colleagues that also use VMC and the E220 modem. Their machines exhibit the same behavior. I'm not sure what verisons of the VMC or drivers they were using. I'm assuming it is the versions that were shipped by default from Vodacom.


Another thing is that it seems to cycle through a whole bunch of ports. Are other people experiencing the same issue? Can someone provide me with feedback as to why this happens?

Please note that my connection is fine and I dont seem to be "losing" any bandwidth.


Here is the partial output of my Netsat - o -a:

TCP EBRAHIM_SM:doom localhost:4242 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4243 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4244 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4245 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4246 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4247 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4248 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4249 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4250 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4251 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4252 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4253 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4254 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4255 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4256 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4257 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4258 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4259 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4260 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4261 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4262 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4263 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4264 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4265 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4266 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4267 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4268 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4269 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4270 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4271 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4272 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4273 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4274 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4275 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4276 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4277 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4278 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4279 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4280 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4281 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4282 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4283 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4285 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4286 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4287 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4295 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4296 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4298 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4299 TIME_WAIT 0
TCP EBRAHIM_SM:doom localhost:4300 TIME_WAIT 0
 
Last edited:
Iam3G said:
Port 666 :D We still haven't figured out what this is...
Click to expand...

I cant believe that Vodacom still cant give us an answer as to why this happens.

btw, I saw the posts in the other thread about this issue, I'm hoping that the vodacom rep on this forum has gotten some sort of feedback on this issue by now
 
eboo said:
Can someone provide me with feedback as to why this happens?
Click to expand...
I thought this was already covered in another thread. VMC Lite has one component that grabs the serial port and communicates directly with the device and another component that handles the GUI. The open ports are the method that the components communicate with each other.
Note that all the ports are on localhost, not your external interface, so you are not open to attack.
 
has anyone managed to find pout why all the ports are being opened by the device?
Also is this behaviour still happeniing on newer version of the frimware? I am still on the old version?
oh yes, is this also occurrig for the newer devices as well?
 
Last edited by a moderator:
Hi

Its a local port on the computer , its only for communicating locally.

9.4.4 does not open these ports

Regards
VodacomData
 
eboo said:
has anyone managed to find pout why all the ports are being opened by the device?
Also is this behaviour still happeniing on newer version of the frimware? I am still on the old version?
oh yes, is this also occurrig for the newer devices as well?
Click to expand...

Why do these ports bother you?
 
Maybe because of the 666 normally very bad number .
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X