Hi pitched noise coming from PC when logging into gamespy using DM client.

[Legacy_Lazarus Magni]

               It seems like during the loging process with the downed master server, it is causing my pc to make some crazy noise when using the DM client. I never notice this with just the regular gaming client, but on logging into game spy, during the master server authentication, my pc starts making a high pitched whiring sound (either coming from the hard disk or the disk drive I assume. It stops as soon as the master server authentication fails, and I click ok to get to the GS screen. It doesn't sound good at all though, and I am wondering if this is damaging my computer? I also recall another post about this a while ago, but I can't find it any more. There was some solution posted about bypassing this whole process. Anyone have any ideas?
Thanks,
Laz
               
               

               
            

[Legacy_altphil]

               wow, never heard of that.  But I setup a local firewall rule on my Linux lappy to block any outbound connection attempts to the master server.  This helps me timeout immediately doing a REJECT instead of a DROP rule, instead of waiting for the timeout.  Makes me timeout the nwmaster login immeadiately - no wait.

Linux iptables for any other Linux users out there...
iptables -A OUTPUT -d 204.50.199.9/32 -j REJECT --reject-with icmp-port-unreachable
Awesome uber cool fedora users like myself can then run "service iptables save".  You lesser linux users can figure it out for yourselves '>  hehe  (iptables-save > filename, usually)

So for blocking from windows... man... I have no idea.  Even on high-end Cisco ASAs I don't know how to specifically say REJECT instead of DROP, and I'm a very advanced networking guy.  I've even asked my CCIE onboard (network GOD) and he doesn't know how.

First thing I would try is to setup a local hosts entry to point nwmaster.bioware.com to localhost.  See if that does it, as your local machine should reply with a closed port immediately.

Edit:  C:\\windows\\system32\\drivers\\etc\\hosts with notepad.
Add a line like so...
127.0.0.1          nwmaster.bioware.com

Save the file.
Might want to fire up a command prompt and run "ipconfig /flushdns" or do a reboot, just to ensure all DNS cache entires are flushed.  I forget if windows overrides dns entires cached or not with a hosts file.

What that does is tell your machine that the "nwmaster.bioware.com" name resolves as 127.0.0.1 (your own machine, localhost) and should try to connect to it as your own machine.  Since your machine doesn't listen on those ports and windows firewall shouldn't block (DROP) localhost connections, it should reply immediately with a REJECT, allowing you to log in without the big long stupid timeout.  Which should negate your issue you're having.

Of course, if that doesn't work, we'd have to try something else.  Maybe your router can block with icmp prohibited (REJECT) and setup an outbound block rule there.  Depends on your equipment.  But I got a feeling the hosts entry should work for you.  If not... I'm sure there's some 3rd party firewall rule for windows out there than can specify REJECT instead of the default firewall rule of DROP.  (Reject actually replies to the request with unreachable, where DROP ignores the request.... causing lengthy timeouts)

Actually laz... it would be darn nice for you to not have to wait for the timeout, because I'm sure I'm not the only one that's noticed that you seem to take a looooooong darn time to log back in...

Post up if the hosts solution works, huh?  I'm curious to know, and my windows VM can't handle nwnclient (no 3d hardware accel)

Of course, this doesn't actually resolve your problem itself... but it's a darn nice workaround that gives some bonus features like not having to wait for that stupid timeout.  Sounds to me like you have some soundcard issues.  Upgrade soundcard drivers... reinstall nwn... beyond that?  No clue.  Again... I'm a Linux guy, not a windows user.
               
               

               

                     Modifié par altphil, 30 novembre 2011 - 09:43 .
                     
                  

            

[Legacy_Lazarus Magni]

               It's possible it's a sound card issue, but to me it sounds like it's coming from the hard disk, or the disk drive. Like my machine is reading the CD keys, and trying to relay that info to the master server, but since it's not responding, it's just hanging on it. That's a complete guess though.

I might try this workaround altphil, but I seem to recall the solution I read about was using the command prompt to direct connect to the server or something. Just bypassing GS (and the master server) all together...
               
               

               
            

[Legacy_Lightfoot8]

               I will recap the thread that you mentioned that I also can not find.   There where no real answers in my opinion.  

I suggested that it could be a battery back if you are using one.  I know that when I had mine hooked up and I exceeded its max power.  It would make that high pitched sound.  

Six or Banner then said something like all sound cards make a high pitched noise when under strain and on some systems that noise gets picked up and amplified by the speakers.    At least that is what I think they said.  

the thread really said nothing more usefull than that.  

If you do have a your computer hooked up to a battery back up you may want to check if it is making the noise.   If it is the problem could be anything form the Battry back up going bad, The back up just not being rated high enough for the power usage, or it could even be the video card going bad causing the sustem to draw more power then normal.    

If you can find the fix for getting rid of that red swirl in the back ground, it would also eais a lot of the strain on the viedo card on logon
               
               

               
            

[Legacy_altphil]

               rofl

If it wasn't just the dmclient, I wouldn't be laughing.  I'd suggest checking your fan bearings.
               
               

               

                     Modifié par altphil, 30 novembre 2011 - 10:14 .
                     
                  

            

[Legacy_Lazarus Magni]

               I don't use a battery back up, and I am pretty sure it's not a hardware issue, I got a pretty decent rig, but I will open it up and check it out. I don't have this problem under any other circumstance, even when running new games.
               
               

               
            

[Legacy_altphil]

               Ya, I'd be REAL surprised to hear a strange sound only when the dmclient tries to connect to nwmaster is a hardware or UPS issue '>

Just try to locate the sound first.  Open the case, listen while you try to connect over and over.  See where it is coming from.
               
               

               
            

[Legacy_Lightfoot8]

               

altphil wrote...

Ya, I'd be REAL surprised to hear a strange sound only when the dmclient tries to connect to nwmaster is a hardware or UPS issue '>

Just try to locate the sound first. Open the case, listen while you try to connect over and over. See where it is coming from.

Unless you take into account that the most  GPU intensive NWN graphics are running in the background. 

Try  unziping this     Download File  and placing it in your override folder.  If it gets ride of your noise. It is a graphics card or Grahpics driver problem.
               
               

               

                     Modifié par Lightfoot8, 01 décembre 2011 - 03:13 .
                     
                  

            

[Legacy_Lazarus Magni]

               TY guys I may try this. I suppose first up will be updating my drivers. I will report back what I find out.
               
               

               
            

[Legacy_SuperFly_2000]

               I had a fan-sound problem with my old computer. It was however not related to the DM client but could just set off at an arbitrary time.

Finally I found the problem and a proper dismantling and cleaning of the CPU cooling flanges helped (I had to take it appart to vacuum clean it properly...there was a lot of dust there).

The problem was that when the CPU didn't get enough cooling it put the fan into turbo-jetdrive :-P
               
               

               

                     Modifié par SuperFly_2000, 01 décembre 2011 - 03:15 .
                     
                  

            

[Legacy_Lazarus Magni]

               Thank you for the input everyone, I guess trouble shooting this will be my weekend project.
               
               

               
            

[Legacy_Lazarus Magni]

               It looks like you were indeed correct Lightfoot about it being soundcard related (or audio configuration). I coulda swore it was coming from the PC, but I can now tell it is coming from my speakers.