LITTLEBLACKDOG.COM

Posted: Wed May 14, 2003 5:39 am Post subject:

thank you for your help that is how I set it up and i still get the same thing. I'm thinking now it might be how I have the thing wired so before I start sending all the ip and address information lets make sure it is correct.

The linksys is fed from my existing hub on my network, the only way I could get it to work is to use a cross over cable plugged into one of the 4 ports on linksys (not the internet port)

Could this be the problem, I tried to get it to work with cross overs and straight throughs on the internet port but I never could get anything on the computers attached to it.

Posted: Wed May 14, 2003 6:41 am Post subject:

That's the problem.

If you don't connect the WAN port of the Linksys to your network, AND you use DHCP in the Linksys to supply IP info to your laptop, then the routing won't work because it's trying to pass information to a port that isn't connected.

Forget the wireless for a minute. Connect your Linksys to the network via the WAN port, and using a computer (that uses DHCP) wired into a Linksys LAN port , give the WAN side of the unit a fixed IP address that fits the existing network scheme. Also, look for a setting that allows you to 'Block WAN request' and make sure it's disabled. Check the lights on the front... you should have a lit WAN indicator. If not, swap your cable type. If that doesn't work, then you have one of several problems: Bad unit, bad cable, bad network jack, bad port on the remote hub. Before all else, you must get that WAN port lit.

Once that happens, THEN we can move on.

So let's assume it's now lit. If you've disabled the 'block wan request' you should be able to ping the WAN IP of the Linksys from another node on your existing wired network. If that doesn't work, it's still not right.

If it does, ping an address on the network from the node connected to the Linksys. It should work... if not the the unit isn't routing.

If it does, see if you can access the internet. If yes, then all is well with the wired portion of your Linksys. If not, then there's a DNS or gateway problem.

Once you get a wired-to-the-linksys node to access the internet, then you should be able to get a wireless unit to work without much more difficulty.

Ok, now that I've rambled on, where are we? Smile

Posted: Wed May 14, 2003 6:59 am Post subject:

should the connection to the wan port be a straight through or a cross over cabe?

Posted: Wed May 14, 2003 11:32 am Post subject:

That depends on the port on the other end of the cable. If it's plugged into an autosensing port (which can tell whether it's being used as an uplink port or not) it won't matter. I think that the following is true:

If the remote port is standard, use a straight cable. If it's an uplink port, use a cross-over cable. This is because the Linksys WAN port is basically the same as a computer, as far as the remote port is concerned.

Basically, if one doesn't work, try the other. If neither of them makes the WAN port, as I said, there are problems you'll have to track down. The WAN port should lightup if you have a good physical connection, regardless of IP address info. If not, then you have:

a bad cable
a bad Linksys unit
a bad port on your remote hub
bad infrastructure wiring

It's possible that resetting to factory defaults and starting over might clear problems in the Linksys itself, or upgrading the firmware.

One way to check your cable(s) feeding the unit is to plug them into one of the LAN ports. If a LAN light comes on, that cable is good... it also means you should use the *opposite* style of cable for the WAN port, assuming the remote port doesn't automatically switch. If you plug that same cable into the WAN port and it doesn't lightup, then you know:

the cable is good
the remote port isn't autosensing or the linksys is bad

Posted: Thu May 15, 2003 6:42 am Post subject:

I've given up on the proxy right now and am just trying to get the dhcp to work so at least I can have the laptop obtain everything from the linksys. Here is the answers to your questions. (ip's changed protect the innocent)

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : dd-zd513itk5gzz
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : SpaceCo
Description . . . . . . . . . . . : Intersil PRISM Wireless LAN PCI Card

Physical Address. . . . . . . . . : 10-90-96-4B-0C-E5
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 216.18.125.29
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 216.18.125.30
DHCP Server . . . . . . . . . . . : 216.18.125.30
DNS Servers . . . . . . . . . . . : 216.18.158.1
216.18.158.2
Lease Obtained. . . . . . . . . . : Thursday, May 15, 2003 7:52:08 AM
Lease Expires . . . . . . . . . . : Friday, May 16, 2003 7:52:08 AM

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-02-3F-B4-CF-F1

C:\Documents and Settings\Administrator>ping 216.18.125.29

Pinging 216.18.125.29 with 32 bytes of data:

