DUX COMPUTER DIGEST

 

Site Search

Site Info

Home » Forums » Forum Archives » Networking and Internet Sharing » Topic # 1845

Windows XP networking problem
kr333 Apr-21-02 12:05 PM
Hi,

I am having a networking problem with Windows XP connecting to my campus network. I can connect with my older Win98 PC. In the Windows XP computer I have entered the Computer name, Workgroup, IP-address, Subnet Mask, Gateway, DNS-Servers, Domain Suffix Search Order and Domain ("Domain" in DNS sense) provided by the network admin. I have triple-checked these values. All other settings are default settings.

The hardware installation of the network card is fine. I have also tried three different network cards(D-Link NetNIC 100P-same as Realtek 8139, SMC 1255TX, Intel) all resulting in the same problem:

I can send packets but not receive any (I checked this in properties of the network connection). I can ping my own computer by using the actual IP-address. But I cannot ping any other computer.

Some time ago I managed to get networking working on this computer under Windows XP, with using exactly the same settings. At that time I was using the Abit nForce N7vm motherboard (which I blew up) with onboard LAN. Now I am using an Asus A7V333 and a Inno3D Geforce3 graphics card instead of that. I also tried replacing the graphics card. Nothing helps.

Does anyone have any ideas how to solve this.


1. RE: Windows XP networking problem
DJ Net2Infinity Apr-21-02 01:38 PM
In response to message 0
What protocols do you have configured to your adapter? (i.e. TCP/IP, IPX/SPX, NetBEUI)

2. RE: Windows XP networking problem
kr333 Apr-21-02 03:53 PM
In response to message 1
Just TCP/IP. In the drop-down box with Clients/Protocols there is also "Client for Microsoft Networks", "QoS Packet Scheduler", "File and Printer Sharing for Microsoft Networks". All four items were there by default. I only configured the TCP/IP settings.

Kasim


3. RE: Windows XP networking problem
DJ Net2Infinity Apr-21-02 05:57 PM
In response to message 2
I would remove QoS Packet Scheduler and try that. And can you ping 127.0.0.0 ?

4. RE: Windows XP networking problem
kr333 Apr-21-02 06:17 PM
In response to message 3
LAST EDITED ON Apr-21-02 AT 06:17 PM (EST)
 
Still have the same problem. When I entered 127.0.0.0 it said "invalid IP address specified". Did you really mean 127.0.0.0 or 127.0.0.1, because that one works.

5. RE: Windows XP networking problem
DJ Net2Infinity Apr-21-02 06:29 PM
In response to message 4
Yes my mistake, I was typing a little too fast. Do you have the 98 machine still ?... I would be curious as to its Network settings. And by the way you have restarted the PC a few times, correct?

6. RE: Windows XP networking problem
kr333 Apr-21-02 06:59 PM
In response to message 5
Yeah, the Windows 98 machine is working fine with the same settings. Essentially it is the same setup and nearly the same dialogue boxes. The only difference is that in Windows 98 I specify the primary network logon as "Client for Microsoft Networking". Also there are less options on the DNS tab in Win98.

I have restarted the computer a few times, I have re-installed Windows XP (formatting the entire disk first) a few times and I have changed the PCI slot of the network controller.


7. RE: Windows XP networking problem
DJ Net2Infinity Apr-21-02 07:19 PM
In response to message 6
Yeah you have to have the client for microsoft networking enabled and configured because thats the way you log onto the network.

8. RE: Windows XP networking problem
lbyard Apr-22-02 11:48 AM
In response to message 0
Most network adapters have a Link LED or a combination Activity/Link LED. The LINK LED should be on solid. Most Activity/Link LEDs stay on solid most of the time, indicating a good link, and blink when there is activity. If the link looks good, try running ipconfig from a DOS Window. Type
C:\>ipconfig /?
for the syntax
What does release and renew the IP address do?
Larry

9. RE: Windows XP networking problem
kr333 Apr-26-02 09:33 AM
In response to message 8
Thanks for your reply. I think I am coming close to the solution of the problem. I found out that some network equipment has a maximum number of ethernet cards that are allowed to connect from one socket. That is why my original card was working throughout, my second one was also working, but the third one could not connect. I will ask the network administrator to look into this. I am sure this is the reason.

Kasim


| Home | Guides | How to | Reviews | Online Store | FAQ | Forums | Forum Archives |
| Links | News | Newsletter | About Dux | Advertising | Contact Info | Privacy |