Recommended Posts

Hey guys,

I need some assistance. I have 4 POS (Point of Sale) systems set up at a restaurant along with 2 desktops and 2 laptops. I have a Comcast wired business modem/router connecting all the POS systems plus the 2 desktops. For the two laptops, we have a Linksys Wireless-N router hooked up to the Comcast Modem.

Here's the issue. We want all the desktops + POS systems + laptops on the same network. Right now, the Comcast modem has a static gateway at address 10.1.10.1 and that's where everything is hardwired. However, the Linksys Wireless-N router has DCHP enabled and is giving out its own IP addresses which means the laptops are not on the same network as the 4 POS systems + 2 desktops even though it is connected to the Comcast modem (so we technically have 2 networks in 1).

Here's my question: We want all the computers + POS systems + laptops on same network so how can that be done? Should I make the Comcast wired modem/router a bridge and set up the static address and gateway on the Linksys router? Will that work?

Thanks for the help :)

the easiest thing to do would be to just use your wireless router as an ACCESSPOINT.. Since you really had no use of another router, what you wanted was an accesspoint.. Any wireless router can be used as just an accesspoint.

here

http://www.dslwebserver.com/main/wireless-...cess-point.html

Thanks, Budman. That seems to be exactly what I am looking for. All I have to do is just add the Linksys to the network by assigning it an IP address that the Comcast network is on, correct?

Just to be sure, this will allow the laptops to see the other 6 desktop computers on the network and vice versa, correct? The main reason we are trying to set this up is so we can access files from our main desktop using any laptop.

Once again, thanks Budman (Y)

In a nutshell you turn OFF the dhcp server on the wireless router.. You change its IP to something on your current network (just so you can access its web ui if you desire, etc) That does not conflict with any current IP, an outside your dhcp scope, etc.

You then plug in using one of its LAN Ports to open port on your first routers switch port or some other switch connected to your routers switch.

Yes once you do this -- all machines will be on the same network. Wireless clients will get their IPs from your gateway router dhcp server, an use it as their gateway, etc. The only thing you might want to make sure is you have AP or Client isolation turned off (lots of wireless routers have this feature). It prevents wireless clients from seeing/talking to each other.

In simple terms your turning your wireless router into a wireless switch ;)

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

    • No registered users viewing this page.
  • Posts

    • I wonder why you say that. As we speak, I'm using it to slash off several minutes of my life.
    • I think you may need to adjust your style of approach. I know you won't though. While some were affected by performance issues, and it's not a huge gap... you're acting as if Ryzen couldn't handle 11 at all. Performance issues are purely based on some facts in certain scenarios, while others are not. I see one link with a handful of people discussing the topic. I didn't join those topics or seek them out myself, as I didn't encounter noticeable drops in performance going from 10 to 11. When 10 came out, during that beta testing phase... I was able to continually crash my system simply by renaming files. It might also have to be because I don't have my nose stuck up the butt of single digit percentage points. I don't benchmark my PC every time something new comes out. Single percentage point differences in performance only ruffle the feathers of those that don't care about daily use. If you have a race car, do you compare that to your daily driver? Do you expect your Honda Accord to break the 9 second quarter mile like your 1000HP Pontiac Firebird? If you're so worried about FPS instead of enjoying your games... perhaps opening a curtain in your basement might provide a new perspective in life.
    • Currently updating my Win10 IoT Enterprise LTSC 2021 in a VM (QEMU/KVM) on Linux. but damn, updates take forever (makes me appreciate the lightness on Linux all the more). to give you a general idea... this update finished at 37 minutes into system uptime and I would estimate updates have been running roughly 20-30 minutes (some of this would be download time, but even subtracting that I would guess that 20-30min is close). granted, I only got two cores of my four core CPU (i5-3550) dedicated to the VM. but still, Linux wipes the floor with Windows in this regard. plus, that does not count the reboot which takes even more time.
    • It's disgusting that this exists and is being marketed by Neowin as a way to earn passive income. Support real writers and real arts. The world needs them more than ever. After at least 10 years, Neowin can GTFO my favorites bar.
  • Recent Achievements

    • Reacting Well
      rshit earned a badge
      Reacting Well
    • Reacting Well
      Alan- earned a badge
      Reacting Well
    • Week One Done
      IAMFLUXX earned a badge
      Week One Done
    • One Month Later
      Æhund earned a badge
      One Month Later
    • One Month Later
      CoolRaoul earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      536
    2. 2
      ATLien_0
      270
    3. 3
      +FloatingFatMan
      212
    4. 4
      +Edouard
      204
    5. 5
      snowy owl
      140
  • Tell a friend

    Love Neowin? Tell a friend!