Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
At work we are stuck on a SQL project due to a lack of resources from IT (as usual). We have gotten a nod from higher up to buy a cheap box and set up our own SQL system locally outside of IT. The comapny (which is a huge national comapny by the way) is running on WIN2k and we would like to grab a cheap box (sub $1000) and use linux and MySQL to do it ourselves.
I have set up and run Linux on my machine at home, but don't have the kind of technical knowledge to forsee possible problems in networking with a windows environment. My questions are these: How difficult is it to network a Linux box into a win2k system. How much support would I need from IT... let me rephrase that... what is the minimum amount of support I would need from IT (assuming that I have a few guys that really know what they're doing locally). Is it possible to run an SQL Linux box inside a Win2k network and keep it under the IT radar?
What distro of linux would work well with something like this? what tools would be useful in setting something like this up and making it as easy as possible.
thanks for all your help. I've found this community is the best resource of all.
All you would probably need from IT is to get them to assign you a valid IP address, this lets them keep track of fixed IPs and make sure they aren't in a dhcp range and maybe make sure the physical connections are in place to support your system. If you intend to make it available throught your national organisation - ie outside your lan then it may be a bit more work and you may run into problems depending on their IP allocation etc.
What are you going to get the clients to use in order to interface with the SQL server?
Any sitro should work fine but something like redhat is probably the simplest.
The idea is that the clients will be on Win2k machines and will interface with the linux sql box via microsoft access. it will be on our local intranet. Can access get an odbc connection to the linux box?