Reply from 216.18.125.29: bytes=32 time<1ms TTL=128
Reply from 216.18.125.29: bytes=32 time<1ms TTL=128
Reply from 216.18.125.29: bytes=32 time<1ms TTL=128
Reply from 216.18.125.29: bytes=32 time<1ms TTL=128

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

C:\Documents and Settings\Administrator>ping 216.18.125.30

Pinging 216.18.125.30 with 32 bytes of data:

Reply from 216.18.125.30: bytes=32 time=2ms TTL=255
Reply from 216.18.125.30: bytes=32 time=2ms TTL=255
Reply from 216.18.125.30: bytes=32 time=2ms TTL=255
Reply from 216.18.125.30: bytes=32 time=2ms TTL=255

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

C:\Documents and Settings\Administrator>ping 216.18.125.26

Pinging 216.18.125.26 with 32 bytes of data:

Reply from 216.18.125.26: bytes=32 time=4ms TTL=255
Reply from 216.18.125.26: bytes=32 time=2ms TTL=255
Reply from 216.18.125.26: bytes=32 time=2ms TTL=255
Reply from 216.18.125.26: bytes=32 time=2ms TTL=255

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

C:\Documents and Settings\Administrator>ping 216.18.158.1

Pinging 216.18.158.1 with 32 bytes of data:

Reply from 216.18.125.30: Destination net unreachable.
Reply from 216.18.125.30: Destination net unreachable.
Reply from 216.18.125.30: Destination net unreachable.
Reply from 216.18.125.30: Destination net unreachable.

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

C:\Documents and Settings\Administrator>ping 216.18.158.2

Pinging 216.18.158.2 with 32 bytes of data:

Reply from 216.18.125.30: Destination net unreachable.
Reply from 216.18.125.30: Destination net unreachable.
Reply from 216.18.125.30: Destination net unreachable.
Reply from 216.18.125.30: Destination net unreachable.

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

I have access to my lan but not access to net, if I hardcode in the numbers here is the ipconfig and everything works peachy

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : dd-zd513itk5gzz
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intersil PRISM Wireless LAN PCI Card

Physical Address. . . . . . . . . : 10-90-96-4B-0C-E5
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 216.18.125.29
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 216.18.125.30
DNS Servers . . . . . . . . . . . : 216.18.158.1
216.18.158.2

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-02-3F-B4-CF-F1

Posted: Thu May 15, 2003 6:12 pm Post subject:

Ok, I have to admit that this is one of the strangest things I've seen.

Can you do a tracert on your DNS server, both DHCP and static? What's the results there?

Posted: Fri May 16, 2003 1:42 pm Post subject:

tracert on dhcp just hits the gateway ip and then times out.
tracert on static hits gateway then an external ip and then times out.

I would like to make sure that I have the linksys setup correctly, I have the configuration type set to static ip, and then all of my static addresses entered here, the ip address is the ip address I have set aside for the router

Lan Ip Address (is this supposed to be the same as the IP address about or my static gateway ip address) I have tried it both ways.

wireless doesn't matter too much i don't believe

on the security tab
DMZ disable, block wan disable
on system tab
multicast enable
mac cloning disable
remote management disable
mtu auto
log disable

and on dhcp
server enable
starting ip address is my valid ip address
number of users 1
then my correct dns addresses.

Posted: Fri May 16, 2003 7:50 pm Post subject:

Ok, bear with me. Let's start from the beginning.... and let's talk real numbers. Each section is numbered so we can refer back to it. I hope it doesn't seem like I'm talking down here, just want to make sure we're covering all the details Smile

First off, reset the Linksys to factory defaults. Usually that's done by pressing and holding the reset button for about 10 seconds. Do not connect the unit to your network using the WAN port yet.

1) What is a valid IP address on your network that we can use, just as if we were adding a new computer to the network... we need IP address, subnet mask, default gateway, and DNS servers.

1.1) Out of curiosity, who controls these numbers? Why do we have to have a static IP address for the WAN of the linksys? Is there no DHCP on the network already?

1.2) get a computer and ensure that there is no IP address information of any kind in it.

1.3) connect a computer via a cable to a Linksys LAN port. make sure the computer is set for DHCP. If you get an IP address, DHCP is basically working. (as a note, there should be NO DNS servers listed in the IP configuration info on the computer at this point) Open the administration webpage of the Linksys (should be 192.168.1.1 at this point, if factory reset worked)

2) Once you have the valid IP information (what is it?), put those values into the WAN portion of the Linksys setup as a static IP. Again, make sure that 'block WAN request' is disabled so you can ping the router.

