MSI RG60SE

Pentru cine este interesat - am gasit versiunea amintita anterior RG60SE - Firmware 3.7.2 Build 080303 Rel.57149n
Aduce nou optiunea de "WDS Bridge" in traducere ro se poate face "wireless" intre 2 routere.
Atasez firmware si help en pt aceasta optiune

bafta la UP

Editat de rasputin, 23 februarie 2010 - 23:35.

Pentru Rasputin:

Mersi pentru firmware...caut de cateva zile pe net si nu se gaseste nicaieri. La siteurile oficiale MSI nu sunt puse, nici altundeva nu am gasit. Am gasit intamplator aici.
Ai facut un bine mare :-)) mersi :))

Bucuria a fost prea devreme :) Cand incerc sa incarc firmware-ul nou din web dupa upload da eroare:
Error
Upgrade unsuccessfully because the version of the upgraded file was incorrect. Please check the file name.

istyke, on 22nd March 2010, 16:03, said:

In momentul cand faci UP la firmware-ul ...nu trebuie sa ai conexiune internet (nu conecta router-ul la internet).
Dupa ce afiseaza ca sa efectuat UP cu succes, intrerupe alimentarea router-ului si repornestel si totodata conecteazal la internet.




Sper sa fie asta rezolvarea.
Nu e asta rezolvarea am atasat si versiunea mai veche pt firmware

Editat de rasputin, 26 martie 2010 - 22:32.

Salut
Am o problema cu internetul de o luna... Folosesc un router wireless MSI rg60se de aproape 2 ani si de o luna conexiunea la net cade; adica routerul se conecteaza singur, merge netu intre cateva minute si 1-2ore si apoi windowsul (win7) nu mai detecteaza conexiunea. In setarile routerului arata ca e conectat prin ppoe (primeste si ip-ul de la retea),dar nu mai pot naviga. Daca il deconectezsi il reconectez din router iar merge si apoi se reia problema.
Cand bag cablu in calculator merge perfect.
Am incercat sa refac setarile, sa clonez mac-ul, dar nimic...
Daca aveti vreo idee va rog sa ma ajutati...
Mersi

pe direct cum se comporta?

carmenclara1, on 29th September 2010, 02:21, said:

pe direct nu are nicio problema...

ping in ipu routerului ai, cand win7 face figuri?

carmenclara1, on 29th September 2010, 15:09, said:

nu cred ca windowsul face figuri pentru ca acelasi lucru se intampla si la laptop(conectat wireless)
cand nu merge netu in optiunile routerului totul pare ok (primeste ip, default gteway, si dns server) dar netu nu merge...

pai pe scurt ideal ar fi sa localizam mai exact problema.

ipconfig /all de pe pc cand merge si cand nu merge
ping ip router lan side
ping gateway
ping dns
ping 8.8.8.8

ce mac adress ai pe pc connectat direct cat si pe router wan side? sunt identice sau difera?

problema poate fi de la rds cat si de la faptu ca routeruu se blocheaza (p2p,heavy traffic).

NB inainte sa muti cablu de la rds intre comp si router asigurate ca dai disconnect first

am facut ce mia-i spus si asta imi apare:

