WiFi blocking Domain Network

Hi All,

I have encountered a strange behavior with my networks.

In my office, my laptop is connected to our Domain network via cable (LAN) connection. I normally also connect to an external network via WiFi that I use as internet connection for my virtual machines.
I am using my virtual machines for VPN connections towards some of our customer domains, so I can connect via RDP to their servers.

The external WiFi I have so far used is the device:

No problem everything worked fine.

As the router mentioned above, is normally intended for use in the field, and has only limited WiFI coverage, I decided to switch to this model:

But, when I connect to the WiFi on the new device, I can no longer be connected to my domain network via cable at the same time.
I shows that I am connected to a network with cable, but it just shows 'Network 2' 'Unknown Network'. And all domain access is lost (Can not send emails, browse intranet or fileservers).

Do anyone have an idea why it is behaving like this?

Discussion is locked

Reply to: WiFi blocking Domain Network
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: WiFi blocking Domain Network
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
- Collapse -
Clarification Request
Is there any IP conflict in the setup?

For example I did consult on one like this and the poor user had set the IP range of the router to be the same as their company LAN. Nope, that never works.

- Collapse -
No IP conflict

Hi R. Proffitt,

No, there is not an IP conflict.

The domain network IP range is 10.xx.xx.xx, and the ext network is 192.168.xx.xx.

I observed another thing yesterday, when the domain network is already connected and working, and I then connect to the ext wifi network, it is not all of my 'domain access' that is gone. Our internal chat system still works (IBM Sametime). However I have no fileserver access or can send and receive emails.

- Collapse -
The thing is

Network shares for all intents do not work across LANs. Inside the LAN? Yes, but if you are on one LAN, then you should not see the share on the other LAN.

Email, chat systems differ on this. There are long prior discussions on this so I won't duplicate that here. In short if the share is on 10.x.x.x, you won't see the share on 192.x.x.x

CNET Forums

Forum Info