Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Resolve a file sharing / wireless networking problem Network
I have a D-Link 614+ and the 800AP access point setup in my apartment, with a G4 tower at the 614+, and a 12" PowerBook wirelessly connected. I was having problems connecting to file sharing if I was connected to the access point, but not if I was connected to the 614+ itself; there were no other problems.

I figured out that even though i had the tower connected via Ethernet to the 614+, it was being given two IP addresses: one for Ethernet, and one for AirPort. This didn't impact any other operations, but for some reason, it just wouldn't work conecting through the access point. I turned off AirPort in the tower, and the problem was solved. I'm sure this affects a very small number of people, but it was very frustrating and I didn't find any info about it on the web.
    •    
  • Currently 1.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (1 vote cast)
 
[7,619 views]  

Resolve a file sharing / wireless networking problem | 7 comments | Create New Account
Click here to return to the 'Resolve a file sharing / wireless networking problem' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Resolve a file sharing / wireless networking problem
Authored by: robJ on Aug 25, '03 10:35:43AM

The D-Link 614+ has a MAC filter that could be set up so that the tower's Airport card would not be assigned an IP address.



[ Reply to This | # ]
Resolve a file sharing / wireless networking problem
Authored by: wsdr on Aug 25, '03 10:36:22AM

This reminds me of a problem that I have yet to find an answer to, regarding Airport networking in general. My home is laid out in such a way as to prevent full end-to-end coverage for Airport access using only one base station. So I have two base stations, one at each end of the house. They are both connected to a central switch, and my internet router is connected to the same switch (as are some other computers/servers). Each Airport is configured with the same network name (our family name) and is set up in Airport to Ethernet bridge mode. This works seemlessly as I move through the house with my or my wife's laptops-- I never loose an internet connection (ssh session, Timbuktu, etc.) while moving from base station to base station.

The problem that I frequently run into is when trying to connect from one Airported computer to another. If the two computers are using the same base station, they connect fine; if they are on different base stations, they can "see" each other (either using Connect to server... or via Timbuktu) but they can't connect.

In my observations of Aiport to Airport file transfers, I've noticed that the base station does not appear to have any activity appearing while the two Macs are moving data. I infer from this that the Macs connect directly to each other in order to move data more efficiently-- makes sense to me. But I think that is the root of the problem-- that they try to connect directly to each other. So when they are actually on different base stations, they attempt to connect directly, and never fall back to connecting via the base station.

Anyone else experience this? Is there a cure?

One thought I had was to create two different network names for my network-- but then I am afraid that moving between stations won't be so seemless. I'd hate to lose an ftp, Timbuktu or ssh session when moving.



[ Reply to This | # ]
Resolve a file sharing / wireless networking problem
Authored by: Deut3221 on Aug 28, '03 10:05:10PM

I too have been unable to connect by iBook and TIBook when they are accessing separate Airports. However, if I connect them through the same Airpot, no problems. They instantly connect. Weird and anoying.



[ Reply to This | # ]
Speed problems and other problems too
Authored by: paulio on Aug 25, '03 11:57:53AM

The IP address problem is more common then you might think. I've seen this before a number of times. I've seen this on campus networks as well as household cable modems. Here is the situation:

Two machines are behind a cable modem/DSL. (There is no router or airport in this simple example.) Both machines get IP addresses from the ISP like 111.222.333.xxx and 111.222.444.xxx. For whatever reason, the netmask is 255.255.255.0. Note that with this netmask these IP addresses are not in the same subnet.

The machines can't see each other in the server browser because rendezvous works only for machines in the same subnet, but one machine can share files with the other machine as long as you type in the IP address manually.

The problem is that large file transfers are slow. The reason is that the machines are on different subnets so they cannot communicate directly, even though they are physically on the same local network. The packets must go from the first machine over the local network, then out the cable modem to the internet, then back in the cablem modem into the local network, to the second machine.

This is really slow. File transfers that should take minutes take hours.

Try doing a Retrospect backup like this (which _can_ see the other machine for some reason, dispite the IP address problems) and it will take forever.

This situation with a Retrospect backup over a metered connection where internet access is paid for by the byte and you could have a financial disaster.



[ Reply to This | # ]
Resolve a file sharing / wireless networking problem
Authored by: moshingkow on Aug 25, '03 01:02:56PM

my problem is that i have a laserjet 4mv, which is a network printer. I have it plugged into a Linksys 4 port AP and router. i can print fine from the wired computers, but alas, i cannot print from the wireless computers. they are all on the same subnet with the same subnet mask.



[ Reply to This | # ]
Appletalk?
Authored by: paulio on Aug 25, '03 02:10:47PM

You should know that Appletalk packets are not forwarded by the Linksys AP router. A real Airport does forward them properly. There are two possible solutions:

- If the printer supports IP printing, give the printer a static IP address in the range of the access point (192.168.1.x) and connect to the printer using IP printing.

- Or on the desktop machine connected to the Linksys AP router by ethernet, share the printer. Printer sharing uses TCP/IP which works well with the router. The desktop machine will have to be on and not sleeping for the print sharing to work. Turn on sharing in System Preferences | Sharing.



[ Reply to This | # ]
Resolve a file sharing / wireless networking problem
Authored by: butterfi on Aug 25, '03 01:25:57PM

One caveat: Appletalk can only be implemented on one network interface. I discovered this when I couldn't print through my airport connection, but could through my ethernet connection. You actually need to go into network preferences and enable Appletalk on the interface you are currently using.

That may help...



[ Reply to This | # ]