联系电话:888420360755-88842036 联系电话:888420360755-89800150  ☆首页 地图 帮助
在线提问
当前位置:天威宽带首页->在线提问->这里发表帖子
 

宽带申请热线

0755-88842036

天威网上申请宽带
48小时安装成功

常见问题解答

常见问题

基础知识

地址设置

使用问题

其它问题

程序下载

路由器设置

工程师现场在线答疑

天威网速测试

1、更换电脑或者网卡后,为什么不能上网了?
2、怎样才可以使用另外一个IP地址?
3、能否同时看电视及上网?
4、是否可以自行购置MODEM来实现上网?
5、为什么不能访问某些网站?
6、Cable Modem 指示灯正常,QQ等能上,为何不能浏览网页?
7、可以ping通,但所有网站都上不了
8、速度是多少?在上网人数增多的情况下速度会否变慢?
9、电脑开始能上网,但过了一会儿约10分钟没有使用就上不了,为什么?
 
看看其它网友是否有相同的问题? ===>

<< 返回在线提问 主题:到底是机房问题还是我的MODEM问题?[ 楼 主 ]
 作者:还我流畅网络 2007-3-8 0:10:35  
1.这里的管理员是天威工程师吗?
2.我打开192.168.100.1里面的LOGS是:
1970-01-02 01:11:02 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-02 00:22:21 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-02 00:21:02 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:01:46 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:01:02 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:57 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:49 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:00:49 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:00:26 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:00:26 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:20:32 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:05:28 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:05:22 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:05:18 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:05:17 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:05:11 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:05:10 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:05:05 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:54 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:41 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:40 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:39 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:39 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:19 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:18 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:16 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:15 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:11 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:10 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:55 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:54 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:52 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:43 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:31 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:31 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:19 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:14 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:13 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:05 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:27 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:26 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:22 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:21 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:10 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:08 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:00 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:48 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:27 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:26 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:21 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:21 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:19 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:18 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:18 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:32 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:21 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:21 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:14 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:13 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:13 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:12 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:08 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:07 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:58 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:21 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:13 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:12 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:07 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:06 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-06 11:33:18 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-06 11:33:14 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-06 11:33:04 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-06 11:32:51 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-06 11:32:51 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-06 11:32:26 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-06 11:32:15 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-06 11:32:15 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-06 11:32:07 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-06 11:32:07 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-06 11:32:07 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-06 11:32:06 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-06 11:32:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-06 11:32:01 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-06 11:31:56 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-06 11:31:55 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-06 11:31:55 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
1970-01-06 11:31:55 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
Event Log has reached maximum size. Older log entries are lost.


情况如下:年初九开始网络很慢,经常打不开网页,玩CS延迟,玩魔兽争霸Ⅲ吊线,这两天QQ还经常吊线,BT不能用偶尔几K,基本上都没有数据,FLASHGET和讯雷才几K左右,当网页打不开时重新启动MODEM有些网页就可以打开了,但是没过多久又不行了.股票买卖的时候提示``网络延迟,检查网络``...
2月28号还是3月号已经打电话给83060666技术员上门来检查了,但是他说是新秀村机房问题(我是住罗湖区春风路向西村,离新秀村也不是很远.)
,他还故意打开了你们天威类似你们内部人员的社区吧,里面有个通告说:最近什么什么网络慢,什么新秀机房问题,然后一切为截取图片为准。大致是这些内容拉,但是我总觉得是MODEM问题,要求换MODEM,可是他不肯,说如果是MODME的问题的话可以换给你,于是我家人正好煮好饭就让他留下来一起吃饭(呵呵,遇到像我家里人的这些客户的真好,不过小事一盅,反正都已经是中午了,也不好意思让他急忙的上来我家,又匆忙的走。)之后吃完饭后就开始截取他的图片回总部,临走前就说应该过几天就能解决机房的问题。
直到3月6号我又打电话83060666,里面的一个技术员又说已经有很多人反映这个情况了,我们会尽快的解决的。。
到底什么时候才能解决啊???是MODEM的问题还是机房的问题啊?怎么都没有在网站里通告的???刘德华都有说拉“今时今日嘅服务态度系晤够噶”,我要肯定的答复啊...
我3月4号正好学会使用IIS搭建网页.http://222.248.141.124/ 好不容易才会搭建,网络就这样的不行,我在瑞星,金山,江民,等知名网站都让人家帮我测试这个网页,人家从我电脑里下载有的1K多,有的零点几K,一百多个人测试,只有2个是20K左右..
 回复:到底是机房问题还是我的MODEM问题? 1
 作者:花猫 2007-3-8 19:54:21  