2.1) connect the Linksys to the network via cable to the WAN port.

3) Now then, go to another computer on the network and see if you can ping the IP address you just entered. If you can, proceed to the next section. If not, don't go any further.

5) Setup the Linksys DHCP: make sure it's enabled, give it a start range of say 100, and number of users at 50 (I think these are defaults) Enter the SAME DNS servers as you did in section 2 above.

6) reset the IP address of your computer connected to the Linksys by releasing and renewing it. (For win2k, that's "ipconfig /release" and then "ipconfig /renew" at a command prompt)

7) verify that your new IP address now has DNS info. The IP address should be 192.168.1.100, your gateway should be 192.168.1.1, your DNS should be as set above, and your subnet mask should be 255.255.255.0 If any of this info is incorrect, stop... there's something wrong.

Cool

At the computer, ping 192.168.1.1 which should be a positive response.

9) ping the WAN IP address, which should be positive

10) ping the WAN degault gateway, which should be positive

11) ping a DNS server, which should be positive.

12) ping an outside URL, such as yahoo.com

If all works up until section 11, then the Linksys is working fine. If number 11 fails, then there is something about the network not directly related to the Linksys that's causing the problem.

if nothing fails, you should be able to surf the net.

Ok. lets stop there for now. Smile

How/where are we?

Posted: Mon May 19, 2003 6:08 am Post subject:

Thank you I really appreciate the help and we are now closer than ever.

Following your instructions I now get onto the net using a proxy. Yahoo
weird thing is I still can't ping a website or my dns but who cares I can surf.

Now I think we are in the home stretch. The last remaining problem is I am on the net, can surf, retrieve emails but I don't have access to any of my computers here on my network which i need to have drives mounted and use the printers that are on the network on a print server.

Thank you again for all your help.

Posted: Mon May 19, 2003 7:34 am Post subject:

Glad we're making progress! Very Happy

There is the possibility that there's filtering on your network that's preventing the ICMP messages (ping) from getting back to you. If you can surf, that's not really a problem.

1) Ok, in order to finish this up, we need real numbers. What is the WAN IP address on the router?

2) Is there a DHCP server elsewhere on the network?

3) If you change the WAN IP address from static to 'obtain automatically', then power cycle the router, can you still surf?

4) If yes on #3, can you now access your local network?

Posted: Mon May 19, 2003 9:28 am Post subject:

There is no DHCP on the rest of the network, the entire network runs off of static ip addresses.

I tried changing the WAN IP address to obtain but then I get nothing because there is nothing on my system to obtain it from

I'm sorry about giving you the ip on the router, I dont' like that information out, is there a reason you need it?

Posted: Mon May 19, 2003 1:02 pm Post subject:

Well, with that I'm guessing it's a public IP address, rather than a private one behind a NAT router or somesuch, yes?
Which means it's going to be more difficult to get local network access working with this thing.

Really, what you need is the Linksys WAP11 wireless network bridge. It doesn't do any routing, just bridges your wireless and wired networks. But since not...

Let's say you have computerA on your local network that you wish to access. Can you ping that? If yes, then the biggest problem we have to deal with is probably name resolution, i.e., you can connect to it, just not see it.

Fair warning note here: I'm about to go out of town for about 3 weeks and won't be on as much until I'm back home. But if you can ping the remote computer that you want to connect to, try setting up a HOSTS file on your laptop with the IP information of the other PC, or setting up WINS, or ???

Name resolution can sometimes be tricky stuff.

Posted: Mon May 19, 2003 2:02 pm Post subject:

Thanks, I'm going to start a new thread to try to learn about VPN's as I would like to access all my work network from home as well. I'll also do some searches on name resolutions. I can ping the addresses but can't see them as computers or mount their drives

Posted: Fri May 30, 2003 7:27 am Post subject:

Okay I got everything set up and I thought I would let you know how just in case someone else if having the same problem.

It still all behaves very weird (stupid windows, think I might have to start learning linux) It turns out that I still can't go into my network places and see any of the computers or devices on my network, however, I can ping them by number and name. So what I did is did is manually set up the computers I needed to get to on my computer by basically creating a shortcut to them by ip address. After I have created a shortcut I can access the computers and mount the drives and printers.

Very weird that they still don't show up in the network places, but hey it works so what the hell do I care.

Thanks for all the help along the way.