Link to home
Create AccountLog in
Avatar of DrEddieS
DrEddieS

asked on

network connection

At&T installed new broadband router on our system, now we can only access the internet. Can't map or connect work stations to server. Ran network wizard. Can ping and get relpy from Gateway, but not the Server IP
Avatar of PaulD77
PaulD77
Flag of United States of America image

Are you able to log into the new router make sure it's not set up as DHCP?
SOLUTION
Avatar of EMJSR
EMJSR
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Well, if their server is handling DHCP, DHCP would in fact have to bet set to OFF in the router. The same goes for DNS. If they have a Windows Server as a domain controller (and a domain), then that server is likely handling all these things.

But, without further information, it's a shot in the dark at best.
Avatar of DrEddieS
DrEddieS

ASKER

There are FIve units in the network. All machines use Windows XP Professional. One Machine is the "Server".The others are "Work Stations".  We were able to MAP to the the Data Drive (D) on the "Server" which containes our Operatioanl Data (Tax), before AT&T brought in the new router and swithched to "Uverse" from DSL. We can ping each machine, except the "Server". We can go to the Internet from all machines, but the "Stations" can't map to the "Server" or ping it.
In that case your server machine most likely has a static IP setup. Go into network settings within Control Panel and look into the Local Area Connection properties and there in the Internet Connection TCP/IP settings. Have a look there and either change the router to the IP settings specified there, or change the server to match the other computers. You can find out the settings when you open a command prompt and type: ipconfig /all

So as I said, most likely AT&T waltzed in there without any regard for your setup and now your network is messed up.
Start with looking at your default gateway....
In your scenario it should be the new router.
Post your IP settings if you like, but if you follow my previous advice you can get this going easily.
IP Settings from "Server":


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\ad_man>ipconfig/all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : server
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Broadcast
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : att.net

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : att.net
        Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
        Physical Address. . . . . . . . . : 10-60-4B-65-F2-0A
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.184
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.254
        DHCP Server . . . . . . . . . . . : 192.168.1.254
        DNS Servers . . . . . . . . . . . : 192.168.1.254
        Lease Obtained. . . . . . . . . . : Wednesday, May 22, 2013 10:22:17 PM
        Lease Expires . . . . . . . . . . : Thursday, May 23, 2013 10:22:17 PM
ASKER CERTIFIED SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Ultimately your server should have static IP though in this case it is NOT the cause of your problem. Make sure that you do not have DHCP server service enabled on your server.
Also let me know if you can ping just the "server" ( from your cmd console "ping server"
I suspect that you will not be able to and we will address this next.
Read up on hosts file to add your server IP to the table. The file location:
Windows 95 - C:windows
Windows 98 - C:\windows
Windows Me - C:\windows
Windows 2000 - C:windows\system32\drivers\etc
Windows XP - C:\windows\system32\drivers\etc
Windows NT - C:\winnt\system32\drivers\etc
That is what I had suggested in the first place, that there are two DHCP servers on the network, but it was stated further above by the author, that all machines are Windows XP Professional, so one machine was simply designated as server, but is not running Server OS. Hence I do not believe that to be the problem. I think it is in fact the issue, that the "server" does not have a static IP and that there are some network drives/shares setup, that point to a UNC path that can no longer be found.

The hosts file you mentioned may very well be half the cause due to settings there. The previous setup may well have been all DHCP auto as well, but the IP lease may have been configured to never expire. Without actually looking at all the machines and the configuration it is very difficult to tell.
For "some" it may be difficult, not for me.
But thank you for agreeing with me. It means a lot...
;-)
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
EMJSR's pointed to static IPs, which I had AT&T assign, however still no connection between Server and workstations. I took a break, came back and asked "What is blocking the Newwork"? Turned off AVG firewall and connection were established. The conflict was the new Uverse Modem and AVG Firewall. EMJSR give the best direction

Thanks