D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: JBattin on August 17, 2009, 07:48:12 PM
-
I need some help. I have a NAS that I'm unable to get to on my 2 wireless computers but I can get to it from my 1 wired computer. I took my wireless laptop, removed the wireless adapter, then wired it, and then I can get to the NAS. This all takes place on 1 dir-655.
Can anyone tell me what setting from the wireless side would keep the wireless out but not the wired?
All help is appreciated.
-
You disabled WLAN Partition in the Advanced/Wireless settings ?
Can you ping the IP of the NAS or a wired computer ?
Internet works wireless ?
Check your firewall software settings if your home network is set to trusted (or however the firewall software will call it) for the wireless connection.
-
Try Network Filtering entering MAC and lan ip's if you haven't already done so, also with DHCP Reservations List.
-
I only use MAC Filtering. If I use Dynamic IP addresses - how does the DHCP Reservation help?
Thanks.
-
WLan partition is unchecked - what should it be?
I can ping the wired and wireless computers, but not the NAS on the 2 that are wireless. I can access the NAS setup (actually it's called Easy Search) via browser on the wired and the laptop when it's wired.
My software firewall is not the problem, because I have turned it off while testing. I left the software firewall up when I wired my laptop and I was able to get to the NAS.
Thanks for the help.
-
I only use MAC Filtering. If I use Dynamic IP addresses - how does the DHCP Reservation help?
Thanks.
You already did some of the work with Mac Filtering.
Thank about it like this, if you have ever mapped a drive in windows from one computer to another.(shared)
Every time you computer boots up it will try to establish a connection to the mapped(or shared) drive. The same Idea applies, your telling your router what MAC's go with what lan ip's.There is no discovery, no searching, the router knows it's(your other computers or devices) there from the info your enter.(MAC's,Lan IP's, computer names)
Setup-->Network Settings-->Add DHCP Reservation
-
So what you are saying is that the computer requesting the IP address will always get the same IP address when requested from DHCP if there is one assigned in the reservations list?
-
So what you are saying is that the computer requesting the IP address will always get the same IP address when requested from DHCP if there is one assigned in the reservations list?
Thats correct if you assign (for example) your NAS 192.168.0.110 your whole Internal network will always see it as 192.168.110. The router being the most important.
-
My NAS is a static IP. I have added my dynamic wireless desktop to the reservation list.
-
OK - I have bypassed the AP on the Dir-655 with a Netgear G AP. I can see the NAS and can map to it. So this tells me there is something wrong with the AP on the Dir-655. It must be a setting somewhere.
I should mention in all cases I have no problem reaching the internet.
-
how are you accessing the NAS, are you useing SMB like \\nas
if so try useing the smb address with the ip \\911.911.911.911
that always works for me, also make sure your not on your nighbors wireless address!
and make all computers inlcudeing the NAS have the same WORKGROUP name, this way \\NAS will always wwork, if the workgroup is not the same you can not use \\NAS, you will have to use \\911.911.911.911 instead.
-
All I have to do is go into the Entire Network and pull up the 1 group I have. Remember I can access the NAS through my wired computer and my desktop when I'm bypassing the Dir-655's AP and using a Netgear AP.
Thanks for the ideas.
-
how are you accessing the NAS, are you useing SMB like \\nas
if so try useing the smb address with the ip \\911.911.911.911
that always works for me, also make sure your not on your nighbors wireless address!
and make all computers inlcudeing the NAS have the same WORKGROUP name, this way \\NAS will always wwork, if the workgroup is not the same you can not use \\NAS, you will have to use \\911.911.911.911 instead.
Excellant suggestion FNAKFHE!!
Nice edit of the page Lycan ;D
-
I've tried using the IP address, but something is blocking all of the static IP's on the 655 AP, except the router.
I don't have to do anything special when I bypass the 655 AP, it just shows up in my list under the Workgroup in My Network, just like my other computers.
By the way, everything has the same WORKGROUP. Nor am I on my neighbors AP - I know because I don't broadcast my SSID, and I'm connected by SSID.
-
I've tried using the IP address, but something is blocking all of the static IP's on the 655 AP, except the router.
I don't have to do anything special when I bypass the 655 AP, it just shows up in my list under the Workgroup in My Network, just like my other computers.
By the way, everything has the same WORKGROUP. Nor am I on my neighbors AP - I know because I don't broadcast my SSID, and I'm connected by SSID.
Just a foolish guess on my part but I'd say you outside the scope of static or dynamic ip's.
from of all places Dlinks support pages
DHCP Server Settings
DHCP stands for Dynamic Host Configuration Protocol. The DHCP section is where you configure the built-in DHCP Server to assign IP addresses to the computers and other devices on your local area network (LAN).
Enable DHCP Server
Once your D-Link router is properly configured and this option is enabled, the DHCP Server will manage the IP addresses and other network configuration information for computers and other devices connected to your Local Area Network. There is no need for you to do this yourself.
The computers (and other devices) connected to your LAN also need to have their TCP/IP configuration set to "DHCP" or "Obtain an IP address automatically".
When you set Enable DHCP Server, the following options are displayed.
DHCP IP Address Range
These two IP values (from and to) define a range of IP addresses that the DHCP Server uses when assigning addresses to computers and devices on your Local Area Network. Any addresses that are outside of this range are not managed by the DHCP Server; these could, therefore, be used for manually configured devices or devices that cannot use DHCP to obtain network address details automatically.
It is possible for a computer or device that is manually configured to have an address that does reside within this range. In this case the address should be reserved (see DHCP Reservation below), so that the DHCP Server knows that this specific address can only be used by a specific computer or device.
Your D-Link router, by default, has a static IP address of 192.168.0.1. This means that addresses 192.168.0.2 to 192.168.0.254 can be made available for allocation by the DHCP Server.
Example:
Your D-Link router uses 192.168.0.1 for the IP address. You've assigned a computer that you want to designate as a Web server with a static IP address of 192.168.0.3. You've assigned another computer that you want to designate as an FTP server with a static IP address of 192.168.0.4. Therefore the starting IP address for your DHCP IP address range needs to be 192.168.0.5 or greater.
Example:
Suppose you configure the DHCP Server to manage addresses From 192.168.0.100 To 192.168.0.199. This means that 192.168.0.3 to 192.168.0.99 and 192.168.0.200 to 192.168.0.254 are NOT managed by the DHCP Server. Computers or devices that use addresses from these ranges are to be manually configured. Suppose you have a web server computer that has a manually configured address of 192.168.0.100. Because this falls within the "managed range" be sure to create a reservation for this address and match it to the relevant computer (see Static DHCP Client below).
-
I totally understand the difference between DHCP addresses and static addresses. I use a combination of both.
-
Try this, clear your logs
Connect to the NAS with the wired system then try with the wireless and compare the log.
Also ping your wireless systems in "tools" "system check".
Portforwarding may be an option.
NAT Endpoint Filtering
The NAT Endpoint Filtering options control how the router's NAT manages incoming connection requests to ports that are already being used.
Endpoint Independent
Once a LAN-side application has created a connection through a specific port, the NAT will forward any incoming connection requests with the same port to the LAN-side application regardless of their origin. This is the least restrictive option, giving the best connectivity and allowing some applications (P2P applications in particular) to behave almost as if they are directly connected to the Internet.
Address Restricted
The NAT forwards incoming connection requests to a LAN-side host only when they come from the same IP address with which a connection was established. This allows the remote application to send data back through a port different from the one used when the outgoing session was created.
Port And Address Restricted
The NAT does not forward any incoming connection requests with the same port address as an already establish connection.
Note that some of these options can interact with other port restrictions. Endpoint Independent Filtering takes priority over inbound filters or schedules, so it is possible for an incoming session request related to an outgoing session to enter through a port in spite of an active inbound filter on that port. However, packets will be rejected as expected when sent to blocked ports (whether blocked by schedule or by inbound filter) for which there are no active sessions. Port and Address Restricted Filtering ensures that inbound filters and schedules work precisely, but prevents some level of connectivity, and therefore might require the use of port triggers, virtual servers, or port forwarding to open the ports needed by the application. Address Restricted Filtering gives a compromise position, which avoids problems when communicating with certain other types of NAT router (symmetric NATs in particular) but leaves inbound filters and scheduled access working as expected.
Just curious you didn't mention what firmware your running.
DIR-655 Firmware Release Notes
=========================================
Firmware: 1.32NA
Date: 07/20/09
1. Fix when disable DHCP server and enable DHCP server, LAN PC cannot get IP.
2. Fix using wireless client to configure Access Control rules, cause DUT reboot.
3. Fix UPnP bug.
4. Disable CAPTCHA by default
5. Fixed QRS issue, can't set up wireless setting.
6. Fixed Router DHCP IP range issue.
7. Fixed WPS UI Show Error warning message.
8. Fix potential security leak with CAPTCHA.
9. Fix USB LED issue about Shareport.
10.Fix Shareport HP932C with Wins 7 issue
11. Fix if set more than 8 Trigger or Firewall port in Application Rules. It will show Warning message.
12. Fix bug: When QRS set wan type of rt to DHCP, the rt will not set Primary and second DNS.
Note: This firmware does not allow downgrading to pre-1.3x.
=========================================
Firmware: 1.31NA
Date: 04/28/09
1. New SharePort support PC/Mac (Requires New Utility Installed on PC or Mac to work)
2. Add SecureSpot 2.0
3. CAPTCHA (Cryptographic Authentication)
4. Fix DHCP server issue.
5. Modify the turn from "Network USB" to "SharePort" in the option of "My USB Type is:"
6. Add Advanced DNS Service feature.
7. Remove 3G feature (not a supported feature by North America ISP).
8. Fix LLTD wrong icon in Vista.
9. Fix reboot issue when connecting to Internet
10. Fix if set more than 8 Trigger or Firewall port in Application Rules, it will show warning message.
11. Fix bug: When QRS set wan type of rt to DHCP, the rt will not set Primary and second DNS.
12. This firmware can not be downgraded to previous versions.
13. Guest Zone disable SharePort support (USB spec v1.05)
14. Router time is not reset when factory reset.
15. Fix schedule end time error.
Note: This firmware does not allow downgrading to pre-1.3x. Please save your configuration file before the upgrade. After the upgrade, please reset to factory default, then upload the configuration file image.
=========================================
-
What type of antivirus are you running on your machines?
-
I'm running AVG and Norton. BUT - it can't be the firewall or anti-virus because I don't have issues when I use my Wireless G AP and not the 655 AP.
-
OK I had the logs set to not show INFO - once I opened it up to also show INFO I noticed that a Mac address was not being accepted. That MAC address was the same as one I already had in my MAC filter list - except in one position there should be a B instead of an 8. Once I changed that I can now get to my NAS.
The difference between my Wireless G and the 655 was that I didn't have to have wired Mac addresses in the Filter list like I do on the 655.
Thank you everyone for all of your thoughts and ideas. Hopefully I don't make this mistake again.
-
OK I had the logs set to not show INFO - once I opened it up to also show INFO I noticed that a Mac address was not being accepted. That MAC address was the same as one I already had in my MAC filter list - except in one position there should be a B instead of an 8. Once I changed that I can now get to my NAS.
The difference between my Wireless G and the 655 was that I didn't have to have wired Mac addresses in the Filter list like I do on the 655.
Thank you everyone for all of your thoughts and ideas. Hopefully I don't make this mistake again.
LOL...good for you!
Alot of trouble for that simple mistake, but it's a learning experience.
-
Uninstall Norton and see what happens.
Norton profiles network hardware by MAC address. Give it a try.
-
Thanks for the ideas Lycan - but I've resolved the issue - see above.