192.168.100.1里的log普通用户没必要关心和查看,这个不一定是MODEM问题,上门工程师如果说不是MODEM问题,用户可以要求维护人员带MODEM上门测试.如果工程师说是客户电脑问题,用户可以要求工程师带笔记本上门测试
 回复:到底是机房问题还是我的MODEM问题? 2
 作者:花猫 2007-3-8 19:57:36  
当觉得网速慢时,用户可以通过在天威内部网站上下载文件测试看速度以判断是天威网内问题还是网外问题,大家可以下载这个:http://www.topway.cn/service/yhsc.doc 当下载这个文件很快,而做其它东东很慢时,就有可能是天威网外的问题,比如服务器限流之类的
 回复:到底是机房问题还是我的MODEM问题? 3
 作者:还我流畅网络 2007-3-8 21:16:31  
之前LOGS里面并不是显示这样的。。就算不是实时的记录日志,但是最起码年月份都要准确啊。。
你提供的WORD能打开啊,今天的网速稍微提升了一点,起码瑞星,金山和江民的网站不用刷新几十次或者隔一段时间才能打开,升级杀毒软件的病毒库不用升5-6次才能正常升级,虽然升级还是慢,但是看股票还是会提示网络延迟。
我所说的网速慢是从年初九开始的,年初九之前都还好的,这绝对是天威的问题,可是我并不是天威的人,所以不知道到底是技术员说的机房问题还是MODEM问题,我的电脑绝对没有问题,因为我是两台电脑的,我的路油器更加没有问题,因为拔掉路油的线都是一样的问题
 回复:到底是机房问题还是我的MODEM问题? 4
 作者:花猫 2007-3-8 22:34:25  
有问题请打83060666申报故障,会有工程师处理
 回复:到底是机房问题还是我的MODEM问题? 5
 作者:还我流畅网络 2007-3-8 22:55:56  
我上面已经写了,,,已经是打了,可是啊 工程师就是说机房问题。。。
所以不知道这里的管理员知不知道到底是什么情况。。。
 回复:到底是机房问题还是我的MODEM问题? 6
 作者:【热心人】 2007-3-11 15:53:29  
我是天威维护部的,年初七开始,新秀3/3机房端口扩容,访问网站使用电信服务器都受影响,现象为ping网站延时正常,丢包20%左右,网站使用网通服务器不受影响,网速正常,因深圳本地网站多为使用电信服务器,现象明显,已在处理中,现在下载,游戏请使用网通区
 回复:到底是机房问题还是我的MODEM问题? 7
 作者:【热心人】 2007-3-11 18:51:03  
我好象没有去过你家吧,你那边好象都是我去哦...
HOHO!
有空和我联系撒!
 回复:到底是机房问题还是我的MODEM问题? 8
 作者:【热心人】 2007-3-11 18:52:42  
绝对不是MODEM问题,问问周围其他人,都是这样的啊,你就 鄙视天威吧...

哈哈...

盔甲!!!!!!!!!!
 回复【热心人】 9
 作者:还我流畅网络 2007-3-12 1:21:40  
现在好像稍微可以了,虽然打开网站没出什么问题,有个别网站刷新几次或者打开几次就可以,但是像CS1.6和CS1.5,还有魔兽争霸3 都没有什么网通和电信之分,所以有时还是会有吊线的迹象,但是下载还是不行啊。。
请问【热心人】这些问题将会在什么时候结束呢?所谓的扩容是什么意思呢,是跟ADSL那样把2M升级为5M?也就是帮我们增加宽带的速度吗。
 回复:到底是机房问题还是我的MODEM问题? 10
 作者:【热心人】 2007-3-13 8:33:48  
