Jump to content

fourmyfriends

Members
  • Posts

    1
  • Joined

  • Last visited

    Never
  • Speed Test

    My Results

Everything posted by fourmyfriends

  1. I Work in a Comcast call center, specifically in internet tech support. I also subscribe to comcast and have a Webstar (Scientific Atlanta) modem. All cable modems have a boot file in them. The boot file actualy controls what kind of speeds you can recieve ('capped speed') The theroretical speed capacity of MOST cable modems is virtually unlimeted, EXCEPT for restrictions in network technology speeds. The cable modem is capable of transmitting at the full capacity of you network. The boot file is pushed to your cable modem by your cable company at the time of its registration. This boot file is what tells your modem how fast it is allowed to go. It is possible that you account could have the wrong bootfile on it, however it is most comonly checked when you call for help, also if the system detects that you have the wrong bootfile, it can automaticaly push the correct file to you, so don't bother trying to overide it :police:One common problem that I find when signal levels are good, and there is no router in place (come on people lets admit it routers are falable, and as well some times do you bad or corrupt you network traffic, as the same goes for cable modems) is that there can be a problem in the way your requests are being routed through the server. This is a problem that will have to be handled by your internet provider, to check if that is what is happening it is fairly simply, In windows XP, go to the command prompt, by 1st clicking on start, and going to run, in the run box, type cmd and press OK In the command prompt ping a couple of internet sites by typing ping nameofsite.com, ie... ping www.google.com In the results you will see the actual IP address of the website you are pinging. Ping a few different sites and get a few good IP addresses Next type tracert and an IP address ie.... tracert 66.102.7.99 try it a few times to a few different IP addresses. If the connection continually times out on the first few hops, then there is a problem with the way that server is routing your connection. If it just so happens that your cable provider is the innocent person in your problems, and you cant figure out anything else to do, try this at your own caution, as it can affect the way some programs run, especially firewall software. In the command prompt (XP) type the following commands- netsh int ip reset resetlog.txt netsh winsock reset (it will tell you to restart your system, but waite.....) ipconfig /flushdns (now just restart your system) Entering these settings resets the bulk of the ways your computer handles connections. The first command resets your TCP/IP stack to defaults. The second set reset the winsock, and the final step flushes the dns (hint- a lot of times if you can ping IP addresses (external ones) but cannot ping a website by name, and the firewalls are off, often flushing the dns will completely fix this problem). When your system restarts it will automatically renew its IP address and re register the dns. you should see an improvement..... This is basically an "if all else fails" tactic. I also highly recommend free online scans from antivirus.com hey its free, live, and does spywaremalware, and viruses
×
×
  • Create New...