Re: Renamed server, can't connect...
From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 10/07/04
- Next message: Jesse Gardner: "Re: Renamed server, can't connect..."
- Previous message: Eric Hughes: "WINS Domain Controller Entry is backup IP address"
- In reply to: Jesse Gardner: "Re: Renamed server, can't connect..."
- Next in thread: Jesse Gardner: "Re: Renamed server, can't connect..."
- Reply: Jesse Gardner: "Re: Renamed server, can't connect..."
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 7 Oct 2004 12:21:35 -0500
Hmm. Nbtstat looks like it might be OK. I just wanted you to run that to see
if it was registering names which would indicate the server, workstation
service, and netbios over tcp/ip are running. If you run netstat -an it
should show at least port 445 tcp and probably port 139 tcp listening. It is
puzzling that you can ping and connect via TS but not file and print
sharing. From another computer on the network I would use the portqry
utility to see if it reports ports 139 and or 445 as listening on your
problem server. See the link below on how to use portqry and where to
download it from. For instance use " portqry -n xxx.xxx.xxx.xxx -e 139 " to
find if port 139 tcp is available on the problem server [using it's IP
address] from a remote computer.
http://support.microsoft.com/default.aspx?kbid=310099
Since it is a domain computer try running the support tool netdiag on it to
see if any failed tests, warnings, or errors are reported that may give a
clue. The /v or debug switches can give more detailed info if you find a
problem as in " netdiag /test:dns /debug ". Netdiag and other support tools
are found on the install disk for the server operating system in the
support/tools folder where you will have to run the setup there to install
them. Be sure to pay attention to the winsock test also when you run
netdiag. Your nbtstat results indicate Local Area Connection 2. If the
computer has more than one nic make sure that the nic used for the local
lan/domain is at the top of the list in network
connections/advanced/advanced properties. -- Steve
"Jesse Gardner" <admin_deleteth1s@badcrc.com> wrote in message
news:416556D8.8050501@badcrc.com...
> Thanks for your reply, I've answered your questions below. Most
> noteworthy is the nbtstat -n results.
>
>
>
> Steven L Umbach wrote:
>
>> Try using the IP address to access it instead of the name to see if that
>> helps as in \\xxx.xxx.xxx.xxx\share or use the IP address in Computer
>> Management.
>
> Tried, didn't work.
>
> At the command prompt run nbtstat -RR and Ipconfig /registerdns.
>> Check the wins and dns records to make sure they are correct.
>
> Tried, didn't seem to help.
>
> It would help
>> to know if this is a domain computer, what operating system, what type of
>> server, etc.
>
> Windows Server 2003 Enterprise w/ SQL 2000 Enterprise On an AD domain in
> mixed mode.
>
> Windows 2003 Server has a built in firewall that you would want
>> to check the configuration of if enabled.
>
> Internet connection firewall is not enabled.
>
> Look in Event Viewer for any
>> pertinent errors
>
> No scary events.
>
> and make sure that the server service is running
>
> It's running.
>
> and that
>> netbios over tcp/ip is enabled in tcp/ip properties/advanced wins.
>
> Yup.
>
> The
>> nbtstat -n command should show at least three entries.
>
>
> !!! This is what I get !!!
>
> C:\Documents and Settings\someuser>nbtstat -n
>
> Local Area Connection 2:
> Node IpAddress: [172.30.32.22] Scope Id: []
>
> NetBIOS Local Name Table
>
> Name Type Status
> ---------------------------------------------
> THE_SERVER <00> UNIQUE Registered
> AD_DOM <00> GROUP Registered
> THE_SERVER <20> UNIQUE Registered
> AD_DOM <1E> GROUP Registered
>
>
> !!! Is there something missing? !!!
>
>
>
> If it is a Windows
>> 2003 Server you may also want to open Local Security Policy and go to
>> security settings/local policies/security options and set the option for
>> Microsoft network server:digitally sign communications(always) to
>> ISABLED. --- Steve
>
> It is disabled.
>
>
>
>>
>>
>>
>> "Jesse Gardner" <admin_deleteth1s@badcrc.com> wrote in message
>> news:2sj9dgF1ka2sjU1@uni-berlin.de...
>>
>>>We renamed a server, and replaced it with another server that has taken
>>>the old server's name and IP.
>>>
>>>DNS and WINS show the right IP to the right name, I can ping it by name.
>>>But when I go Start-->Run-->\\Servername I get "Windows cannot find
>>>'\\Servername.domain.com'. Check spelling blah blah"
>>>
>>>Where should I look? I can ping, connect via TS. But cannot access
>>>shares, and if I try to "manage" the server remotely I get "Computer
>>>\\Servernam cannot be managed. The semaphore timeout period has
>>>expired."
>>>
>>>I've never had this problem before, is it WINS or something like that?
>>>Netbios over TCP/IP is enabled if that helps.
>>>
>>>
>>>Thanks!
>>
>>
- Next message: Jesse Gardner: "Re: Renamed server, can't connect..."
- Previous message: Eric Hughes: "WINS Domain Controller Entry is backup IP address"
- In reply to: Jesse Gardner: "Re: Renamed server, can't connect..."
- Next in thread: Jesse Gardner: "Re: Renamed server, can't connect..."
- Reply: Jesse Gardner: "Re: Renamed server, can't connect..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
