• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

TCP/IP network question

R

rsales

Senior member
When I tried to run Diablo2 between two of my computers using the lan it didn't work. I put in the IP for the other computer in Diablo2 and it said it couldn't find it then brought up the dial networking. Won't ping either. Now I don't have the network setup as tcp/ip, but the tcp/ip prodicals are loaded and the nic tcp/ip is showing. When I have taken the computer to a friends house who's network is tcp/ip it worked ok. Any ideas?
 
Sounds like you need to assign some IP addresses and subnet masks. I suggest 192.168.1.10 255.255.255.0 and 192.168.1.11 255.255.255.0. I hope it is truly that simple.
 
You friend may have been running a DHCP server (some routers for example, do this) so that you did not have to assign TCP/IP addresses manually. At home you might have to.

As for seeing the other system's shared folders and printers, that is enabled through the NetBEUI protocol. But Diablo2 needs TCP/IP protocol.

Right-click on Network Neighborhood then --> Properties -->TCP/IP (for NIC, not dialup) -->Properties -->IP Address -->Specify an IP address -->IP Address -->192.168.0.10 -->Subnet Mask -->255.255.255.0

Do the same on the other machine, but use 192.168.0.11 for the IP Address

 
Both machines have ip addresses specified and subnet mask. That's where I got the ip addresses I tried to use. Now one of the machines has an ip address that was created by ICS. ICS is currently disabled. The other machine had an IP address I put in 100.100.100.100 . I use these same IP addresses when I use ghost to image drives across the network to a drive I use to backup the other drives. Must be something I am missing here.
 
Both machines MUST have ip addresses that are in the same subnet. Won't work otherwise. This is what CTR is suggesting, in part at least. If you use what he's telling you, then it should work.

You can't have one machine with 192.168.0.1/24 and another with 100.100.100.100/??.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top