Microsoft Legacy OS
--
Questions
--
Followers
Top Experts
One PC, Two NICS, Two Lans
So I have a computer (W7 x32) that is connected to a local lan for our phone system.
Problem is, I cannot remote into it, because of how the network is set up for that vlan. This is a pain going locally to the machine every time to go to the manager tool.
There is no other NICs available, so I was thinking about plugging in a wireless card, so I can remote into the PC from my laptop on our local wireless network.
However, that NIC on the machine HAS to stay connected to that lan at all times so our phone system does not go down. So I can't just unplug the LAN when I need to use the WLAN. I need them to run together harmoniously.
Can I somehow make it so I can use the LAN and WLAN run at the same time? After Googling for it, I've come across a bunch of keywords such as Multi homing, and other items. But I'm not familiar with any of this persay, but I'm a quick learner.
Let's imagine the NIC is on 192.168.0.1
Let's imagine the WLAN needs to be on 10.0.0.1
How do I get this to work? =]
Problem is, I cannot remote into it, because of how the network is set up for that vlan. This is a pain going locally to the machine every time to go to the manager tool.
There is no other NICs available, so I was thinking about plugging in a wireless card, so I can remote into the PC from my laptop on our local wireless network.
However, that NIC on the machine HAS to stay connected to that lan at all times so our phone system does not go down. So I can't just unplug the LAN when I need to use the WLAN. I need them to run together harmoniously.
Can I somehow make it so I can use the LAN and WLAN run at the same time? After Googling for it, I've come across a bunch of keywords such as Multi homing, and other items. But I'm not familiar with any of this persay, but I'm a quick learner.
Let's imagine the NIC is on 192.168.0.1
Let's imagine the WLAN needs to be on 10.0.0.1
How do I get this to work? =]
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Yes, you can multi-home this PC. No, it isn't difficult. Yes, you can do it via WiFi. The whole process should be no more difficult than setting up the second NIC.
Just set both NIC and Wifi as you would set it up with a single NIC.
If you intend the wifi to be a fixed IP, then just go ahead and let it connect to the access point or router. If it's a dynamic IP, make sure the AP or router has been setup in the correct subnet.
Windows will route the correct traffic through the correct interface, you don't need to setup anything else (assuming the internet facing device has the gateway filled it, and the internal one not).
If you intend the wifi to be a fixed IP, then just go ahead and let it connect to the access point or router. If it's a dynamic IP, make sure the AP or router has been setup in the correct subnet.
Windows will route the correct traffic through the correct interface, you don't need to setup anything else (assuming the internet facing device has the gateway filled it, and the internal one not).
attach the wireless adapter to the computer or a network card whichever is preferable and basically assign it a manual ip range from your other lan with a default gateway.
if its too difficult then use something like VNC or even logmein or teamviewer which are not ideal as you will be going out and coming back in
if its too difficult then use something like VNC or even logmein or teamviewer which are not ideal as you will be going out and coming back in
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
@Spec01 I think I'm understanding it now. I think I'm confusing myself on the addresses though. Could you help me? I'll give you the actual addresses this time:
LAN1
INT. 11
10.170.12.183 /24
Gateway: 10.170.12.254
WLAN (This is the new one I just installed so I can connect)
INT. 18
192.168.90.177 /24
Gateway: 192.168.90.99
I'm assuming I leave the gateway blank for the WLAN in the IPv4 settings though.
Picture, just in case I got the interfaces wrong:
What would be the command for adding a static based off my IP settings?
Thanks!
LAN1
INT. 11
10.170.12.183 /24
Gateway: 10.170.12.254
WLAN (This is the new one I just installed so I can connect)
INT. 18
192.168.90.177 /24
Gateway: 192.168.90.99
I'm assuming I leave the gateway blank for the WLAN in the IPv4 settings though.
Picture, just in case I got the interfaces wrong:
What would be the command for adding a static based off my IP settings?
Thanks!
SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
So to add a static route for WLAN on interface 18 would look like below...
route -p add 192.168.90.0 MASK 255.255.255.0 192.168.90.99 IF 18
The static route above says any traffic going out 192.168.90.0 subnet use 192.168.90.99 on Interface 18.
Will.
route -p add 192.168.90.0 MASK 255.255.255.0 192.168.90.99 IF 18
The static route above says any traffic going out 192.168.90.0 subnet use 192.168.90.99 on Interface 18.
Will.
@ChiefIT
The problem with fixing remote desktop on the wireless network, is they block all traffic other the phone traffic. They're pretty picky about it, whereas I'm hoping with this method, for just one computer it would be a lot easier. Where do you see if RRAS is enabled? I certainly don't want that to happen. Is that on the computer itself or router or what? This particular computer is not part of a domain, though is does use our DNS server that's about it.
The problem with fixing remote desktop on the wireless network, is they block all traffic other the phone traffic. They're pretty picky about it, whereas I'm hoping with this method, for just one computer it would be a lot easier. Where do you see if RRAS is enabled? I certainly don't want that to happen. Is that on the computer itself or router or what? This particular computer is not part of a domain, though is does use our DNS server that's about it.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
I was only stating the obvious, that you cannot have multiple gateways on a machine unless you have RRAS installed. This is a role that is part of the server OS. I just wanted to mention that to get my point across, i did not intend for you to install it, it was simply a statment. creating a static IP for the interface will work without issue.
Will.
Will.
Great okay, I never installed RRAS, unless it comes on by default on w7 pro, which it doesn't sound like the case. Since this is not part of a domain, it shouldn't pick up anything from our servers even if they do have RRAS installed. I'll give that command a try.
SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
@Spec01
I tried the command and it stated it was OK, but I'm not able to ping anything on the 192.168.90.0 /24 network still. Is there something I'm missing?
This is how the IP settings are set up
I left the 192.168.90.99 gateway out as I understood as you can see.
@ChiefIT
Sadly the machine does not have a serial connection, that was one of the first things I looked for as well. And thanks for the tip, I double-checked that the service remained off.
I tried the command and it stated it was OK, but I'm not able to ping anything on the 192.168.90.0 /24 network still. Is there something I'm missing?
This is how the IP settings are set up
I left the 192.168.90.99 gateway out as I understood as you can see.
@ChiefIT
Sadly the machine does not have a serial connection, that was one of the first things I looked for as well. And thanks for the tip, I double-checked that the service remained off.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Are you sure that the gateway is correct? can you ping the gateway from the workstation? Also what does your routing table look like "route print"?
Will.
Will.
I'm able to ping the gateway and it replies back just fine from the workstation, but nothing else. On my laptop in my office I also am using 192.168.90.99 as a gateway on the wireless, I'm able to ping everything, but not 192.168.90.177 (the workstation).
Here's the routing table and ping examples:
Here's the routing table and ping examples:
couple things you can do.
Create a route directly to your workstation from the dual homed VLAN machine.
which would be the following...
route -p add 192.168.90.(your IP) mask 255.255.255.0 192.168.90.99 IF 18
Also on your workstation create a static route to the other workstation IP.
route -p add 192.168.90.177 mask 255.255.255.255 192.168.90.99 IF (whatever your IF # is)
Will.
Create a route directly to your workstation from the dual homed VLAN machine.
which would be the following...
route -p add 192.168.90.(your IP) mask 255.255.255.0 192.168.90.99 IF 18
Also on your workstation create a static route to the other workstation IP.
route -p add 192.168.90.177 mask 255.255.255.255 192.168.90.99 IF (whatever your IF # is)
Will.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Some have replaced the serial with an RJ45 interface.. What interfaces does the PBX have? And would you consider using the Web interface that ALL of the latest PBX's should have? Keeping one nic is SOOO much easier and better.
@Spec01
It's very odd, it still doesn't seem to be working for some reason still.
My laptop in my office has a IP of 192.168.90.32
Here is the routing table on my laptop that's connected to the same wireless vlan right now. It's able to ping everything besides 192.168.90.177 (the workstation)
The only thing 192.168.90.177 (the work station) can ping is our gateway 192.168.90.99
Workstation Table:
What am I missing?
@ChiefIT
It literally only has one RJ45 jack that is being hogged for the phone network right now. It needs to be on that network, because the workstation also is used for the voicemail etc.
If I can use the second NIC I can either remote into the PC, or use the webtools as well probably over remoting in. So I've also thought about it, but the dang box doesn't have enough ports for anything :(
It's very odd, it still doesn't seem to be working for some reason still.
My laptop in my office has a IP of 192.168.90.32
Here is the routing table on my laptop that's connected to the same wireless vlan right now. It's able to ping everything besides 192.168.90.177 (the workstation)
The only thing 192.168.90.177 (the work station) can ping is our gateway 192.168.90.99
Workstation Table:
What am I missing?
@ChiefIT
It literally only has one RJ45 jack that is being hogged for the phone network right now. It needs to be on that network, because the workstation also is used for the voicemail etc.
If I can use the second NIC I can either remote into the PC, or use the webtools as well probably over remoting in. So I've also thought about it, but the dang box doesn't have enough ports for anything :(
Everything seems right. Do you have any firewalls enabled on the duel homed workstation? Check to make sure that windows firewall is not blocking communication and also make sure that RDP is enabled so you can remote into the PC.
Will.
Will.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
I'l give the firewalls a check, just a quick question, we that command above with the 255.255.255.255 a typo, or do you really mean 255.255.255.0?
Also on your workstation create a static route to the other workstation IP.
route -p add 192.168.90.177 mask 255.255.255.255 192.168.90.99 IF (whatever your IF # is)
SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Hmm yeh turned off firewalls completely on both machines for testing purposes, still no ping from either machine. They can both ping and reach the gateway though.
The wireless on the workstation has a caution sign on it though (says something is wrong with it) it's because I'm leaving the gateway out. But that's intended. Don't know what else would be prohibiting the pings, unless the router is not recognizing the traffic somehow. But everything on the same network should be able to communicate anyways.
The wireless on the workstation has a caution sign on it though (says something is wrong with it) it's because I'm leaving the gateway out. But that's intended. Don't know what else would be prohibiting the pings, unless the router is not recognizing the traffic somehow. But everything on the same network should be able to communicate anyways.
SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
In your initial description you stated "vlan".
vlans don't cross talk that's what they're for, so same copper can broadcast on different subnets and not drag down bandwidth.
I would suggest adding an entry in the router to allow vlan(x) to talk to vlan(y) for ip ipaddress(z) only.
What type of router do you have installed?
vlans don't cross talk that's what they're for, so same copper can broadcast on different subnets and not drag down bandwidth.
I would suggest adding an entry in the router to allow vlan(x) to talk to vlan(y) for ip ipaddress(z) only.
What type of router do you have installed?
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Got it to work!
I deleted all routes and only put in one route from my laptop:
route -p add 192.168.90.177 mask 255.255.255.255 192.168.90.99 IF 11
And that got it to go. Having both routes in it seemed to break it or put it in some type of loop maybe.
I'm now able to remote into the machine perfectly =]
Thanks for all the help
I deleted all routes and only put in one route from my laptop:
route -p add 192.168.90.177 mask 255.255.255.255 192.168.90.99 IF 11
And that got it to go. Having both routes in it seemed to break it or put it in some type of loop maybe.
I'm now able to remote into the machine perfectly =]
Thanks for all the help
Microsoft Legacy OS
--
Questions
--
Followers
Top Experts
The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.