[solved] [zero] unable to conect

[wolverine]

Hey, Killer. I just realized I can just open my WoW up to you. I created you an account killerdragon and the pass is temp.

My IP address is 173.172.198.80. Just put that in your realmlist.wtf file in your vanilla client and you should be able to connect. If you still have trouble, as I have already tested my setup, then I will upload my copy of the client and you can download it and we will see if that works for you.

I was just wondering if you had had a chance to try this one out yet? This way we can eliminate whether or not you might have a corrupted copy of the client...

[KillerDragon]

is the server up right now?

[wolverine]

Yes.

I'm even connected via the external IP that I gave you.

[KillerDragon]

I tryed to connect to the server. and I got connecting for a bit then disconnected from server. hehe well thats a difrent error then what I got trying to get onto my server. heh. Is there a way we can do live chating for this?

[wolverine]

All I can think of is skype. I'm wolverine79936 on there...

What are you running the client on? Server 2008? If that's the case, it could be something to do with how the kernel in 2008 deals with networking. I use to have 2008 server, but got rid of it. I do a lot of video streaming over my private network and it wouldn't do that. Every few seconds we had to restart the videos. And that was with the streaming features enabled.

I don't know if that could even be related to this issue, but technically, MaNGOS could be considered as a stream by the server...? Perhaps you should try running this on your PC, I'm assuming that is either Windows 8 or 7... And see if it works there.

Just another idea.

[wolverine]

I wish that there were a fireworks emote on here now. We finally got him fixed. Turns out that KillerDragon's client was corrupted. We got him a new copy of the client and everything started working again for him.

[wolverine]

Well, as I pointed out in my last post, this issue has been resolved. It turned out that the client was corrupted and needed to be replaced. Now everything is working the way it should for [MENTION=175]KillerDragon[/MENTION].