<html><body>
Actually "command" _AND_ "cmd" _BOTH_ work in Windows XP :) But I know that that is off-topic for this mailing list.<br /><blockquote>Sat Apr 8 19:41:25 2006 from kobear to nflug@nflug.org <br />Subject: Re: [nflug] Router Questions<br /><br />If 'cmd' does not work, then use 'command'. I don't recall if winipcfg<br />specifically says that you are DHCP configured or not. Never bothered using it<br />since I could do it command-line. ;)<br /><br />Kyle<br /><br />Quoting Joe :<br /><br /><blockquote>> I'll take another look, but I know cmd is an XP thing - not supported in<br />> 98. winipcfg (or whatever it's called - I'm on Linux now) is the<br />> equivalent.<br />><br />> Joe<br />><br />> kobear@sharedbrain.net wrote:<br />> > Joe,<br />>><br />> > You can see if you are using DHCP by going to a command prompt (Start --><br />> Run<br />> > --> cmd) and typing "ipconfig /all". Somewhere in there there should be a<br />> line<br />> > that says Dhcp Enabled : Yes|No<br />>><br />> > HTH,<br />> > Kyle<br />>><br />>><br />> > Quoting Joe :<br />>><br />>><br />> >> I have it configured as Dave suggested (see my original post).<br />> >> The DSL modem lives at 192.168.1.1 (I'm not sure what else it uses, but<br />> >> they're in the 192.168.1.x range.)<br />> >> The VoIP uses 192.168,251,x addresses.<br />> >> I got these from the tech help configuring them and from Zone Alarm<br />> >> firewall logs. I have added both of these local subnets to my trusted<br />> >> zones in Zone Alarm. The DSL modem works a bit better now - less<br />> >> arguing after I kill it by inserting the VoIP - but the VoIP still<br />> >> doesn't work or pass through the Internet.<br />> >><br />> >> Verizon sent me a new modem and Sunrocket finally called back from level<br />> >> 3. Now I just have to get back to the location so I can call them back<br />> >> and work on it again.<br />> >><br />> >> So the consensus seems to be that I don't need a router at this point.<br />> >> That I should just hook them up in a row and get them to work.<br />> >><br />> >> I have no idea what Win 98se does regarding DHCP (I was at the last<br />> >> meeting, but I'm still not even sure what DHCP is. Forget configuring<br />> >> it!) I don't really want to get into the depths of networking any more<br />> >> than I have to at this point. I'm sure I'll have to learn quite a bit<br />> >> more if I ever get wireless equipment in the future, but for now, I can<br />> >> wait.<br />> >><br />> >> Any idea how I can tell about DHCP on my laptop? I've been running<br />> >> winipgcfg (release and restore) and sometimes that seems to help, but I<br />> >> don't know if that has anything to do with DHCP.<br />> >><br />> >> Joe<br />> >><br />> >> kobear@sharedbrain.net wrote:<br />> >><br />> >>> Quoting "David J. Andruczyk" :<br />> >>><br />> >>><br />> >>><br />> >>>> --- Joe wrote:<br />> >>>><br />> >>>><br />> >>>><br />> >>>>> I understand what a router is, but I've never worked with one, so<br />> >>>>> I've<br />> >>>>> got some basic questions. I don't expect anyone on this list to<br />> >>>>> debug<br />> >>>>> my VoIP (SunRocket) problem. The questions below are mostly OS and<br />> >>>>> vendor independent.<br />> >>>>><br />> >>>>> I'm having trouble getting VoIP to work for my partner (I'll be<br />> >>>>> talking<br />> >>>>> to VoIP level 3 support later.) She has Verizon DSL. I don't<br />> >>>>> remember<br />> >>>>> the exact speeds, but it's about 800/168 (the slowest/cheapest). The<br />> >>>>><br />> >>>>> VoIP says it needs 90/90 to work.<br />> >>>>><br />> >>>>> Currently, the DSL line comes into the Modem, out to the VoIP box,<br />> >>>>> and<br />> >>>>> then from the VoIP box into the notebook (Win 98se). Nothing has<br />> >>>>> wireless capabilities.<br />> >>>>><br />> >>>>> When I hook up the DSL without the VoIP box, it works fine. When I<br />> >>>>> put<br />> >>>>> the VoIP in the middle, not only does it not work, but the DSL goes<br />> >>>>> away and when I remove the VoIP box, I have to argue with the DSL box<br />> >>>>><br />> >>>>> for awhile to get it to work again.<br />> >>>>><br />> >>>>><br />> >>>> Solution. Install in sequence below:<br />> >>>> DSL line -> DSL modem-> VoIP box - >Laptop<br />> >>>><br />> >>>> power off all device (INCLUDING the dsl modem)<br />> >>>> power up DSL modem, wait till all lights on it say it's ready and<br />> >>>> working, power up Voip box make sure it becomes "ready", then power<br />> >>>> up laptop, and all should be working correctly now. Make sure the<br />> >>>> laptop is configured for DHCP. (almost all are).<br />> >>>><br />> >>>> Reason: DSL and cable modems detect the MAC address of the device<br />> >>>> directly plugged into them (whether it be a router, computer, appliance<br />> >>>> device, etc), and refuse to accept traffic from any other MAC address<br />> >>>> unless powercycled. MAC addresses do NOT cross router boundaries<br />> >>>> (read up on the OSI model if you really want to know why). The Voip box<br />> >>>> is essentially a simple router device with added gee-whiz stuff inside<br />> >>>> (the voip crap).<br />> >>>><br />> >>>><br />> >>>><br />> >>> Actually, I think he said that he never had the DSL router not be the<br />> first<br />> >>> device facing the DSL network. If that is the case, then the MAC address<br />> >>><br />> >> would<br />> >><br />> >>> not change.<br />> >>><br />> >>> I think that what is going on here is that you have a IP address<br />> >>> conflict/overlap the two networks.<br />> >>><br />> >>> Let's take a standard out-of-the-box config. Most routers plant the<br />> >>><br />> >> internal<br />> >><br />> >>> addresses on the 192.168.1.x network. If both the DSL router and the<br />> VOIP<br />> >>> router are doing this, then you have the following kind of problem:<br />> >>><br />> >>> DSL Line (Public IP's) --> DSL Modem (192.168.1.0/32 or 192.168.1.1) --><br />> >>><br />> >> VOIP<br />> >><br />> >>> Router (192.168.1.0/32 or 192.168.1.1) --> Internal network<br />> >>><br />> >> (192.168.1.0/24).<br />> >><br />> >>> Notice that both routers think that their address is 192.168.1.1. When<br />> the<br />> >>><br />> >> VOIP<br />> >><br />> >>> router gets traffic that it does not know what to do with, it is supposed<br />> >>><br />> >> to<br />> >><br />> >>> hand it off to it's default gateway, which is the DSL modem. But since<br />> it<br />> >>><br />> >> has<br />> >><br />> >>> the same IP address as the modem, it cannot find a route to it, and<br />> >>><br />> >> therefore a<br />> >><br />> >>> routing loop is created.<br />> >>><br />> >>> Given this, most verizon routers can be setup in Bridged mode, thereby<br />> the<br />> >>><br />> >> VOIP<br />> >><br />> >>> router can be given the public IP address for its WAN port and the<br />> problem<br />> >>><br />> >> is<br />> >><br />> >>> likely solved.<br />> >>><br />> >>> HTH,<br />> >>><br />> >>> Kyle<br />> >>><br />> >>><br />> >>><br />> >>><br />> >>>> Dave J. Andruczyk<br />> >>>><br />> >>>> __________________________________________________<br />> >>>> Do You Yahoo!?<br />> >>>> Tired of spam? Yahoo! Mail has the best spam protection around<br />> >>>> a href=http://mail.yahoo.com TARGET=webcit01http://mail.yahoo.com/A<br />> >>>> _______________________________________________<br />> >>>> nflug mailing list<br />> >>>> nflug@nflug.org<br />> >>>> a href=http://www.nflug.org/mailman/listinfo/nflug TARGET=webcit01http://www.nflug.org/mailman/listinfo/nflug/A<br />> >>>><br />> >>>><br />> >>>><br />> >>><br />> >>><br />> >>> ----------------------------------------------------------------<br />> >>> This message was sent using IMP, the Internet Messaging Program.<br />> >>><br />> >>> _______________________________________________<br />> >>> nflug mailing list<br />> >>> nflug@nflug.org<br />> >>> a href=http://www.nflug.org/mailman/listinfo/nflug TARGET=webcit01http://www.nflug.org/mailman/listinfo/nflug/A<br />> >>><br />> >>><br />> >>><br />> >> _______________________________________________<br />> >> nflug mailing list<br />> >> nflug@nflug.org<br />> >> a href=http://www.nflug.org/mailman/listinfo/nflug TARGET=webcit01http://www.nflug.org/mailman/listinfo/nflug/A<br />> >><br />> >><br />>><br />>><br />>><br />>><br />> > ----------------------------------------------------------------<br />> > This message was sent using IMP, the Internet Messaging Program.<br />>><br />> > _______________________________________________<br />> > nflug mailing list<br />> > nflug@nflug.org<br />> > a href=http://www.nflug.org/mailman/listinfo/nflug TARGET=webcit01http://www.nflug.org/mailman/listinfo/nflug/A<br />>><br />>><br />> _______________________________________________<br />> nflug mailing list<br />> nflug@nflug.org<br />> a href=http://www.nflug.org/mailman/listinfo/nflug TARGET=webcit01http://www.nflug.org/mailman/listinfo/nflug/A<br />><br /></blockquote><br /><br /><br /><br />----------------------------------------------------------------<br />This message was sent using IMP, the Internet Messaging Program.<br /><br />_______________________________________________<br />nflug mailing list<br />nflug@nflug.org<br />a href=http://www.nflug.org/mailman/listinfo/nflug TARGET=webcit01http://www.nflug.org/mailman/listinfo/nflug/A<br /><br /><br /><br /></blockquote><br /><br />--<br />Robert_Wolfe%2C_Linux%2FWindows_Admin%0D%0ANet261%2Ecom_%2F_OpenSource_Solutions%0D%0Arobert%40net261%2Ecom_-_http%3A%2F%2Fwww%2Enet261%2Ecom%3A2000
</body></html>