Re: Απάντηση: Δοκιμή του Mede8er MED400X
Αντιστοιχα, οταν εγκατέλειψα την προσπαθεια να συνδεθώ ασύρματα με laptop στο δικτυο, είχα κλειστο το laptop και μετα προσπαθησα να συνδεθω με το mede8er...
Αυτο που παρατηρησα ειναι οτι στο router, στο DHCP client list, το mede8er παιρνει IP αλλα δε φαινεται το name του device, και ισως αυτο έχει να κανει με αυτο που αναφερεται στο mede8er forum:
**QUOTE**
The Med500 NAS keeps appearing and disappearing as we know. But disappearing from what?
http://support.microsoft.com/kb/105997
So we have two issues. DNS problems causing the Med IP to vanish, and WINS problems cuasing the Med to not appear in the Network Discovery Display. Windows performs Network Discovery by requesting devices to send their Names, not IP's. Not all routers can pass this request, expecting instead for Network Discovery to request IP's from devices.
To solve this we must avoid contention with the automatic systems which should be doing the job. Files are used by Microsoft for that very purpose. If Networking was totally reliable those files would never have been created. They have been in use since the start of TCP/IP and Unix. You will find the same files are part of the TCP/IP system of other operating systems. They exist to workaround the very problems we are having with the Med500 and some Networks.
These instruction are based on Windows 7.
1) Set Manual IP settings in the med500, and PC so that the both have fixed addresses (outside of the DHCP pool).
We now need to get the Med500 to always be part of the DNS and Network Discovery information.
2) Create the Network Discovery WINS Lmhosts file.
Open and save the document attached below to your default download folder. This is a new Lmhosts file. Edit the downloaded lmhosts.doc document to match the address you gave your Med500, and save as lmhosts.txt (not .doc!!!). This will be used later so remember where it is.
3) Modify the default DNS Hosts file.
Goto Accessories and open Notepad with Administrator Priveledges
Open \Windows\System32\drivers\etc\hosts from within Notepad.
Copy, and paste the line below to the end of the file.
192.168.2.202 MEDE8ER
Edit to match the IP you gave your Med, and make sure there is a final Carriage Return by pressing Enter after MEDE8ER to create a new blank line.
Save file (ignoring any request to change format to TXT).
4) Use the lmhosts.txt file.
Open Network and Sharing Center. Select Change adapter settings. Double click on the adpter you are using. Select Properties . Select IPV4 - Properties. Select Advanced - WINS. Select Enable LMhosts Lookup, and press Import LMHOSTS and browse to select lmhosts.txt where you saved it. Also select "Netbios over TCP/IP" if you havn't yet followed the advice in the "Beginners Guide".
Press all the OK's and final Close to exit Adapter Settings. Reboot
The Med500 should now be more reliable in both TCP and Network Discovery on the PC.
Reliabilty of Network Discovery still seems dependent upon which order the Med500 is turned on WRT the router and PC. Windows 7 has a particuler dislike to non-Windows 7 devices. It can take 15 mins for it acknowledge their presence!
But the DNS fix still works when that fails. So it worth having a Shortcut to \\MEDE8ER on your Desktop. This opens a Network Explorer Window, similer to the normal Windows Explorer Window. It even gets the Med added to the list of Network Devices!
Rare Problems
Even after following the above, you may still across some rare problems
1) Networked Folders are visible but can't be opended
Follow this Tip
http://www.mede8erforum.com/index.php/topic,4427.0.html
2) Believe it or not, but your Network may not be working becuase your clocks are out of step!
http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/68ffbe2a-09a7-4e29-859c-ca1aaf75dcd1
Make sure your Med's internet clock is working and in synch with your PC. It everything has stopped working since the end of Summer time, you now know why.
....now we need the PC to appear more reliably at the Med500 end!
In general, becuase the PC has the Med fixed in it's IP Cache by the fix's above, the Med connects to the PC far more reliably as well!
Addendum
Here are the locations of these files in other Operating Systems. It is probaly safer to edit these and not replace the Lmhosts with my windows file.
Ubuntu users can find their versions here:-
http://manpages.ubuntu.com/manpages/hardy/man5/hosts.5.html
http://manpages.ubuntu.com/manpages/hardy/man5/lmhosts.5.html
OSX users can find their versions here:-
http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man5/hosts.5.html
http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man5/lmhosts.5.html
**UNQUOTE**
Σ'ευχαριστω, το Mede8er ομως ήταν κλειστο οταν προσπαθούσα να συνδεθώ ασύρματα με το laptop στο desktop...μμμμ...θελω να τσεκαρεις κατι..με το mede8er κλειστο,συνδεσου ασυρματα απο το λαπτοπ στο Belkin...οταν συνδεθεις,συνδεσου ασυρματα και με το mede8er και δες τι κανει το λαπτοπ...
Αντιστοιχα, οταν εγκατέλειψα την προσπαθεια να συνδεθώ ασύρματα με laptop στο δικτυο, είχα κλειστο το laptop και μετα προσπαθησα να συνδεθω με το mede8er...
Αυτο που παρατηρησα ειναι οτι στο router, στο DHCP client list, το mede8er παιρνει IP αλλα δε φαινεται το name του device, και ισως αυτο έχει να κανει με αυτο που αναφερεται στο mede8er forum:
**QUOTE**
The Med500 NAS keeps appearing and disappearing as we know. But disappearing from what?
http://support.microsoft.com/kb/105997
So we have two issues. DNS problems causing the Med IP to vanish, and WINS problems cuasing the Med to not appear in the Network Discovery Display. Windows performs Network Discovery by requesting devices to send their Names, not IP's. Not all routers can pass this request, expecting instead for Network Discovery to request IP's from devices.
To solve this we must avoid contention with the automatic systems which should be doing the job. Files are used by Microsoft for that very purpose. If Networking was totally reliable those files would never have been created. They have been in use since the start of TCP/IP and Unix. You will find the same files are part of the TCP/IP system of other operating systems. They exist to workaround the very problems we are having with the Med500 and some Networks.
These instruction are based on Windows 7.
1) Set Manual IP settings in the med500, and PC so that the both have fixed addresses (outside of the DHCP pool).
We now need to get the Med500 to always be part of the DNS and Network Discovery information.
2) Create the Network Discovery WINS Lmhosts file.
Open and save the document attached below to your default download folder. This is a new Lmhosts file. Edit the downloaded lmhosts.doc document to match the address you gave your Med500, and save as lmhosts.txt (not .doc!!!). This will be used later so remember where it is.
3) Modify the default DNS Hosts file.
Goto Accessories and open Notepad with Administrator Priveledges
Open \Windows\System32\drivers\etc\hosts from within Notepad.
Copy, and paste the line below to the end of the file.
192.168.2.202 MEDE8ER
Edit to match the IP you gave your Med, and make sure there is a final Carriage Return by pressing Enter after MEDE8ER to create a new blank line.
Save file (ignoring any request to change format to TXT).
4) Use the lmhosts.txt file.
Open Network and Sharing Center. Select Change adapter settings. Double click on the adpter you are using. Select Properties . Select IPV4 - Properties. Select Advanced - WINS. Select Enable LMhosts Lookup, and press Import LMHOSTS and browse to select lmhosts.txt where you saved it. Also select "Netbios over TCP/IP" if you havn't yet followed the advice in the "Beginners Guide".
Press all the OK's and final Close to exit Adapter Settings. Reboot
The Med500 should now be more reliable in both TCP and Network Discovery on the PC.
Reliabilty of Network Discovery still seems dependent upon which order the Med500 is turned on WRT the router and PC. Windows 7 has a particuler dislike to non-Windows 7 devices. It can take 15 mins for it acknowledge their presence!
But the DNS fix still works when that fails. So it worth having a Shortcut to \\MEDE8ER on your Desktop. This opens a Network Explorer Window, similer to the normal Windows Explorer Window. It even gets the Med added to the list of Network Devices!
Rare Problems
Even after following the above, you may still across some rare problems
1) Networked Folders are visible but can't be opended
Follow this Tip
http://www.mede8erforum.com/index.php/topic,4427.0.html
2) Believe it or not, but your Network may not be working becuase your clocks are out of step!
http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/68ffbe2a-09a7-4e29-859c-ca1aaf75dcd1
Make sure your Med's internet clock is working and in synch with your PC. It everything has stopped working since the end of Summer time, you now know why.
....now we need the PC to appear more reliably at the Med500 end!
In general, becuase the PC has the Med fixed in it's IP Cache by the fix's above, the Med connects to the PC far more reliably as well!
Addendum
Here are the locations of these files in other Operating Systems. It is probaly safer to edit these and not replace the Lmhosts with my windows file.
Ubuntu users can find their versions here:-
http://manpages.ubuntu.com/manpages/hardy/man5/hosts.5.html
http://manpages.ubuntu.com/manpages/hardy/man5/lmhosts.5.html
OSX users can find their versions here:-
http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man5/hosts.5.html
http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man5/lmhosts.5.html
**UNQUOTE**