ICS @home DHCP problem

[Mapidus]

Anyone using ICS with @home DHCP? ICS worked fine for me with static ip, but now it won't grab a dynamic IP with the @home DHCP system. Could it be because of the weird way @home does DHCP? @home uses the hostname to assign dynamic ips. Is this information sent or received over a port that ICS is blocking? As soon as I turn off ICS, I will get an ip, but it won't grab one with ICS on.

 

[sohcrates]

if it gets an IP with ics disabled..then why do you need ics? have you bought two IP address from @home?

let me know what you're trying to do

 

[Mapidus]

I need ICS because I need to share my connection with other computers in the house. If I turn ICS off I can get an IP, but then only the computer connected to the cable modem can use the internet.

 

[sohcrates]

can you give me some details about your network? How do you have both computers hooked up? Are you using a switch? a hub? 2 nics in the main machine and one in the secondary machine with a crossover cable?

 

[DainBrammage]

What operating systema re you using?

What is the ip and subnetmask listed for your systems?

 

[bomb99]

I happen to get a static IP from att@home and I have no problems with ics. Even though ics have a built in DHCP server, but you don't have to use it, just set your clients to whatever private IP you want. I'm currently using NAT with win2k, because I heard it's better, but I don't notice any difference.

 

[Mapidus]

Ok, I guess I need to give more info to clarify.

I used to get a static IP from @home and ICS worked fine under this, but now @home is switching to DHCP and my ICS setup will not obtain the dynamic ip from @home.

I am not having DHCP problems with the local lan (some machines on my local lan are setup to get dynamic ips, while a few are using hardcoded 192.168.0.x ips and this is working fine).

My ICS setup is two nics in the host and one nic in each of the client machines. These are connected to the host with an 8-port hub. The cable modem is connected to the host.

I think the problem could be with @home allocating ips based on a hostname they assign and this host name is entered in where the computer name for windows networking is entered. I know ICS blocks the windows networking ports and that may be the problem. I tried opening up 137-139, but it did not work. Does windows networking use other ports?

Sharing the internet works fine once I get an ip. If I disable ICS temporarily then I will get an IP and the sharing will work one ICS is enabled again. But is ICS is enabled and the computer is restarted it won't get an ip until I turn off ICS.

Right now I am using the disabling then reenabling of ICS to get the dynamic ips, but this is very annoying since it takes a while to do each time I turn my computer on.

This is all under win2k.

 

[cavingjan]

Not familiar enough with W2K's ICS to offer any fixes for that but how about obtaining the IP address from @home and just leaving the computer on? Or do they have a time limit on the address lease? I'm not sure if this is a viable option for you but it was the first one that came to my mind.

 

[PrinceofWands]

Record the ip's you're getting from @Home...unless they're doing something increadibly odd you'll notice you're getting the same IP over and over again. They've been telling people for years that they're DHCP but they're not really. They only change IP's when they split a node or when an error comes up. Of course, your area could just be doing something new and they might actually be going DHCP. If you see that you're getting the same IP just leave yourself static and you'll be fine. You may occasionally have to call up and get your new settings, but not very often.

 

[Mapidus]

Yeah, I was one of the first customers in the area, so I have had a static ip until recently. Now they sent an email and a snail mail letter out telling me to switch over to DHCP before the 22nd, so it must be a major change they are implementing. Right now I am still getting the same address as my static one under DHCP, but who knows what will happen come the 22nd. Using the static IP is what I am doing now, but it would be nice if I could get ICS to work with DHCP.

I would think that ICS would work with DHCP because it seems like this is likely the setup most ICS users are using. So I think it must be because of the weird way that @home does DHCP.

 

[PrinceofWands]

hahahahahha, sorry to inform you, but you've been duped. That's a form letter, everybody eventually gets one. Some people get two or three. They're not changing anything at all in the network, or in the way they do things. Oh, they're probably doing some node splits, but they always are. No, you can stay static just fine. Probably around the 22nd they'll reorganize the network and you may end up with a different ip, but then it'll be stable for a long time after that. They may also be upgrading the network to pure DOCSIS complience, but it will only affect people with older modems (ones that they've purchased more than likely since @Home is pretty good about upgrading their own modems). I received one of those about two months after getting service. Then again 6 months ago. Nothing changes, except maybe your ip once or twice. Ignore them, they'll eventually go away.

Ad for getting it to work DHCP, you can keep trying if you'd like. You are correct that @Home's system is closer to a WINS server than a DHCP. Who knows what chaos that will cause you though. I'd personally just stay static and if it stops working, call in and demand your new settings. They'll argue with you, but they can't refuse to give you your current settings so eventually you'll win.

 

[bomb99]

I have att@home for more than 2 years now, and I've always left it as a static IP. The only thing that you need is the computer name they assign you to get the service.

 

[Mapidus]

Thanks for all the advice. I will likely leave my system with static ip instead of trying to get ICS to work with their system. This is my first letter though, after over 3 years of service (got cable modem the week it was available. I guess they are good with modem upgrades in your area, but I had the original non-docsis Com21 modem that they gave 3 years ago until last week when I replaced it with an RCA docsis I got off of ebay. I could not believe how much faster the new modem is. I used to get 150KBps max down, but now I see 400KBps+ from fast sites. I did get a new IP with the new modem, but I am getting the same one from DHCP so far, so I'll stick with static and sees what happens in a few days.

I don't know about @home support in your area, but around here they are very stupid. I had to schedule a service call to get my new modem online even though all they need is the MAC address. And after the guy came over and called in the numbers, it did not work, so I had to call in and they wanted to schedule another service call. After a lot of arguing, they finally let me give them the MAC over the phone. I guess the service call person read them the wrong number when he came or something.

 

[TheMabbi]

If the IP ever changes you can always just set it back to DHCP and see what the new IP is. Would probably be quicker than calling up tech support

Of corse, that's assuming that the DHCP server hasn't lost track of your computer name in the meantime...

 

[PrinceofWands]

Actually the DHCP servers usually won't respond after 8 days of no contact with your system. Sometimes they will, but not very often. That's why I always just say, 'call tech support'. Actually tech support in my area are the same people as in your area. Tech support is nationalized. Yeah I know they're a pain, but in honesty it's not them, it's management that forces them to be that way. When I was working for them I could have fixed so much more than I did, if they just would have let me. Oh well.