OK, no one is answering our questions in the guide threads. How the hell do we setup the network bridging? My network settings are:
IP: 192.168.1.2
Subnet: 255.255.255.0
Gateway: 192.168.1.1
DNS: 192.168.1.1
All help is appreciated! And no posts like "check the video" and etc. I've already seen it, it isnt explained at all there! So if anyone who has already done this and is willing to help, please, enlighten us! :D
Thanks in advance,
Deko
same request..
I need it too :D
Static IP I think cant use the Bridged network...I have static thats why I use NAT and didnt change anything in the CentOS inside. If you want NAT then in VMWare select NAT and in CentOS if you have edited the network configuration then goto System->Administration->Network and there click twice on the eth0, then select the Automatically obtain IP settings. And to see whats your IP: Enter the Terminal and type ifconfig and then you will see your CentOS IP, but for the file odbc.ini just put your PC Static IP and thats all! :P There is no difference between NAT and Bridged, just Bridged is for those who has Modems and stuffs like that, but NAT is for Cable and Static IP's.
So, i put my 192.168.1.2 ip in ODBC.ini , and what about the /etc/cabal/ ini files? do i leave the CentOS ip or do i put in the static ip?
If you have NAT then in odbc.ini you have to put the Windows Static IP not the Bridged one Windows Static IP, but Windows Static IP, for example Bridged static IP would be: 192.168.1.2, but Windows Static IP for example 89.110.39.1 something like that. So in odbc.ini you have to put 89.110.39.1. In the other ini's you have to put the IP which you see when you type in the Terminal: ifconfig.Originally Posted by deso_2006
oh, thanks man! I will try to do this now, i hope it works :D I'll post a feedback as soon as i can!
Wow, i cant believe it! :D This actually worked. Now there is the issue of getting in the server. I edint the internal.txt in my %cabal\Data\ folder. But still, I cannot connect the bar fulls up and just disconnects me. Any ideas?
Check the logs in /var/log/cabal carefully for clues. The first thing you have to do is make sure the various processes are talking to each other and the database ok as nothing else will work until they are. If they are struggling the logs will tell you.
omg so many errors in the /var/log/cabal. The DBAgent_24 cannot connect to the mssql server. WorldSvr is ok, no errors there (odd :D) and the others have similar erros. I dont know what to do, I have uploaded the logs for you guys to see it.
Reply With Quote