听说是电信与天威二公司之间的问题,电信天威的矛盾到底是如何??我们不得而知,但却造成了现在这么慢的网速。
希望他们能协商好,尽快解决
 回复:到底是机房问题还是我的MODEM问题? 11
 作者:管理员 2007-3-13 12:51:31  
非常感谢楼上这位朋友的支持与理解,请相信我们有责任有能力处理好的。谢谢您的支持。
 回复:到底是机房问题还是我的MODEM问题? 12
 作者:【热心人】 2007-3-13 13:13:26  
各位天威用户注意了,据天威内部消息,此次网速慢问题为电信机房限定天威IP段引起的,因这次所限定IP段多为新秀机房分配IP用户,所以这一片区用户多为访问电信服务器慢,天威运行部已多次扩容端口,效果不明显,已与电信协商中,但就算协商处理好新秀机房限定IP问题,电信始终要限定一定量天威IP,等于说这里好了,别的机房又不行了,总的说就是电信必须保证自己ADSL用户IP流量,天威也是没办法的
 回复:到底是机房问题还是我的MODEM问题? 13
 作者:【热心人】 2007-3-14 9:40:23  
电信也只有个深圳之窗嘛 ,仅是放在电信机房,其他很多大的内容服务商游戏商会在网通和电信机房都放置服务器,天威用户只要选择网通服务器就没问题了。

比如:中游,QQ游戏 等都可以下载网通版本或者登录网通服务器,大型网站比如新浪等就不用选择,一般情况它们会照顾到所有用户(包括网通电信);
 回复:【热心人】 14
 作者:还我流畅网络 2007-3-15 19:19:52  
这个内幕是真的吗???我现在网速还是不行啊,在线看电视看一下卡一下,缓冲很久啊。。我不玩QQ游洗,也不玩中国游洗中心,,只完CS1.6和CS1.5还有魔兽争霸三,,是用浩芳对站平台来玩的,,我想这些游戏那么经典大家都听说过的吧,,这些游戏都没有网通电信之分,,但是这些不用说都应该是电信的网络的,所以很慢啊。
 回复:管理员 15
 作者:还我流畅网络 2007-3-15 19:23:32  
管理员 你能不能说一下“热心人”说的内幕是真的吗?那么还叫人怎么弄啊,那还不如用回200元的ADSL,虽然我相信天威,但是我只想平平静静的上上网而已。。
 我的网络好慢啊 16
 作者:还我流畅网络 2007-3-15 19:26:08  
用天威的测试网络速度显示下面的内容,,晕那么慢,,怎么玩啊
您的计算机连接到TOPWAY的
速度:192 Kbps
(23.5 KBps)
 回复:【热心人】 17
 作者:还我流畅网络 2007-3-17 3:25:04  
23.5 KBps才是我真正的网速,192 Kbps不知道是什么速度来的。。。一到半夜就恢复正常,早上到晚上黄金时段就不行,23.5 KBps打开网页都慢死了,我想应该真的是机房的问题,因为住我对面大厦的那栋楼的朋友打电话给我,我过去一看,他说也是打了很多次电话给天威,开始也以为是MODME的问题。。。。唉 希望天威快点与电信妥协好啊。。
 回复:到底是机房问题还是我的MODEM问题? 18
 作者:我来回答 2010-5-26 20:04:28  
慢死了!!!!!!!!!!!!!!!!!!

回复此内容帖 ( 带 * 为必填选项 )
 发贴者姓名:  *无须注册即可发表
 发贴者邮箱: 
 帖子标题:  *
 帖子内容:  *
验证码:
深圳天威宽带申请 上网服务电话0755-88842036,天威有线宽频资费标准E版50元包月经典版100元包月(须预付1100元包一年);2M高速宽频上网,在线申请www.96355.com,深圳天威宽频免初装费优惠活动。

深圳宽带|关于我们|资费标准|网上申请|在线提问|覆盖范围|最新资讯|网上营业厅|手机版

深圳天威宽带申请热线:联系电话:888420360755-88842036 联系电话:888420360755-89800150点这里给我发消息 点这里给我发消息 点击这里发给我消息
地址:深圳市福田区彩田路6001号(彩田基地518036)
深圳市威威上网络有限公司 @96355.com,All rights reserved. 备案/许可证号:粤ICP备15004170号-2