25-03-2008, 07:12 AM
Fixed.
Had to reset Winsock settings in Command Prompt.
Googled around, found out it's common I guess.
Something about the settings being corrupted during debugging.
Had to reset Winsock settings in Command Prompt.
Googled around, found out it's common I guess.
Something about the settings being corrupted during debugging.