Failure to Assign IP address
This is a discussion about Failure to Assign IP address in the Windows Hardware category; I have a problem when dialing into my ISP. They have 2 numbers, one which works fine, although is engaged 99% of the time and teh otehr, well it just won't work. When it comes up loggin onto network, that's as far as it gets.
I have a problem when dialing into my ISP. They have 2 numbers, one which works fine, although is engaged 99% of the time and teh otehr, well it just won't work. When it comes up loggin onto network, that's as far as it gets. It drops out and says that server failed to assign IP address. MY ISP has told me "beta.... beta.... beta....", cannot support blah blah blah, but one guy there did say that he's seen this prob and it was a win 2k bug. Anyone know of this, more importantly, know how to fix it?
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Nov 1
Nov 17
0
3 minutes
Responses to this topic
I've been using assigned IP to conect to my company secure network, and to my ISP when the ADSL fails, whith no problems since W2K beta 2.
But hang about . . . one of your ISP's dial-in works, and the other doesn't. Might be worthwhile finding out what differences there are at their end between the two.
Also, try and pre-define as much info as possible - default gateway, DNS and such - to give your connect the best chance of getting an IP address.
But hang about . . . one of your ISP's dial-in works, and the other doesn't. Might be worthwhile finding out what differences there are at their end between the two.
Also, try and pre-define as much info as possible - default gateway, DNS and such - to give your connect the best chance of getting an IP address.
There's a hotfix for dhcp issues that cured my ip address problem.
if you can't find it on MS's site, let me know, and I'll see if I can find the link again.
if you can't find it on MS's site, let me know, and I'll see if I can find the link again.
OP
If you could find that patch for me I'd be forever greatful, I can't find it anywhere
Thanks
Thanks
I have a similar problem.
Whenever I dial into my ISP with my internal Courier v.everything it connects fine, verifies username and password, and then tries to "register computer on the network." That sounds like DHCP, and sure enough it fails and says my server didn't assign it an IP address.
How do I get it to stop using DHCP or whatever is confusing it? My connection works fine under WIn98, of course...
Whenever I dial into my ISP with my internal Courier v.everything it connects fine, verifies username and password, and then tries to "register computer on the network." That sounds like DHCP, and sure enough it fails and says my server didn't assign it an IP address.
How do I get it to stop using DHCP or whatever is confusing it? My connection works fine under WIn98, of course...
OP
Ok man this prob is pretty east to fix
goto the properties of your dial-up connection, then click on networking tab. Click on settings and make sure that enable software compression is the only one checked.
Negotiate Multilink......... is the actual culpurate
good luck
goto the properties of your dial-up connection, then click on networking tab. Click on settings and make sure that enable software compression is the only one checked.
Negotiate Multilink......... is the actual culpurate
good luck
Thanks very much.
I didn't have the multilink option (only LCP and software compression) but having software compression worked just fine.
I also switched off LMHOSTS for good measure.
Now if only I could get my HP4200C scanner to work...
Thanks again,
James
I didn't have the multilink option (only LCP and software compression) but having software compression worked just fine.
I also switched off LMHOSTS for good measure.
Now if only I could get my HP4200C scanner to work...
Thanks again,
James
OP
NP man.
Friggen dial-up KRAP. Can't wait till OZ get's decent cable
Friggen dial-up KRAP. Can't wait till OZ get's decent cable
