Posts: 147
Threads: 7
Joined: Apr 2009
My home pc, Win 7 64 is running the Master server just fine, but I rarely use that pc. Since I work from home and spend most of my time in the office I'd like to install a Client Server on my work pc. My work pc logs into a domain.
I've tried what I thought were the right names and IP address for the Master Server, but it doesn't seem to connect. I am able to browse to the Master Server PC from my laptop and copy files and such, but figure I am doing something really stupid that I can't get CQC to talk.
The IP isn't static for the Master as I need some permission in my router to do that, but it would be "static" enough for the install I thought. Obviously the computer name is an easy one.
Is there something I am overlooking?
Posts: 40,483
Threads: 491
Joined: Aug 2002
You probably will need to upgrade to the latest best (in the Beta section, sticky thread at the top.) Upgrade the server and then try the client again. There were some issues with IPV6 which are probably causing the failures. It's plenty stable and has lots of new stuff.
Dean Roddey
Explorans limites defectum
Posts: 147
Threads: 7
Joined: Apr 2009
Doh! Haven't used CQC in nearly a year since I "got" a new Win 7 laptop and it didn't speak to my XP Server. Finally upgraded it a few months ago and have been struggling with this thinking I was a Windows moron since. Going to grab the Beta now and try it out. Thanks Dean.
Posts: 147
Threads: 7
Joined: Apr 2009
Problem solved, resolved just by the computer name. Thanks for the help.
Posts: 40,483
Threads: 491
Joined: Aug 2002
The whole IPV6 thing was kind of unfortunate. The problem is that you have to explictly indicate you only want IPV4 addresses in any socket calls that deal with addresses or lookup. But, for a long time there really wasn't anything else so you got that by default if you didn't set the flag explictly. So there was probably lots of software out there that hadn't set it in lots of calls. Then IPV6 starts getting installed and enabled automatically and suddenly the program may not get an IPV4 address, and won't work.
Dean Roddey
Explorans limites defectum
Posts: 3,415
Threads: 158
Joined: Jan 2006
According to standards IPV6 is always preferred over IPV4. So once it is turned on it will get used by default. Just try to ping a name on a Win7 machine with IPV6 enabled and you will see what I mean.
Unfortunately we are quickly getting to the point where IPV6 is going to be required. IPV4 addresses have run out several times in the last few years. Companies and carriers will mitigate with private addressing but within the next 5 years most software will probably be required to support IPv6. Some countries, like China, and some entities like the U.S. government already require it. And you will probably start seeing mobile devices using IPV6 exclusively on some cell networks in the next couple of years.
Posts: 40,483
Threads: 491
Joined: Aug 2002
It wouldn't be an issue within the home LAN though, right? It would seem that NAT could just as easily expose everything through a single IPV6 as IPV4 address but still use IPV4 addresses internally for a long time to come?
Dean Roddey
Explorans limites defectum
Posts: 3,415
Threads: 158
Joined: Jan 2006
02-10-2012, 01:25 PM
(This post was last modified: 02-10-2012, 01:28 PM by wuench.)
Yes it will start with public IP's, and consumer's routers will need to support NATing 6 to 4.
But one of the goals of IPV6 is end-to-end security with IPSEC builtin so you will have to have IPV6 addresses on both hosts for that to work. Think VPNs, etc. That's mostly why MS has it turned on now, to support their VPN technologies. What you will probably see at some point is MS delivering PC's with IPV4 turned off. IPV6 has features (link-local addressing, etc) that eliminates the need for static ip's or DHCP on small non-routed networks. So the network will come from the router (assigned by your ISP) and the host addresses will just be based on the MAC. So in the end it will be easier for the consumer (theoretically).
It has to happen and it will be painful. Everyone's excuses for delaying it are going to run out, the internet can't grow much more without it. So plan accordingly, maybe 3-5 years before MS turns off IPV4 (and pisses people off in the process). Probably 10-15 before IPv4 is totally gone. And word is you'll see mobile devices very soon, using it when on carrier networks.
