From: HeyBub on 15 Jun 2010 19:37 J Tinsby wrote: > Doesn't XP flush the IP address when it's shut off so it's ready for a > new one when you restart it? The reason I ask is: > > I have a Linksys WRTP54G wireless router that has 2 phone ports for > use with the Vonage phone company. > > When we have electrical strorms I unplug everything including my cable > connection to my modem, the router and of course the 'puter. After the > storm it can take me up to 45 minutes to get an internet connection > again. > > The setup is a Surfboard cable modem that feeds the Linksys then to > one of my motherboard's 2 ethernet connectors. When powering up after > a storm I power them in that order. But I continually get the message > ballon that says " A network cable has been unplugged." The ethernet > connection light on the router is either blinking or isn't on at all. > When I have a proper connection it's on solidly all the time until I > shut off the computer then it goes dark. In spite of all this I do get > a useable phone connection as the phone light on the Linksys comes on. > > If I elminate the router, of course losing my Vonage, and plug the > computer in directly to the modem and power up, I get a connection > immediately. > > The only way I could get THIS connection after 5 reboots of everything > was to change to the other ethernet port on my MB. > > I don't think it should take all this fooling around to get an IP > address so I can get a connection. > > I have tried the command 'IPCONFIG/RELEASE." > > Once I have a good connection to the 'net with the above setup, I can > shut the machine off entirely, or let it sleep or hibernate and once > it starts to boot I get a solid ethernet light on the router. > Unplugging everything sends it into a frenzy! > > I am using XP pro SP3 with all updates, the ISP is Comcast. What is > wrong or what am I doing wrong? > > Vonage, although they try to help haven't been able to fix the > trouble, it may be beyond their purvie, but they do try. > > I hope this topic is appropriate for this forum, if note please move > it to where it should have been posted. > At a command prompt, type: ipconfig /release followed by: ipconfig /renew See if that helps. Look under your couch cushions for spare change. Finding same, buy a surge protector.
From: Jordan on 16 Jun 2010 22:25 I had that router and it sucked with Gigabit ports. Even when I forced the NIC to 100 MB it still had issues. "J Tinsby" <none(a)present.com> wrote in message news:q25c16l8o1dui8i9oei47lsoftbv4u3j4c(a)4ax.com... > On Sun, 13 Jun 2010 23:53:23 -0700, Mike S <mscir(a)yahoo.com> wrote: > >> >>I have an XP Pro box that I run into a router, which itself is connected >>to another router. I hibernate my machine instead of turning it off, and >>when I boot up it often has problems connecting, so I made a small batch >>file that I run when I restart it after a hibernate. Maybe running this >>batch file will help you. This is just a patch, I'm not sure what the >>source of your connection problem is, but if this works it's an easy fix. >> >>Just save this as a filename.bat file on your desktop and double-click >>it to run it after when you have turned everything on but still have a >>blinking ethernet light on the router. Remove the first line to change >>to a default color scheme. >> >>color 4f >>cd \ >>cls >>rem ================================ >>rem Releasing IP Configuration >>rem ================================ >>rem >>ipconfig /release >>cls >>rem ================================ >>rem Renewing IP Configuration >>rem ================================ >>ipconfig /renew >>cls >>echo ================================ >>echo Done!! >>echo ================================ >> >>Mike > > > Mike, > > Thanks for the batch file I will try it! The odd thing is I never used > to have this trouble. > > Regards, > > J T >
First
|
Prev
|
Pages: 1 2 Prev: transferring files from "un-bootable" laptop Next: Windows XP 32bit and 64bit |