Thanatoast

I am having a bit of a problem. I will explain what I have done and what is happening now below.
I have a cable modem connected to a wired router. All of my desktop machines and a wireless router are connected to that router. Originally I could not get anything but internet access to work with this arrangement. I tried wireless syncing but could not get it to work. I ran a packet sniffer (Ethereal) and finally found that my Axim was asking the router for "athlon" (the name of the machine it syncs with). A litte research (on aximsite, of course) turned up Pocket Hosts, which I setup to have athlon as 192.168.0.5. Tada! I could now sync. Now the next problem is that I would like to access the shares on that computer as well. I have had no luck at all (Error connecting to resource). Ethereal shows nothing from the Axim when I attempt to access a share.
What I have seen, packet-wise, is when I first turn on wireless on the Axim, there is a TCMP time-to-live exceeded packet from the wireless router to the cable router. I have also seen a (failed) DNS query for isatap.wavecable.com. wavecable is my isp, and I use the Axim to directly connect to mail.wavecable.com to check my mail, but I have never given it that address; "isatap.wavecable.com."

From what I can find "isatap" is a version of, or something like, VPN.
I am guessing that somehow my Axim thinks that isatap.wavecable.com is my VPN and when it fails to find it it does not even try to access the shares when I make the attempt.
Is anyone familiar with this problem or have any suggestions on accessing the shares?

Thanks!

Howard2k

Could it be appending wavecable.com to isatap due to the DNS config?

The Axim gets an IP address from the wireless router right? So you have three subnets. Network 1 is the Wireless LAN, Network 2 is the wired LAN and Network 3 is the Internet.

Does the WAN interface on the Wireless router connects to the Wired router's LAN interface? Or did you connect the LAN interface on the wireless router to the LAN interface on the wired router? Which would give you two networks.

There is a free tool called vxUtil. You can use that to ping your PC (that is sharing) by IP address (to verify IP connectivity) and by name (to verify name resolution).

If you can ping by both IP and Name then it's a higher level issue.

__________________
Always read stuff that will make you look good if you die in the middle of it.

Thanatoast

Thanks for answering, Howard.
You were right. The wireless router was appending wavecable.com to the isatap DNS request. I still have no idea why it is asking for isatap (or why the wireless router "knows" to add wavecable.com), but I added isatap to pockethosts to point to 192.168.0.5, since that is the only "local" machine it should be talking to anyway (at least for now).

I already installed PocketPing which showed that I could ping 192.168.0.5. (TCP stuff works fine)

I am still unable to access the shares, but now I can see 192.168.0.5 try to answer, but instead of the desktop machine talking "through" the router, it is trying to talk directly to the Axim, using the IP address that the wireless router assigned it. (192.168.0.5 is trying to talk to 192.168.0.101 directly, instead of answering 192.168.0.3). (ICMP seems to not be working)

I connected the Wireless router's WAN port to the lan, so I have two "nested" networks. Would it work any other way?

star882

Quote:

I connected the Wireless router's WAN port to the lan, so I have two "nested" networks. Would it work any other way?

Connect the LAN cable to the LAN port.

__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

TCPA would take your freedom! Say NO!
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

HDTV the way it should be:
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

Originally Posted by A friend of mine who has a Linux kernel named after his girlfriend.

If I was VirtualBox, I could load my virtualization module into Hannah and boot up another kernel in the same address space.

Howard2k

IF you connect the two LAN ports you need to use a cross-over cable, unless the router detects MDIX or has an MDIX port. But it would simplify your network. Either way - it is possible to make it work.

What subnet is on each network?

Network 1 the wireless, Network 2 being the wired and network 3 being the Internet.

Of course - Network 1 includes wired ports too since the wireless router has LAN ports. But let's just call it the wireless LAN for simplicity.

__________________
Always read stuff that will make you look good if you die in the middle of it.

Thanatoast

Well, it sorta mostly works now :)

I have one of the wireless router's lan ports plugged into one of the wired router's lan ports. Once I got it configured, I had to turn of the wireless router's DHCP server. Problem is that I can't "get" to the wireless router anymore. It has it's own ip address assigned by the wired router, but the web interface does not respond (and I did configure it). Anyway, the shares now work, syncing still works, and I can still get to the net. So I am happy enough for now (until I need to reconfigure the wireless.)

Thanks a lot for the help!