How do I see clients on new cable modem/router?

[energy4life]

...just had a cable modem/router install. installation contractor said physical connectivity on our network is a LAN issue; however, I have no]IP for the router, nor documentation on it's functionality. The behavior:
a. I can't see any PC clients either 1) through the hub with the router plugged into the hub or 2) with a PC plugged directly into the router.
b. Pings (the machine i'm sitting) take 20+ seconds; tracerts timeout after 30 hops. 30 hops? (WHAT is going on). Pings to other clients time out. (no IP addresses when I go and check).
c. IP addresses in the client's TCP/IP properties are now gone. I don't know default gateway nor IPs to enter (statically); nor has the router (that I can't telnet or hyperterminal to) assigned any.

Now the old router (for the ISDN LAN vendor) was the default gateway for the LAN (a small simple network - 15 nodes and shared printing); handled DHCP assignment; could be configured for dynamic or static IP assignment; AND - had full documentation.

I'm the closest to an MIS person in this little shop. Am i gravely missing something w/ re-configuring around the new cable modem/router? or should the cable modem vendor ensure we get WAN connectivity of their router in existing hub (or at least provide documentation)? Are low end routers now fully dynamic? (hard to believe)

thanks...

 

[Guest_imported]

I think I would start by looking for another contractor. This contractor obviously did not deliver a turn-key installation. The new router should be configured as a DHCP server, which should appropriately and dynamically configure the hosts on your network. I assume that you are doing away with the old ISDN connection (you can only have one DHCP server on the network).

 

[energy4life]

thanks grtrooper! i spent a few hrs on the phone troubleshooting with the vendor today (note: NOT the wiring guys sub-contracted to do the cabling). after getting internet connectivity from client->cable modem, then client-> router -> modem, the vendor's done (in that they've determined their equipment isn't causing the connectivity problem).

I'm now on my own to determine what is (the problem) when inserting the hub. (client -> hub -> router -> modem). I must admit, I wouldn't have gotten this far without the vendor. For example, each client's TCP/IP properties changed (DUH, LOL): DNS, dynamic IP assignment, using DHCP not WINS. Go figure why the sub-contractor/installation guy didn't provide valid DNS's. live and learn...

 

[zephan]

any matter about router's IP ?

 

[energy4life]

all: fyi, this is resolved. turned out to be hw - wiring to be specific - I needed a CROSSOVER CABLE; was using straight through cat5. Also, there's a toggle on the back of the router that must be in the correct position. THANKS ALL!