-
Posts
115 -
Joined
-
Last visited
-
Donations
0.00 USD -
Points
1,594,150 [ Donate ]
Content Type
Profiles
Forums
Gallery
Twitch
Running Commentary
Events
Store
Downloads
Everything posted by wingnut
-
has she got a sister called Wilma Fingerdoo
-
are you north london then, slowz ? come on arsenal
-
looking forward to this, last meet was great fun
-
happy birthday
-
happy birthday
-
happy birthday all
-
happy birthday
-
Please send me the antidote for Coors Lite - urgent
wingnut replied to RobMc's topic in Jokes and Misc stuff
more coors works for me -
Call name in WAW
wingnut replied to Themadman's topic in Call of Duty: World At War's Call Of Duty: World At War Discussion
hi madman waw -
happy birthday
-
happy birthday for yesterday
-
happy birthday
-
yeah im unsure about that part, but the not being able to join LAN sounds like a fix
-
first i would make sure firewall is allowing game and that you dont have a vpn running
-
found this maz sounds alot like your issue, and not too bad to fix If you are having trouble loading Call of Duty: World at War (CoD 5) games via LAN and are forced to use manual IP addresses, it is likely due to the game's inability to automatically broadcast or discover servers on your network, or because of conflicting network adapters . Here are the tested fixes for this issue: 1. Fix LAN Discovery (Set Net Port) Often, the game fails to establish a proper LAN handshake, requiring you to force the port. Open the console in the game using the ~ key (tilde). Type: /set net_port 28961 and press Enter. Type it again to verify the output shows: net_port 28960 -> latched value 28961. Have all players do this, then try to see the lobby. 2. Disable Virtual/VPN Network Adapters If you have VirtualBox, VMware, Hamachi, or a VPN installed, CoD 5 may be trying to use those network connections instead of your actual LAN/Ethernet connection. Go to Control Panel -> Network and Sharing Center -> Change adapter settings. Disable all adapters except the one you are currently using (e.g., disable Wi-Fi if using Ethernet, disable VirtualBox Host-Only Network). 3. Check for Firewall/Antivirus Blocking Windows Firewall may be blocking the game from acting as a server, even on a local network. Allow the CoDWaW.exe or CoDWaWMP.exe through Windows Firewall. 4. Direct IP Connect (Alternative) Since you are already comfortable with using IP addresses, you can force the connection in the console, which is sometimes more reliable than the lobby browser: Host opens the server. Clients open the console (~) and type: /connect <HOST_IP_ADDRESS>. Summary of Common Causes Multiple Network Adapters: The game gets confused. Port Conflicts: Using the same port (28960) for multiple computers on the same router. Firewall Rules: Blocking the game's ability to broadcast.
-
happy birthday
-
happy birthday to you both
-
that could make things interesting
-
good idea jonesy bolt only used to be really popular one little issue on our servers is there are certain people who turn down graphics to an unplayable degree to make bushes and ammo crates disappear and gain an unfair advantage which they would love bolts only but a server without rocket launchers and betties would be interesting
-
yeah and hes a useless lupus