Windows IP Configuration  CAND MERGE

   Host Name . . . . . . . . . . . . : mircea-PC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Bluetooth PAN Network Adapter
   Physical Address. . . . . . . . . : 00-03-0D-00-00-01
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek RTL8168D/8111D Family PCI-E Gigab
it Ethernet NIC (NDIS 6.20)
   Physical Address. . . . . . . . . : 00-1F-D0-DC-7F-FF
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::2982:b349:6782:b1e1%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, September 29, 2010 6:21:58 PM
   Lease Expires . . . . . . . . . . : Wednesday, September 29, 2010 8:21:58 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 234889168
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-10-E0-74-00-1F-D0-DC-7F-FF

   DNS Servers . . . . . . . . . . . : 193.231.189.18
                                       193.231.189.19
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{DD79B0B5-5E53-40A6-B2FF-E11131265BF5}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:200e:f43c:b08b:36af(Pref
erred)
   Link-local IPv6 Address . . . . . : fe80::200e:f43c:b08b:36af%12(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{45C1C4BF-A272-4E35-8FC0-189489B5730B}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

*******************************************************************
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=10ms TTL=54
Reply from 8.8.8.8: bytes=32 time=10ms TTL=54
Reply from 8.8.8.8: bytes=32 time=10ms TTL=54
Reply from 8.8.8.8: bytes=32 time=10ms TTL=54

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 10ms, Average = 10ms
********************************************************************

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms
*********************************************************************

Pinging 79.116.201.80 with 32 bytes of data:
Reply from 79.116.201.80: bytes=32 time=1ms TTL=64
Reply from 79.116.201.80: bytes=32 time<1ms TTL=64
Reply from 79.116.201.80: bytes=32 time<1ms TTL=64
Reply from 79.116.201.80: bytes=32 time<1ms TTL=64

Ping statistics for 79.116.201.80:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms
************************************************************************

Pinging 193.231.189.18 with 32 bytes of data:
Reply from 193.231.189.18: bytes=32 time=1ms TTL=59
Reply from 193.231.189.18: bytes=32 time<1ms TTL=59
Reply from 193.231.189.18: bytes=32 time=1ms TTL=59
Reply from 193.231.189.18: bytes=32 time=1ms TTL=59

Ping statistics for 193.231.189.18:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms
*************************************************************************

CAND NU MERGE

Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
**************************************************************************

Pinging 193.231.189.18 with 32 bytes of data:
Request timed out.
Request timed out.ping
Request timed out.
Request timed out.

Ping statistics for 193.231.189.18:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
***************************************************************************

Pinging 79.116.201.80 with 32 bytes of data:
Reply from 79.116.201.80: bytes=32 time=1ms TTL=64
Reply from 79.116.201.80: bytes=32 time<1ms TTL=64
Reply from 79.116.201.80: bytes=32 time<1ms TTL=64
Reply from 79.116.201.80: bytes=32 time<1ms TTL=64

Ping statistics for 79.116.201.80:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms
***************************************************************************

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

Editat de Ravy, 30 septembrie 2010 - 09:33.

mai verifica daca ai ping in 10.0.0.1.

daca ai ping in ambele cazuri problema e la rds.

carmenclara1, on 30th September 2010, 00:16, said:

ping in 10.0.0.1 nu merge nici cand am internet nici cand nu am
cand nu am net pingul nu merge in 8.8.8.8 si in DNS in rest in ip m,erge in ambele cazuri
e ciudat ca dupa ce ii dau disconnect merge iar pentru un timp; poate fi o problema legata de ip (se modifica la fiecare deconectare)

ca sa poti testa in 10.0.0.1  ai nevoie de arp ping nu de ping simplu. arp ping nu vine cu windows. trebuie instalat separat. de exemplu nmap.
ar fi util si un traceroute forum.softpedia.com cand nu iti merge netu.

Am folosit programulde care imi spuneai

CAND MERGE
Starting Nmap 5.21 ( http://nmap.org ) at 2010-09-30 18:38 GTB Daylight Time
Nmap scan report for forum.softpedia.com (212.146.105.234)
Host is up (0.0040s latency).
TRACEROUTE (using proto 1/icmp)
HOP RTT     ADDRESS
1   ... 12
13  4.00 ms 212.146.105.234
Nmap done: 1 IP address (1 host up) scanned in 6.18 seconds
=================================================
PT 10.0.0.1
Starting Nmap 5.21 ( http://nmap.org ) at 2010-09-30 18:39 GTB Daylight Time
Note: Host seems down. If it is really up, but blocking our ping probes, try -PN
Nmap done: 1 IP address (0 hosts up) scanned in 3.13 seconds

CAND NU MERGE
pt 10.0.0.1
Starting Nmap 5.21 ( http://nmap.org ) at 2010-09-30 20:21 GTB Daylight Time
Note: Host seems down. If it is really up, but blocking our ping probes, try -PN
Nmap done: 1 IP address (0 hosts up) scanned in 3.12 seconds
=======================================================
trace:
Starting Nmap 5.21 ( http://nmap.org ) at 2010-09-30 20:21 GTB Daylight Time
Nmap done: 0 IP addresses (0 hosts up) scanned in 12.03 seconds
Failed to resolve given hostname/IP: forum.softpedia.com.  Note that you can't use '/mask' AND '1-4,7,100-' style IP ranges
WARNING: No targets were specified, so 0 hosts scanned.

Editat de Ravy, 04 octombrie 2010 - 15:03.

eu banuiesc ca problema e la provider. ea legatura cu ei si vezi ce zic.

am luat legatura cu ei si mi-au spus ca daca merge fara router ei nu au ce sa faca; nu stiu ce s-a schimbat ca doar mi-a mers fara probleme o perioada buna de timp.
Legat de pingul 10.0.0.1 nu merge nici cand am net nici cand nu am; ce inseamna asta?

Editat de Ravy, 04 octombrie 2010 - 15:03.

ping icmp este blocat din firewall.
arp ping nu este.
10.0.0.1  este urmatorul hop/router/server intre tine si inet
fa un traceroute direct din windows catre yahoo.com si posteaza aici rezultatele si cand merge si cand nu merge

Editat de Ravy, 04 octombrie 2010 - 15:03.

Am facut un traceroute cu nmp ca din windows nu stiu...

Cand nu merge:
Starting Nmap 5.21 ( http://nmap.org ) at 2010-10-01 20:55 GTB Daylight Time
Nmap done: 0 IP addresses (0 hosts up) scanned in 14.30 seconds
Failed to resolve given hostname/IP: yahoo.com.  Note that you can't use '/mask' AND '1-4,7,100-' style IP ranges
WARNING: No targets were specified, so 0 hosts scanned.

CAnd merge
Starting Nmap 5.21 ( http://nmap.org ) at 2010-10-01 20:57 GTB Daylight Time
Nmap scan report for yahoo.com (69.147.125.65)
Host is up (0.11s latency).
Hostname yahoo.com resolves to 5 IPs. Only scanned 69.147.125.65
rDNS record for 69.147.125.65: ir1.fp.vip.re1.yahoo.com

TRACEROUTE (using proto 1/icmp)
HOP RTT       ADDRESS
1   ... 9
10  112.00 ms ir1.fp.vip.re1.yahoo.com (69.147.125.65)

Nmap done: 1 IP address (1 host up) scanned in 3.60 seconds

Editat de Ravy, 04 octombrie 2010 - 15:04.