Excellent idea! Thanks Kim!

ISP's are doing some weird things now!

Shutdown or Disconnect desktop cable.

Shutdown Laptop, power off Modem/Router for 30 sec to 1 minute

Power on Modem give 10-20 sec to init then power up the laptop.

Mike

Ok this is really getting old... I ran the laptop over to a friends house, who has the exact same setup as me...(both have the same ISP) and started it up, and at first it didn't work, but then I remembered I had it still set on static ip, and so I switched back to DCHP, and it worked like a charm. Like I said, they have the exact same setup as me. One desktop with ethernet running to modem/router (and I then hooked up my laptop)...so the ISP hasn't placed limits. Besides, I just did what I am trying to do now last weekend, and it worked flawlessly. @ last idea...tried it, only thing it changed was the network name from "unidentified network" to "Network". other than that I'm still at local connectivity only.

Then it must be a Router issue
You could run the Hardware reset on it, usually a small button for a pin somewhere on it.
But you would then need to re-set it up again.

OK I think we are on to something here with Kims Idea!

I was headed to something similar as what Kim posted but had not thought of the MAC address issue.

Kim below is my template for what I call the TCP/NETBIOS/Winsock enema!

Going a little deeper! And gets a little log info.

Code:

netsh interface ip delete arpcache

ipconfig /flushdns

ipconfig /release *

ipconfig /renew *

ipconfig /registerdns

nbtstat -RR

netsh winsock show catalog >"%USERPROFILE%"\Desktop\lsp.txt

netsh winsock reset catalog

netsh winsock show catalog >>"%USERPROFILE%"\Desktop\lsp.txt

netsh int ip reset >"%USERPROFILE%"\Desktop\tcpreset.txt

Reboot see new icons on desktop, paste contents of lsp and tcp.txt back to thread.

Mike

Well if we're crossing notes, do this with Ipconfig, instead of going to a command prompt:

Start --> Run--> cmd /c ipconfig /all >Desktop\ipconfig.txt < ok>

But you would have to do each individually!

Pasted to the cmd prompt they all run one after another.

But what ever it takes to get the job done.

Guys I am headed to bed soon. Will let you know when I am logging off. I am Zapped!

But will be here for another 15-20 mins.

Mike

Oh yes that's true :blush:

Mine was for that one off situation

Yours therefore isn't exactly as posted
Yours in actual fact a Batch file (obviously)
How it looked, was, doing each command individually

Therefore I add your batch file here
Doh! I had to Zip it up!

ok I'm posting them...

Here they are:

tcpreset.txt

Reseting Echo Request, OK!
Reseting Global, OK!
Reseting Interface, OK!
Reseting Unicast Address, OK!
Reseting Route, OK!
A reboot is required to complete this action.

attached is lsp.txt since it is very long...

OK I will hang a little longer.

What about the test with the other computer and router off after you ran these?

And if this don't work like Kim said find the reset button on the back of the router.

Mike

Well, nvm, this is obviously a problem with the router, as I did this last weekend and it worked fine plus it worked just fine on my friends. I will just run it down to the isp sometime and see if we can replace it. Thank you very much for all your time!

Ok I will check back in the morn signing off for the night!

Good luck

Good night,
Mike

see http://www.mynucleus.ca/files/dsl/DSLSelfInstallGuide.PDF

the device comes in TWO models; ADSL+4 and ADSL+2
The install guide plainly states to plug the modem into your computer or router.
As the +2 device has only one rj45, this device will not have the DHCP you need
and is the reason for the router.

Kimsland's comment: (via mac address) limitations is VERY COMMON.
It's known as hardware provisioning and the ISP accepts only the first device
attached to the modem.

Get a router, place it between the modem and all other systems.
You may need to set MAC Mascarading or call the ISP to provision the new router.