VCP = Vanity Credit Points
1 posted on
04/02/2003 5:47:31 PM PST by
BibChr
To: chance33_98; Libertarianize the GOP
p1ng
2 posted on
04/02/2003 6:03:55 PM PST by
BibChr
(Liberalism means never even having to admit to yourself that you SHOULD be sorry)
To: BibChr
Similar problem here. My fix was simpler than I thought. Reset (power cycle) your cable-modem. When you injected the router, it has to re-apply for an IP address. The cable modem may not have been expecting this, and it keeps waiting for the old negotiated IP to come it's way.
So, do the instructions as per the wizard, reboot your machines, then power cycle the cable modem (DSL Modem, ect.) Worked for me.
3 posted on
04/02/2003 6:05:07 PM PST by
Hodar
(With Rights, comes Responsibilities. Don't assume one, without assuming the other.)
To: BibChr; Hodar
I would concur, at least as a trouble shooting step. Make sure the boxes are set up for dhcp, reboot the router, and then get into the router and look at the settings.
My network is setup with cable modem->nat router (4 port)->24 port smart switch for vlans->windows, linux, unix, xp all attached (though XP has just went away in favor of 2000 server). I also have several laptops I can just plug in and go.
Certainly do an ipconfig /all and check to see what address your systems have (if they are 169, I think, that means they are getting the addresses from MS and not the router).
Drop me a line and let me know status!
4 posted on
04/02/2003 7:37:26 PM PST by
chance33_98
(www.hannahmore.com -- Shepherd Of Salisbury Plain is online, more to come! (my website))
To: BibChr
6 posted on
04/03/2003 6:43:25 AM PST by
Consort
To: Bush2000
Ping
9 posted on
04/03/2003 10:45:55 AM PST by
BibChr
(Liberalism means never even having to admit to yourself that you SHOULD be sorry)
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson