Recommended Posts

Dear Neowin member,

Sorry I have lots of questions lately. Please bear with me.

I have a Linksys WRT54G router and my computer connects to the wireless router using a WUSB54G adapter, while my sister connects it wiredly. Anyways, my sister's DHCP address is 192.168.1.100 while mine is 192.168.1.101 .. which means hers is the host or the start or whatever you call it. Right? I hope so. Anyways, how do I change it so I am the 100 and my sister is the 101? Help would be GREATLY appreciated.

Thank you for your attention!

dL

Link to comment
https://www.neowin.net/forum/topic/157248-dhcp-client-question/
Share on other sites

i believe what you are talking about is the dmz host setting which allows you to be openly connected to the internet (without any sort of hardware firewall), go to advanced settings and enter your local IP for the DMZ host. :D

and as was said before, the local IP addresses have nothing to do with hosting, etc. If your sister turns her computer off, and you reboot, you will likely become ... .100 and she will be .101 when she restarts.

I would recommend you not turn on the dmz host setting.. Renders your firewall useless.

Check the diagram below to see why you can use netmeeting when you're 100 and not when you're 101. To make it so that you're always .100, you can set yourself as a Static IP in the LAN config section of your router (at least, I can ;)).

Although, it doesnt matter if you're .100 or .101... There isnt any "start" or anything, all computers get data the same no matter if they're .100 or .199

post-32-1081835456.jpg

  HellBender said:
I would recommend you not turn on the dmz host setting.. Renders your firewall useless.

Check the diagram below to see why you can use netmeeting when you're 100 and not when you're 101. To make it so that you're always .100, you can set yourself as a Static IP in the LAN config section of your router (at least, I can ;)).

Although, it doesnt matter if you're .100 or .101... There isnt any "start" or anything, all computers get data the same no matter if they're .100 or .199

is this a joke?

  HellBender said:
Um.. no? Why would it be? :dontgetit:

just the diagram mostly........is not really how it works at all. the port the data comes in on in no way correlates with the local IP addresses. you could have a local IP address set as any given numbers and as long as either you enable DMZ hosting / open the necessary ports.....everything should work fine......

unless I'm really really lost?? :huh:

EDIT: okay, i've been looking at it more, and I kinda understand what you are saying. you are saying that someone set up the router to forward the data entering netmeetings ports to local IP [...].100 ???

Edited by rumbleph1sh
  rumbleph1sh said:
just the diagram mostly........is not really how it works at all. the port the data comes in on in no way correlates with the local IP addresses. you could have a local IP address set as any given numbers and as long as either you enable DMZ hosting / open the necessary ports.....everything should work fine......

unless I'm really really lost?? :huh:

EDIT: okay, i've been looking at it more, and I kinda understand what you are saying. you are saying that someone set up the router to forward the data entering netmeetings ports to local IP [...].100 ???

That's how data travels without DMZ Hosting involved. The thread starter obviously hasnt and doesn't want to set up DMZ hosting, so what he must have done is forwarded port 100 to IP address 192.168.1.100, and so he can use netmeeting fine. But once he pops to 192.168.1.101, the data for netmeeting is sent to 192.168.1.100, so he doesnt receive it, thus rendering netmeeting useless.

  HellBender said:
That's how data travels without DMZ Hosting involved. The thread starter obviously hasnt and doesn't want to set up DMZ hosting, so what he must have done is forwarded port 100 to IP address 192.168.1.100, and so he can use netmeeting fine. But once he pops to 192.168.1.101, the data for netmeeting is sent to 192.168.1.100, so he doesnt receive it, thus rendering netmeeting useless.

alright, thanks for clarifying. i'm sorry , i guess I was just reading the diagram wrong. :blush: everything seems in order now

  dL said:
HellBender is right. That's what I think, and his/her diagram is exactly what I think the problem is. I'm not sure if it's true though.

dL

If thats indeed the problem, then all you have to do is assign yourself a static IP (like me and Smeg earlier mentioned). This means that every time you connect to the DHCP server, it will assign you the same IP no matter what order you connect in. That way, you'll always be 192.168.1.100 and you'll always get the netmeeting traffic.

  HellBender said:
If thats indeed the problem, then all you have to do is assign yourself a static IP (like me and Smeg earlier mentioned). This means that every time you connect to the DHCP server, it will assign you the same IP no matter what order you connect in. That way, you'll always be 192.168.1.100 and you'll always get the netmeeting traffic.

Now How do I do that with my WRT54G Linksys router?

Can I do it in the Wireless Network Connection, underneath TCP/IP properties in My Network Place?

dL

  HellBender said:
If thats indeed the problem, then all you have to do is assign yourself a static IP (like me and Smeg earlier mentioned). This means that every time you connect to the DHCP server, it will assign you the same IP no matter what order you connect in. That way, you'll always be 192.168.1.100 and you'll always get the netmeeting traffic.

I don't understand this. Just because it was set up with port forwarding to work a specific way on his OLD router, why should it be set up on his new router already? You must manually open ports/ re-setup the port forwarding on your new router in order for it to work properly.

  dL said:
Now How do I do that with my WRT54G Linksys router?

Can I do it in the Wireless Network Connection, underneath TCP/IP properties in My Network Place?

dL

No, you'll have to go into your router admin... I think its http://192.168.1.1 for you.. Enter your user/pass in and find something that says Static IP. I dont have a linksys router, so I can't tell you exactly where it is.. hopefully someone will come along who can.

to set your lan connection to be a static IP:

Right-click on My Network Places.

- Left-click on Properties.

- Double-click on Local Area Connection.

- Click on the Properties button.

- Highlight TCP/IP, then double-click on it.

- Select "Use the following IP address." Then enter the IP address 192.168.1.100 with Network Mask of 255.255.255.0.

- Set the Default Gateway to 192.168.1.1 which is the default address for the linksys.

or in the router setup (192.168.1.1) click on advanced and there are options for setting up static routing

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.