IT Employment

General discussion

Gravatar
0 Votes
Locked

w2k cisco router config problem

By wpcc ·
I tried to swap an smc barricade router with a new cisco soho91 router last night.
I have 7 peer-to-peer machines...3 xppro, 3 w2k, 1 w98se.
I have a cable modem with internet access shared by all.
When the wap was complete (2 minutes) and the new router was registered with the isp, I released/renewed the ip's succesfully, but could only get to the internet with the xp and 98 machines.
I tried every conceivable config combo I could think of on the router and on the w2k machines.
I tried static ip's on both, combos of static/dynamic, changed subnets...etc.
I finally called Cisco and spent 3 hours on the phone without a successful resolution.
I could never ping beyond the router, but could ping the router.
The tech at Cisco was telnetted in and could ping in.
He finally gave up and told me to reload windows 2k on each machine.
These are production machines in my customers office...not an option.
I put the SMC ack in, reregistered and all machines worked fine.
Any ideas?
Thanks, Gordon

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

gravatar
Collapse -

Some solutions

by zaheerahmed2 In reply to w2k cisco router config p ...

Ok looks at though it could be some service that is disabled within win2k machines? The type of ports win 2k machine r trying to access?

gravatar
Collapse -

service?

by wpcc In reply to Some solutions

If a service was disabled, then why would it work on the MC router?
Also, I just took 1 machine to my shop and hooked it up to my network...same isp.
I use a Symantec VPN100 firewall/router.
It works fine on that router.
So far SMC and Symantec OK, Cisco Not.
Gordon

gravatar
Collapse -

Start w/ the basics

by road-dog In reply to w2k cisco router config p ...

If all of the PCs are using IP, then if the router is configured correctly, IP is an all or nothing deal.

You left out a lot of pertinent details,
1)Are you NATing?
2)Are you using a switch or hub?
3)What service on the Internet were you trying to use, and were you trying to access the same services on every machine?
4)Is there a mix of DHCP and static IP during testing? Is it possible that DHCP (on the router LAN port)may have tried to assign addresses that were statically assigned to other machines?

Before you go too nuts, debug IP by setting up the router with only the basics, and then connect (and debug) machines one at a time. Use ALL DHCP or ALL STATIC. Small network, I suggest static for simplicity, as you probably have an entire class C network available to you.

Good luck and open this in Q&A next time!

gravatar
Collapse -

basics

by wpcc In reply to Start w/ the basics

I am using the router as DHCP.
I am NATing.
Simply web connection on the Internet, all machines the same.
No mix of IP's, all dhcp...although I tried static IP's too and mixing.
Router is set to basic (default) setup no firewall.
I have tried connecting 1 machine (w2k) at a time and most of my testing with 1 xp, 1 w2k.
I have a 3com SS2 10 speed 24port.
I tried w/o the 3com, directly into the router.

gravatar
Collapse -

Easiest way.....

by LordInfidel In reply to basics

1) Disable the DHCP service on the router
(you only have a few machines)

2) Make a list of machine names

3) Make another list of your IP address'.
IE.
192.168.1.1
192.168.1.2
etc

4) Combine the 2 lists.
(I usually will make my network devices (rtr's, switches in the 1-9 range. My Servers 10-20 range, user IP's 100-199 range, user's with no inet access 200-254) ***No 2 machines can have the same IP!!!!

5) Then manually set your router's internal IP.
(That becomes your gateway IP) usually this is .1

6) Manually set every system IP according to your list.

7) Make it easy on your self and set the subnet mask of all machines, inlcuding the internal IP of the router to 255.255.255.0

Make sure each machine is pointing to the correct valid DNS server.

If you still can not surf the net after all of that, then something else is really wrong. And typically that would be on the router/nat side with some sort of #of Hosts restriction.

gravatar
Collapse -

easy way

by wpcc In reply to Easiest way.....

I tried that...sorry.

gravatar
Collapse -

Router

by timwalsh In reply to w2k cisco router config p ...

I'm assuming you are using the router as the DHCP server.

You have a number of conflicting symptoms here:

The fact that the WinXP and and Win98 machines have Internet access suggests that the problem lies with the WWin2K computers.

The fact that the Win2K machines work on the other routers would lead to one of two conclusions:
1. There is some sort of misconfiguration on the Win2K machines and the other routers are less "finicky" about the misconfiguration than the Cisco.
2. There is some sort of misconfiguration on the Cisco.

So let's check a couple of things (if you haven't already):

What happens if JUST the Win2K computers are connected?

Are there any differences in configuration of the Local Area Connection (as far as clients, services, or protocols) between the Win2K machines and the others? In particular, is the QoS Packet Scheduler installed? I have had instances where this service has caused problems.

When you perform the IP release/renew operation on the Win2K machines, do the new IP addresses belong to the same IP address range as the other computers?

Could the router be misconfigured to allow only a certain range of IPs outbound access?

Hope this gives you some things to think about.

gravatar
Collapse -

thinking about

by wpcc In reply to Router

Just w2k...same problem.
Just 1 w2k...same problem.
The only difference in lan config that I have not check...but will now... is QoS Packet Scheduler.
I know it is installed on the xp machines.
All machines are in the same subnet, no conflict, not outside the range...both in the default 10.10.10.1 (2) - 100 on the Cisco and in the range 192.168.10.1 (2) - 49 when I changed the Cisco default...I thought the 10's might be conflicting with the ISP.
I tried static and automatic assignment.
Both were in the range.
I will check QoS however...thanks.

gravatar
Collapse -

That brings up...

by ghstinshll In reply to thinking about

...an initeresting question, what IP range is the ISP actually using? It's possible they might be using the 10's like you said, or the 192 might show up somewhere also. Might want to think about using 172.16.1.0 as your network .1 for router, .2-.254 for DHCP.

gravatar
Collapse -

this brings up answer

by wpcc In reply to That brings up...

They only use 10's if you are not registered customer...otherwise 12's
I did try a different ip manually, both on the router and the machines.
Cisco suggests I get a sniffer and see where the packets are going.

Back to IT Employment Forum

Start or search

Related Discussions

Related Forums