Getting Games to use TCP/IP and IPX/SPX in win 2k pro

[Gloryhound]

Details:
Realtek RTL8029(AS) PCI adapter
DSL connection
Stand alone install of OS

No Games are able to use the TCP/IP protocals even though they are installed and appear to be working properly. Previously this setup was working, now for no apparent reason it has failed.

IPX/SPX is equally unavailable, for use over the dsl connection. Also this had operated previously.

there is only 1 user besides admin on system, permissions appear correct.

There are no viruses or HD failure evident after checking.

I've tried several different games to exclude developer/genre or programming style.

Network operates nominally otherwize.

If somebody could tell me what I've missed it would be great.

plz feel free to request addition info, I've spent a great deal of time trying to solve this problem and have just run out of ideas, I've had no luck finding helpfull information else where

Thanx in Advance.

 

[tlcscousin]

Have you inadvertently told your firewall to stop them from accessing the internet?

 

[Gloryhound]

There is no firewall installed. Atleast I don't think there is, unless win 2k pro has it's own by default, couldn't find any indication of one.

 

[txtxcowboy]

Your not using a linksys router or ZONEALARM or anything like that? If not, then you should try reinstalling TCP/IP and also make sure your games are setup to use IP correctly.

Just trying to help...

Dave

 

[Gloryhound]

Thanx for you input dave.. all i use is a net gear 6 port hub and a DSL modem bay networks. Unless there is something on the DSL network that is inhibiting these protocals.

I tried reinstalling TCP/IP and IPX/SPX after physically removing the network card and restarting, then physically reinsert the card and reinstalled it. Still same problem. I'm all out of chickens, would someone sacrifice one and pray to the all knowing techy for an answer?? plzzzz

 

[Gloryhound]

I was checking my event viewer and notice this error on last startup

The A4SII300 service depends on the ÿParallel arbitrat group and no member of this group started.

Which was then followed by

Remote Access Connection Manager failed to start because NDISWAN could not be opened. Restart the computer. The system cannot find the file specified.

Which was then followed by

Your computer was unable to automatically configure the IP parameters for the Network Card with the network address 525400DB6FDB. The following error occurred during configuration: WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable. .

I think maybe I've hit on the cause of the problem, but I'd be darned if I new where to go to fix it. I'll keep working on it and keep this thread updated, if you can help I'd be glad.

 

[txtxcowboy]

Now it sounds like a bad driver or bad NIC. Not being able to automatically configure IP parameters hits on it being a DHCP issue (obtaining an IP from your ISP's DHCP sever).

Now, as for your HUB, does your ISP allows this? The reason I ask is because my ISP (Roadrunner) does not and they have blocked simply using a hub and requesting multiple IP's without paying for em. However, if you were to use a router and NAT you would not have this issue because the router gets the 1 IP provided from the ISP and the Router also does DHCP/NAT on your internal network and hands out internal IP's to all your machines and everything "ROUTES" through the 1 IP provided by the ISP.

Other than that, the ONLY thing I can think is that your ISP is blocking certain ports (which they shouldn't, that should be up to you) but you never know with ISP's. Give them a ring and see what they have to say.


Dave

 

[eholdo]

I'm having a similar problem. I get the same WSAStartup error, and my attempt to grab an IP through DHCP is failing. It's giving me a generic 169.x.x.x ip, which WIndows assigns when it can't see the DHCP server. My other systems can get on just fine.

If you hear of anything else that may fix this, please post it. I'm pulling my hair out on this one and will probably need to blow away the OS and start over