Dear Unreal, wtf are you doing?

[[§Ŕ] ŤhěxĐâŕkśîđěŕ]

Just installed Windows 7 x64 on my dad's laptop for best performance in Windows games, and decided to try out Unreal. It works with no problems, etc., but something caught my eye when I first started it: ZoneAlarm notified me that it's trying to access 199.7.51.190 (I allowed it, lulz). Can anyone explain me, what the fuck is that shit, and is it Unreal-related or Windows 7-related? Oh by the way, I installed Unreal from a ~170 MB RAR (inb4 illegal) that I made, containing just the default Unreal files (no Unreal.ini and no User.ini), patched to 227f, with nothing else changed, so it's the same as if I installed it from the CD and patched to 227f, without touching anything else, so it isn't user settings that made it do that. I never noticed Unreal doing that crap on my laptop under both XP and Linux, so I'm somewhat sure that it's 7's "fault".

For TL;CR wankers: an original Unreal install with patch 227f tried to access 199.7.51.190 on Windows 7 x64. Verified that the exe is clean.

Oh and don't be sad, I kept Ubuntu 9.10 on the HDD of course. Just made a dual boot for gaming on Windows for my dad, lol.

EDIT: Oh and forgot to note that this happened before Unreal actually started, it was during the setup screen, which lets you choose video and audio drivers (displayed when starting Unreal for the first time).

[[]KAOS[]Casey]

can't explain through master servers or otherwise, i'm not sure. unless you clicked the mutliplayer menus...

[Oldsparky]

OrgName:    VeriSign Global Registry Services
OrgID:      VGRS
Address:    21345 Ridgetop Circle
City:       Dulles
StateProv:  VA
PostalCode: 20166
Country:    US

NetRange:   199.7.48.0 - 199.7.63.255
CIDR:       199.7.48.0/20
NetName:    VGRSGTLD-15
NetHandle:  NET-199-7-48-0-1
Parent:     NET-199-0-0-0-0
NetType:    Direct Assignment
NameServer: C2.NSTLD.COM
NameServer: D2.NSTLD.COM
NameServer: E2.NSTLD.COM
NameServer: L2.NSTLD.COM
Comment:    
RegDate:    2004-01-29
Updated:    2004-01-29

OrgTechHandle: NETWO480-ARIN
OrgTechName:   Network Admin
OrgTechPhone:  +1-703-948-4300
OrgTechEmail:  netadmin@verisign.com

[Pyro]

dude, you're fucked! get the hell outta there, throw your laptop in the lake and take the bus, dont pay with your credit card!

[Smirftsch]

This is definitely not Unreal related. I strongly suggest to check with antivirus and antispy tools where this is really coming from.

[Hyper]

The server at 199.7.51.190 is a VeriSign Certificate Authority. I guess it is a signed installer or program. It was signed with a VeriSign Certificate and Windows by default will attempt to contact the certificate authority in order to determine if the certificate that signed the executable is still valid. 199.7.51.190 is actually "crl.verisign.com" which is a Certificate Revocation List server. Checking certificate status is actually a very good thing and signing install files is something that a lot of companies do now - and those that don't should, because it ensures that the file is as the signing company meant it to be, i.e. unaltered and unhacked.

[Smirftsch]

from the installer or the game itself?
I understood that the game is assumed to do it.
The installer is the original which Epic used too, maybe that would explain it, I never checked if its signed or not, but I'm pretty sure that the game doesn't contain anything like that- I mean, there are hundreds of thousands lines of code, it's close to impossible to know everything in there, but if there is something like that it was there before already.
227 doesn't contain any malware, spyware or virus, anyone is invited to verify that.
So either its something old or it's something on the pc.

[Pyro]

turn off ur internets, and see what it does ?

[[§Ŕ] ŤhěxĐâŕkśîđěŕ]

It appeared when I started Unreal (after it was already installed), but before it started rendering, playing music, etc.: it was during the "first time configuration" dialog. I did it on a clean installation of Win7 on a freshly formatted partition (did both the format and installation earlier that same day). I didn't even think that 227 has malware in it, I've been running it on both Windows and Linux since it came out and nothing bad ever happened to my laptop or any other PC I was running it on.

I know how to use whois, nslookup, and other server query tools, and I'm aware that the IP belongs to VeriSign, I just thought it was weird because I never saw it accessing that IP before. Although maybe it did it before but I didn't notice (I set Unreal.exe to safe after running it a few times on Windows on my laptop, so it doesn't ever ask me anything about it anymore cause I trust the patch).

And you don't have to investigate it or anything, I posted this as info, not as a bug report. I don't worry about it so I don't think you should either, lol.