also @ TechSpot: Nvidia interested in licensing graphics technology to other chip makers

Need for speed most wanted LAN problem

Discussion in 'Gaming' started by getwaqas, Dec 27, 2005.

  1. anshulgoel0168 Newcomer, in training

    Nfs most wanted lan prob

    I would advice to set manual IP for all the pc's which are on lan.
    Eg

    Ip address: 192.168.1.1
    Subnet : It will take by default
    Default Gateway: 192.168.1.100
    DNS: 192.168.1.100

    all the other system should have the same lan/wifi config with the IP address changed.eg
    192.168.1.2
    192.168.1.3
    and so on.
    You Should check that all the firewall in your system are disabled including the default firewall.

    you can check if the connection is established btw system by ping command.
    eg
    start->run->ping 192.168.1.2 -t
    if everything goes fine you should get a response.

    Next run the game and make the Lan server on a system Running Windows XP and not windows vista.
    I dont know what the problem is with windows vista but the server created on windows vista is not detectable.

    Make a server on windows Xp system.

    Then it should be detectable by all systems.
    This worked for me.
    Hope This works 4 u too.
  2. jobeard TS Ambassador Posts: 12,341   +132

    Most of us highly recommend AGAINST using manual TCP configs; here's an example
    of why:
    Ip address: 192.168.1.1 This is a standardized address for a router not a workstation (the other one is at x.254)
    Subnet : It will take by default ? Without DHCP, there is no default.
    Default Gateway: 192.168.1.100 ouch! only one in 254 chances that this is correct and it's no known router's default address
    DNS: 192.168.1.100may or may not work depending upon the vendor firmware forwarding DNS requests
    DHCP is a one-time request at boot or first network access time, sets the tcp config and then
    disappears entirely. Dynamic TCP is the most reliable means to get a vaild and stable network connection.
    The SOLE exception is were you need one system to be at a known location for
    others to access, ie: a server address. The right way to setup a lan with server(s) is:
    1. set manual addresses for the server at the high end of the range
    2. set the others to DHCP and limit the ip range to less than the lowest server address
    If you have SRVR-A and SRV-B, the set A= 192.168.1.200 and B= 192.168.1.201.
    Now in your router, restrict DHCP address range to 192.168.1.2 thru 192.168.1.199
    Life will be good :)

    If you want to ensure access by name, add these two lines to
    \windows\system32\drivers\etc\host with notepad:
    192.168.1.200 srvra
    192.168.1.210 srvrb
    save the file and then copy to all your systems. Life will even be better :) :)
    most of us have lan's with routers; eg
    Code:
     
    modem---router---systemA
                +---systemB
    and the above easily conflicts with the default router address of linksys routers. The above would work ONLY when the systems
    are NOT attached to a router, but only each other using a cross-over cable; eg
    Code:
     systemA-----systemB
    keep your life simple: a router belongs at x.x.y.1 and systems at y.2 -> y.254
    y.0 and y.255 are broadcast address so don't even thing of using these.

    If you visit the Network forum, you will see that one of the first things recommended
    for connection issues is to update the router firmware and the network adapter drivers. This frequently solves 80% of the issues.

    GAMING places heavy stress on our routers and that is why there are some models specifically marketed as gaming routers.
  3. Zacholt Newcomer, in training

    i am zac holt ha
  4. ROADSIDEROMEO Newcomer, in training

    hei i'll make it easy for you . first open the properties of your lan in the server machine and then follow the followings steps
    click on internet protocol>properties then write the following--:
    ip -192.168.0.1
    subnet- 255.255.255.0
    default gateway- 192.168.0.1
    click on use preffered dns then type
    preferred dns 192.168.0.1
    click on advanced and then select wins tile and type
    add>type 192.168.0.1>add
    then return to lan properties and click on advanced>windows firewall settings>off
    then in the client pc open its lan properties & follow these steps
    click on internet protocol>properties then write the following--:
    ip -192.168.0.2 or (192.168.0.3)
    subnet- 255.255.255.0
    default gateway- 192.168.0.1
    click on use preffered dns then type
    preferred dns 192.168.0.1
    click on advanced and then select wins tile and type
    add>type 192.168.0.1>add
    then return to lan properties and click on advanced>windows firewall settings>off
    this will do to get nfs mw running in lan
  5. jobeard TS Ambassador Posts: 12,341   +132

    this is fine for a quick test, but DO NOT EXPECT TO LEAVE IT OFF!

    If the test w/o the FW works, then you only need to properly configure the FW.
    If not, then there are other issues.
  6. eway2addy Newcomer, in training

    How many ON LAN at a time..??

    heu guys if anyone could please help me increase the number of players >4 in NFS most wanted while playing on LAN....
    whats the max no of players who can play on a single LAN server...??
     
  7. ROADSIDEROMEO Newcomer, in training

    4 players can play at max in this game so no effort can be made to increase the no of players
  8. LookinAround TechSpot Chancellor Posts: 7,699   +40

    hey guys

    Interesting thread.

    It was interesting to read the chronological list of posts as you all muddled your way through to something that worked (and not saying that in a bad sense. Simply. that was one of the few options on how to solve your problems) And having something that works is important. Tho, of course, we only know it works "for now"

    But let me add, I'm with jobeard 110% and don't think it's wise to manually configure your LAN by the "trial-and-error-oh-this-option-looks-interesting-lets-try-it" approach to making things work

    So, point of all this being is, if you all want, you can continue to present/discuss the problems you're having and any requirements you need fill.

    I'd be happy to add a network/configuration perspective from time-to-time. And i'm certain jobeard would be happy to do same (jobeard: don't want to be speaking on your behalf but thought this was a safe bet to state on your behalf)

    Then, hopefully, your problems don't "just" get fixed but, rather, get fixed from a broader networking point of view.