- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
M4250 driver update issue
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After support got my switch running. the switch has worked just fine. I updated it because I was going to trunk a new switch. After the update. I now have 2 cams showing on 192.168.12 and 2 showing up on 192.168.100. .12 is my address from modem/router so when I go to OBS or NDI Tools, all I get is the 2 cams on .12
I did test all my cables with both the one on the 4250 as well as a good Klien tester
I'm just a live streamer with just enough network knowledge to get me in trouble
What should I do?
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Finally figured it out.
For some reason the 2 cams had reverted back to static ip addresses.
Not sure where the .100. came from as the cams factory setting was a .1. address
Whatever, its back to working
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: M4250 driver update issue
I ended up resetting the switch and used engage to get it setup.
I just changed the default DATA to NDI on all the ports
To add a vlan for DATA. do I just leave the dhcp stuff greyed out so that I can it gets seen by my ip scanner?
Can I just copy the Engage exe file to a usb stick so I can control from my home and location I work from?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Finally figured it out.
For some reason the 2 cams had reverted back to static ip addresses.
Not sure where the .100. came from as the cams factory setting was a .1. address
Whatever, its back to working